AWS serverless documentation change
Summary
Updated API request workflow steps with numbering, verb tense corrections, and added 'Users Table' specificity
Security assessment
Changes improve documentation structure and clarity but do not address security issues or document security features
Diff
diff --git a/serverless/latest/devguide/starter-apigw.md index 9ad580b20..f782dc6d5 100644 --- a/serverless/latest/devguide/starter-apigw.md +++ b/serverless/latest/devguide/starter-apigw.md @@ -55 +55 @@ Let’s start with a high level work flow for an API request, pictured in the fo - * API HTTP request for a user is received and authentication is checked + 1. API HTTP request for a user is received and authentication is verified. @@ -57 +57 @@ Let’s start with a high level work flow for an API request, pictured in the fo - * The call matched the API `GET` method and `users` resource, which is integrated with a get-users Lambda function + 2. The call matches the API `GET` method and `users` resource, which is integrated with get-users Lambda function. @@ -59 +59 @@ Let’s start with a high level work flow for an API request, pictured in the fo - * Permissions were verified before invoking the AWS resource + 3. Permissions are verified before invoking the AWS resource. @@ -61 +61 @@ Let’s start with a high level work flow for an API request, pictured in the fo - * Lambda function sends queries to retrieve items from a data store + 4. Lambda function sends queries to retrieve items from a Users Table data store. @@ -63 +63 @@ Let’s start with a high level work flow for an API request, pictured in the fo - * Data is wrapped in an HTTP response to be returned to the client + 5. Data is wrapped in an HTTP response to be returned to the client.