AWS lexv2 documentation change
Summary
Removed 'Amazon Lex V2' product name references and simplified link text in Lambda function documentation
Security assessment
Changes are editorial in nature, removing product name repetition and simplifying documentation links. No security-related content was added or modified.
Diff
diff --git a/lexv2/latest/dg/paths-code-hook.md b/lexv2/latest/dg/paths-code-hook.md index 28260662e..7d45d5cf4 100644 --- a//lexv2/latest/dg/paths-code-hook.md +++ b//lexv2/latest/dg/paths-code-hook.md @@ -7 +7 @@ -At each step in the conversation when Amazon Lex V2 sends a message to the user, you can use a Lambda function as the next step in the conversation. You can use the function to implement business logic based on current state of the conversation. +At each step in the conversation when sends a message to the user, you can use a Lambda function as the next step in the conversation. You can use the function to implement business logic based on current state of the conversation. @@ -9 +9 @@ At each step in the conversation when Amazon Lex V2 sends a message to the user, -The Lambda function that runs is associated with the bot alias that you are using. To invoke Lambda function across all dialog code hooks in your intent, you must select **Use a Lambda function for initializing and validation** for the intent. For more information on choosing a Lambda function, see [Creating an AWS Lambda function for your Amazon Lex V2 bot](./lambda-attach.html). +The Lambda function that runs is associated with the bot alias that you are using. To invoke Lambda function across all dialog code hooks in your intent, you must select **Use a Lambda function for initializing and validation** for the intent. For more information on choosing a Lambda function, see [Creating an AWS Lambda function for your bot](./lambda-attach.html).