AWS lambda documentation change
Summary
Minor grammatical correction in Node.js initialization documentation
Security assessment
The change fixes a typo and does not impact security content.
Diff
diff --git a/lambda/latest/dg/lambda-nodejs.md b/lambda/latest/dg/lambda-nodejs.md index 28ea2cefb..9a7c2f94a 100644 --- a//lambda/latest/dg/lambda-nodejs.md +++ b//lambda/latest/dg/lambda-nodejs.md @@ -77 +77 @@ Node.js has a unique event loop model that causes its initialization behavior to -Some initialization tasks may run asynchronously. These asynchronous tasks are not guaranteed to complete execution prior to an invocation. For example, code that makes a network call to fetch a parameter from AWS Parameter Store may not be complete by the time Lambda executes the handler function. As a result, the variable may be null during an invocation. There can also be a delay between `INIT` and `INVOKE` which can trigger errors in time-sensitive operations. In particular, AWS service calls can rely on time-sensitive request signatures, resulting in service call failures if the call is not completed during `INIT` phase. +Some initialization tasks may run asynchronously. These asynchronous tasks are not guaranteed to complete execution prior to an invocation. For example, code that makes a network call to fetch a parameter from AWS Parameter Store may not be complete by the time Lambda executes the handler function. As a result, the variable may be null during an invocation. There can also be a delay between `INIT` and `INVOKE` which can trigger errors in time-sensitive operations. In particular, AWS service calls can rely on time-sensitive request signatures, resulting in service call failures if the call is not completed during the `INIT` phase.