Skip to content

Commit 25e7d58

Browse files
authored
Merge pull request #301 from saintmalik/fix-typo
fix typos in doc
2 parents 72e689d + 2d2df77 commit 25e7d58

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

doc_source/API_Invoke.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -118,7 +118,7 @@ HTTP Status Code: 502
118118
HTTP Status Code: 502
119119

120120
**EFSIOException**
121-
An error occured when reading from or writing to a connected file system\.
121+
An error occurred when reading from or writing to a connected file system\.
122122
HTTP Status Code: 410
123123

124124
**EFSMountConnectivityException**
@@ -220,4 +220,4 @@ For more information about using this API in one of the language\-specific AWS S
220220
+ [ AWS SDK for JavaScript](https://docs.aws.amazon.com/goto/AWSJavaScriptSDK/lambda-2015-03-31/Invoke)
221221
+ [ AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/lambda-2015-03-31/Invoke)
222222
+ [ AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/lambda-2015-03-31/Invoke)
223-
+ [ AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/lambda-2015-03-31/Invoke)
223+
+ [ AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/lambda-2015-03-31/Invoke)

doc_source/troubleshooting-images.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66

77
Verify that the ENTRYPOINT to your container image includes the absolute path as the location\. Also verify that the image does not contain a symlink as the ENTRYPOINT\.
88

9-
## Lambda: System provisioning additonal capacity<a name="troubleshooting-images-capacity"></a>
9+
## Lambda: System provisioning additional capacity<a name="troubleshooting-images-capacity"></a>
1010

1111
**Error:** *“Error: We currently do not have sufficient capacity in the region you requested\. Our system will be working on provisioning additional capacity\.*
1212

@@ -16,4 +16,4 @@ Retry the function invocation\. If the retry fails, validate that the files requ
1616

1717
**Error:** *You are using an AWS CloudFormation template, and your container ENTRYPOINT is being overridden with a null or empty value\.*
1818

19-
Review the `ImageConfig` resource in the AWS CloudFormation template\. If you declare an `ImageConfig` resource in your template, you must provide non\-empty values for all three of the properties\.
19+
Review the `ImageConfig` resource in the AWS CloudFormation template\. If you declare an `ImageConfig` resource in your template, you must provide non\-empty values for all three of the properties\.

doc_source/with-sns-example.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ Do not use the `--source-account` parameter to add a source account to the Lambd
130130
**Note**
131131
If the account with the SNS topic is hosted in an opt\-in region, you need to specify the region in the principal\. For an example, see [Invoking Lambda functions using Amazon SNS notifications](https://docs.aws.amazon.com/sns/latest/dg/sns-lambda.html) in the *Amazon Simple Notification Service Developer Guide*\.
132132

133-
## Create a subscription<a name="with-sns-create-supscription"></a>
133+
## Create a subscription<a name="with-sns-create-subscription"></a>
134134

135135
From account B, subscribe the Lambda function to the topic\. When a message is sent to the `sns-topic-for-lambda` topic in account A \(01234567891A\), Amazon SNS invokes the `Function-With-SNS` function in account B \(01234567891B\)\.
136136

@@ -207,4 +207,4 @@ You can now delete the resources that you created for this tutorial, unless you
207207

208208
1. Select the subscription you created\.
209209

210-
1. Choose **Delete**, **Delete**\.
210+
1. Choose **Delete**, **Delete**\.

0 commit comments

Comments
 (0)