chore(apigatewayv2): review readme

packages/@aws-cdk/aws-apigatewayv2-alpha/README.md

@@ -46,6 +46,8 @@ This module supports features under [API Gateway v2](https://docs.aws.amazon.com
 that lets users set up Websocket and HTTP APIs.
 REST APIs can be created using the `aws-cdk-lib/aws-apigateway` module.
 
+HTTP and Websocket APIs use the same Cloudformation resources under the hood. However, this module separates them into two separate constructs for a more efficient abstraction since there are a number of Cloudformation properties that specifically apply only to each type of API.
+
 ## HTTP API
 
 HTTP APIs enable creation of RESTful APIs that integrate with AWS Lambda functions, known as Lambda proxy integration,
@@ -65,16 +67,15 @@ integration, HTTP proxy integration and, AWS service integrations, also known as
 [Configuring integrations](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations.html).
 
 Integrations are available at the `aws-apigatewayv2-integrations` module and more information is available in that module.
-As an early example, the following code snippet configures a route `GET /books` with an HTTP proxy integration all
-configures all other HTTP method calls to `/books` to a lambda proxy.
+As an early example, we have a website for a bookstore where the following code snippet configures a route `GET /books` with an HTTP proxy integration. All other HTTP method calls to `/books` route to a default lambda proxy for the bookstore.
 
 ```ts
 import { HttpUrlIntegration, HttpLambdaIntegration } from '@aws-cdk/aws-apigatewayv2-integrations-alpha';
 
 const getBooksIntegration = new HttpUrlIntegration('GetBooksIntegration', 'https://get-books-proxy.example.com');
 
-declare const booksDefaultFn: lambda.Function;
-const booksDefaultIntegration = new HttpLambdaIntegration('BooksIntegration', booksDefaultFn);
+declare const bookStoreDefaultFn: lambda.Function;
+const bookStoreDefaultIntegration = new HttpLambdaIntegration('BooksIntegration', bookStoreDefaultFn);
 
 const httpApi = new apigwv2.HttpApi(this, 'HttpApi');
 
@@ -86,7 +87,7 @@ httpApi.addRoutes({
 httpApi.addRoutes({
   path: '/books',
   methods: [ apigwv2.HttpMethod.ANY ],
-  integration: booksDefaultIntegration,
+  integration: bookStoreDefaultIntegration,
 });
 ```
 

packages/@aws-cdk/aws-apigatewayv2-authorizers-alpha/README.md

@@ -39,9 +39,9 @@ API](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-acces
 
 ## HTTP APIs
 
-Access control for Http Apis is managed by restricting which routes can be invoked via.
+Access control for Http APIs is managed by restricting which routes can be invoked via.
 
-Authorizers and scopes can either be applied to the api, or specifically for each route.
+Authorizers and scopes can either be applied to the API, or specifically for each route.
 
 ### Default Authorization
 
@@ -150,7 +150,7 @@ api.addRoutes({
 
 #### User Pool Authorizer
 
-User Pool Authorizer is a type of JWT Authorizer that uses a Cognito user pool and app client to control who can access your Api. After a successful authorization from the app client, the generated access token will be used as the JWT.
+User Pool Authorizer is a type of JWT Authorizer that uses a Cognito user pool and app client to control who can access your API. After a successful authorization from the app client, the generated access token will be used as the JWT.
 
 Clients accessing an API that uses a user pool authorizer must first sign in to a user pool and obtain an identity or access token.
 They must then use this token in the specified `identitySource` for the API call. More information is available at [using Amazon Cognito user

packages/@aws-cdk/aws-apigatewayv2-integrations-alpha/README.md

@@ -225,3 +225,4 @@ webSocketApi.addRoute('sendmessage', {
   integration: new WebSocketLambdaIntegration('SendMessageIntegration', messageHandler),
 });
 ```
+Extra line so this shows up in the files changes for the API Review - delete later