Amend RESTAPI examples

Author: julianwood

apigw-rest-api-lambda-dotnet/README.md

@@ -1,8 +1,8 @@
-# Hello World AWS Lambda and Amazon API Gateway REST API
+# Hello World AWS Lambda and Amazon API Gateway REST API (.NET)
 
 This project contains source code and supporting files for a serverless application that you can deploy with the AWS SAM CLI. It includes the following files and folders.
 
-- src/HelloWorld - Code for the application's Lambda function.
+- hello_world - Code for the application's Lambda function.
 - events - Invocation events that you can use to invoke the function.
 - template.yaml - A template that defines the application's AWS resources.
 
@@ -25,22 +25,21 @@ The AWS Toolkit is an open source plug-in for popular IDEs that uses the AWS SAM
 
 ## Deploy the sample application
 
-The Serverless Application Model Command Line Interface (SAM CLI) is an extension of the AWS CLI that adds functionality for building and testing Lambda applications. It uses Docker to run your functions in an Amazon Linux environment that matches Lambda. It can also emulate your application's build environment and API.
+The AWS Serverless Application Model Command Line Interface (AWS SAM CLI) is a framework for building and testing Lambda applications. It uses Docker to run your functions in an Amazon Linux environment that matches Lambda. It can also emulate your application's build environment and API.
 
 To use the AWS SAM CLI, you need the following tools.
 
 ### Requirements
 
 * AWS SAM CLI - [Install the SAM CLI](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-install.html)
