documentation update

Author: Chandrashekar

docs/partner_editable/additional_info.adoc

@@ -32,7 +32,7 @@ image:../images/image7.png[Figure 4,width=648,height=198]
 
 image:../images/image8.png[Figure 5,width=646,height=348]
 
-*Figure 5: Checking for S3 bucket updates after a commit*
+*Figure 4: Checking for S3 bucket updates after a commit*
 
 === Best Practices
 

docs/partner_editable/architecture.adoc

@@ -7,8 +7,10 @@ Deploying this Quick Start builds the following environment in the AWS Cloud.
 [link=images/architecture_diagram.png]
 image::../images/image3.png[Architecture,width=100%,height=100%]
 
+
 *Figure 2: Webhook endpoint architecture on AWS*
 
+
 The Quick Start deployment sets up a serverless AWS Cloud environment that includes the following components.
 
 * An API Gateway endpoint to accept the webhook requests from Git.

docs/partner_editable/deploy_steps.adoc

@@ -30,10 +30,11 @@ After you have successfully deployed the Quick Start, you can configure the serv
 
 image:../images/image5.png[Figure 4,width=701,height=222]
 
-*Figure 4: Outputs tab after deployment*
+
+*Figure 3: Outputs tab after deployment*
+
 
 * *GitPullWebHookApi* is the webhook endpoint to use if you opt for the Git pull method described in the link:#webhook-endpoints[Webhook Endpoints] section of this guide.
-// * *ZipDownloadWebHookApi* is the webhook endpoint to use if you opt for the zip download method described in the link:#webhook-endpoints[Webhook Endpoints] section of this guide.
 * *PublicSSHKey* is the public SSH key that you use to connect to your repository if you’re using the Git pull endpoint. This key can be configured as a read-only machine user or as a deployment key in your Git service.
 
 The exact process to set up webhooks differs from service to service. For step-by-step instructions, consult your Git service’s documentation.

docs/partner_editable/faq_troubleshooting.adoc

@@ -17,6 +17,12 @@ If your commits are not being pushed through to Amazon S3, check the following:
 * In your Git service’s webhooks configuration, check that your configured security parameters and the endpoint are correct. Consult the Git service documentation for detailed guidance on configuration.
 * Check the Lambda logs for errors. These are stored in Amazon CloudWatch Logs. To access the logs, open the endpoint’s Lambda function in the AWS console, navigate to the *Monitoring* tab, and then choose *View logs in CloudWatch*.
 
+For additional information, see https://docs.aws.amazon.com/lambda/latest/dg/lambda-troubleshooting.html[Troubleshooting issues in AWS Lambda^] on the AWS website.
+
+* Check the AWS CodeBuild project logs for errors. These are stored in Amazon CloudWatch Logs. To access the logs, open the endpoint’s CodeBuild Build Project in the AWS console, select a *Build run* and click on the hyperlink and navigate to the *Build logs* tab to see the build execution logs.
+
+For additional information, see https://docs.aws.amazon.com/codebuild/latest/userguide/troubleshooting.html[Troubleshooting AWS CodeBuild^] on the AWS website.
+
 == Additional Resources
 
 === AWS services

docs/partner_editable/licenses.adoc

@@ -1 +1 @@
-The Quick Start provides an Amazon API Gateway endpoint and several Lambda functions to handle the download, zipping, and deployment of code to Amazon S3. AWS CodePipeline carries a cost for each active pipeline; see https://aws.amazon.com/codepipeline/pricing/[AWS CodePipeline pricing]. Depending on your configuration, the Quick Start may deploy an AWS Key Management Service (AWS KMS) key; for pricing, see https://aws.amazon.com/kms/pricing/[AWS Key Management Service pricing]. API Gateway, Amazon S3, and Lambda costs vary depending on how often you commit code to your repository; each commit triggers a request to the Lambda execution in API Gateway; for details, see the pricing pages for https://aws.amazon.com/api-gateway/pricing/[API Gateway], https://aws.amazon.com/s3/pricing/[Amazon S3], and https://aws.amazon.com/lambda/pricing/[Lambda].
+The Quick Start provides an Amazon API Gateway endpoint, several Lambda functions and an AWS CodeBuild project to handle the download, zipping, and deployment of code to Amazon S3. AWS CodePipeline carries a cost for each active pipeline; see https://aws.amazon.com/codepipeline/pricing/[AWS CodePipeline pricing]. Depending on your configuration, the Quick Start may deploy an AWS Key Management Service (AWS KMS) key; for pricing, see https://aws.amazon.com/kms/pricing/[AWS Key Management Service pricing]. API Gateway, Amazon S3, Lambda, and AWS CodeBuild costs vary depending on how often you commit code to your repository; each commit triggers a request to the Lambda execution in API Gateway; for details, see the pricing pages for https://aws.amazon.com/api-gateway/pricing/[API Gateway], https://aws.amazon.com/s3/pricing/[Amazon S3], https://aws.amazon.com/lambda/pricing/[Lambda] and https://aws.amazon.com/codebuild/pricing/[codebuild] .

docs/partner_editable/product_description.adoc

@@ -5,6 +5,6 @@ image:../images/image2.png[image,width=647,height=266]
 
 *Figure 1: Using webhooks for code commits*
 
-This Quick Start implements the required code to trigger a Lambda function that zips up the code in your repository and places the .zip file in Amazon S3. When this function is triggered by a Git webhook, it provides a convenient way to bridge Git services with AWS services like AWS CodePipeline and AWS CodeBuild, so that builds and pipeline executions occur automatically when you commit your code to a Git repository. Linking your existing code repositories to the AWS Cloud in this way enables your code to be continuously integrated, tested, built, and deployed on the AWS Cloud with each change.
+This Quick Start implements the required code to trigger a Lambda function and an AWS CodeBuild project working together that zips up the code in your repository and places the .zip file in Amazon S3. When this function is triggered by a Git webhook, it provides a convenient way to bridge Git services with AWS services like AWS CodePipeline and AWS CodeBuild, so that builds and pipeline executions occur automatically when you commit your code to a Git repository. Linking your existing code repositories to the AWS Cloud in this way enables your code to be continuously integrated, tested, built, and deployed on the AWS Cloud with each change.
 
-NOTE: The Lambda functions that are deployed by this Quick Start must be able to communicate with your Git repository. For example, you can use a SaaS-based Git service that Lambda can reach through the internet.
+NOTE: The AWS CodeBuild Project deployed by this Quick Start must be able to communicate with your Git repository. For example, you can use a SaaS-based Git service that AWS CodeBuild can reach through the internet.