stephen feedback

content/en/deployment/lambda/overview/index.md

@@ -307,7 +307,7 @@ A deployment strategy is the method by which CD-as-a-Service deploys your change
 For AWS Lambda, CD-as-a-Service supports a canary deployment strategy, which involves releasing a new software version to a small subset of users or systems while leaving the majority on the current version. This strategy allows for real-world testing and monitoring of the new version's performance and stability. 
 If the canary users experience positive results, the new version can be gradually rolled out to a wider audience.
 
-This example deploys 100% to the target. You'd use this `allAtOnce` strategy to initially deploy your function to AWS Lambda when the function does not exist in the AWS Lambda console.
+This example **routes 100% of traffic** to the **new version**. You’d use this `allAtOnce`` strategy to initially deploy your function to AWS Lambda when the function does not exist in the AWS Lambda console. **This strategy is also useful in non-production environments such as staging.**
 
 ```yaml
 strategies:

content/en/reference/deployment/config-file/traffic-management.md

@@ -20,9 +20,9 @@ trafficManagement:
         aliasName: <function-alias>
 ```
 
-* `targets`: the target name
+* `targets`: the list of targets using this alias
 * `function`: This is the same value as `artifacts.functionName` and `providerOptions.lambda.name`. See {{< linkWithTitle "reference/deployment/config-file/artifacts.md" >}} for details on those sections.
-* `aliasName`: The alias name, such as "latest-version". Your function's alias must already exist in the AWS Lambda console.
+* `aliasName`: The alias name, such as "live-version". Your function's alias must already exist in the AWS Lambda console.
 
 This example declares a traffic split canary strategy. You must declare your function's alias for each deployment target that uses the traffic split strategy.