-* .NET Core - [Install .NET Core](https://www.microsoft.com/net/download)
-* Docker - [Install Docker community edition](https://hub.docker.com/search/?type=edition&offering=community)
+* Docker - [Install Docker Desktop](https://hub.docker.com/search/?type=edition&offering=community)
 
 To build and deploy your application for the first time, run the following in your shell:
 
 ```bash
-$ cd apigw-rest-api-lambda-dotnet
-$ sam build --use-container
-$ sam deploy --guided
+cd apigw-rest-api-lambda-dotnet
+sam build --use-container
+sam deploy --guided
 ```
 
 The first command will build the source of your application. The second command will package and deploy your application to AWS, with a series of prompts:
@@ -50,30 +49,32 @@ The first command will build the source of your application. The second command
 * **Confirm changes before deploy**: If set to yes, any change sets will be shown to you before execution for manual review. If set to no, the AWS SAM CLI will automatically deploy application changes.
 * **HelloWorldFunction has no authentication. Is this okay? [y/N]:**: Select `y` for the purposes of this sample application. As a result, anyone will be able to call this example REST API without any form of authentication. For production applications, you should [enable authentication for the API Gateway](https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-control-access-to-api.html) using one of several available options and [follow the API Gateway security best practices](https://docs.aws.amazon.com/apigateway/latest/developerguide/security-best-practices.html). If `N` is selected for this question, this deployment will not succeed.
 * **Allow AWS SAM CLI IAM role creation**: Many AWS SAM templates, including this example, create AWS IAM roles required for the AWS Lambda function(s) included to access AWS services. By default, these are scoped down to minimum required permissions. To deploy an AWS CloudFormation stack which creates or modifies IAM roles, the `CAPABILITY_IAM` value for `capabilities` must be provided. If permission isn't provided through this prompt, to deploy this example you must explicitly pass `--capabilities CAPABILITY_IAM` to the `sam deploy` command.
-* **Save arguments to samconfig.toml**: If set to yes, your choices will be saved to a configuration file inside the project, so that in the future you can just re-run `sam deploy` without parameters to deploy changes to your application.
+* **Save arguments to samconfig.toml**: If set to yes, your choices will be saved to a configuration file inside the project.
+* 
+For future deploys, you can run `sam deploy` without parameters to deploy changes to your application.
 
-You can find your API Gateway Endpoint URL in the output values displayed after deployment.
+You can find your API Gateway endpoint URL in the output values displayed after deployment.
 
-## Use the AWS SAM CLI to test locally
+## Use AWS SAM CLI to test locally
 
-The SAM CLI installs dependencies defined in `src/HelloWorld.csproj`, creates a deployment package, and saves it in the `.aws-sam/build` folder.
+The AWS SAM CLI installs dependencies defined in `hello_world/package.json`, creates a deployment package, and saves it in the `.aws-sam/build` folder.
 
-Ypu can test a single function by invoking it directly with a test event. An event is a JSON document that represents the input that the function receives from the event source. Test events are included in the `events` folder in this project.
+You can test a single function by invoking it directly with a test event. An event is a JSON document that represents the input that the function receives from the event source. Test events are included in the `events` folder in this project.
 
 Run functions locally and invoke them with the `sam local invoke` command.
 
 ```bash
-$ sam local invoke HelloWorldFunction --event events/event.json
+sam local invoke HelloWorldFunction --event events/event.json
 ```
 
-The AWS SAM CLI can also emulate your application's API. Use the `sam local start-api` to run the API locally on port 3000.
+AWS SAM CLI can also emulate your application's API. Use the `sam local start-api` to run the API locally on port 3000.
 
 ```bash
-$ sam local start-api
-$ curl http://localhost:3000/
+sam local start-api
+curl http://localhost:3000/
 ```
 
-The AWS SAM CLI reads the application template to determine the API's routes and the functions they invoke. The `Events` property on each function's definition includes the route and method for each path.
+AWS SAM CLI reads the application template to determine the API's routes and the functions they invoke. The `Events` property on each function's definition includes the route and method for each path.
 
 ```yaml
       Events:
@@ -84,13 +85,13 @@ The AWS SAM CLI reads the application template to determine the API's routes and
             Method: get
 ```
 
-## Use the AWS SAM CLI to test remotely
+## Use AWS SAM CLI to test remotely
 After you have deployed your application, you can remotely invoke your Lambda function to test it in the cloud. 
 
 Invoke functions remotely with the `sam remote invoke` command.
 
 ```bash
-$ sam remote invoke HelloWorldFunction --event-file events/event.json
+sam remote invoke HelloWorldFunction --event-file events/event.json
 ```
 
 You can also go to the API Gateway endpoint URL that was output after the deployment of your application, which will similarly invoke your deployed Lambda function. 
@@ -101,12 +102,11 @@ To simplify troubleshooting, AWS SAM CLI has a command called `sam logs`. `sam l
 `NOTE`: This command works for all AWS Lambda functions; not just the ones you deploy using AWS SAM.
 
 ```bash
-$ sam logs -n HelloWorldFunction --stack-name "YOUR_STACK_NAME_HERE" --tail
+sam logs -n HelloWorldFunction --stack-name "YOUR_STACK_NAME_HERE" --tail
 ```
 
 You can find more information and examples about filtering Lambda function logs in the [AWS SAM CLI Documentation](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-logging.html).
 
-
 ## Cleanup
 
 To delete the sample application that you created, use the AWS CLI. Assuming you used your project name for the stack name, you can run the following:
@@ -117,4 +117,4 @@ $ sam delete
 
 ## Resources
 
-See the [AWS SAM developer guide](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/what-is-sam.html) for an introduction to SAM specification, the SAM CLI, and serverless application concepts.
+See the [AWS SAM developer guide](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/what-is-sam.html) for an introduction to AWS SAM specification, the AWS SAM CLI, and serverless application concepts.

apigw-rest-api-lambda-dotnet/apigw-rest-api-lambda-dotnet.json

@@ -1,14 +1,14 @@
 {
     "title": "Hello World AWS Lambda and Amazon API Gateway REST API",
-    "description": "Create a simple Lambda Function connected to a REST API.",
+    "description": "Create a simple Lambda function connected to a REST API.",
     "language": ".NET",
     "level": "200",
     "framework": "SAM",
     "introBox": {
       "headline": "How it works",
       "text": [
-        "This sample project demonstrates how to trigger a simple Lambda function using a REST API.",
-        "This pattern deploys one Lambda Function, andn one API Gateway REST API."
+        "This sample project shows how to trigger a simple Lambda function using a REST API.",
+        "This pattern deploys one Lambda function and one API Gateway REST API."
       ]
     },
     "gitHub": {
@@ -22,7 +22,7 @@
     "resources": {
       "bullets": [
         {
-          "text": "Trigger Lambda with a REST API",
+          "text": "Invoking a Lambda function using an Amazon API Gateway endpoint",
           "link": "https://docs.aws.amazon.com/lambda/latest/dg/services-apigateway.html"
         },
         {

apigw-rest-api-lambda-dotnet/example-pattern.json

@@ -1,7 +1,9 @@
 AWSTemplateFormatVersion: '2010-09-09'
 Transform: AWS::Serverless-2016-10-31
 Description: >
-  Sample SAM Template for REST API Lambda Hello World
+  Hello World AWS Lambda and Amazon API Gateway REST API
+
+  Sample AWS SAM template to create a simple Lambda function connected to a REST API.
 
 # More info about Globals: https://github.com/awslabs/serverless-application-model/blob/master/docs/globals.rst
 Globals: