Fix typo's

Author: npalm

content/posts/2021-12-15-run-lambda-local/index.md

@@ -37,11 +37,11 @@ _This post explains how to run and debug AWS Lambda's locally without mocking an
 
 ## The problem
 
-Imagine you are building an AWS serverless function. As a good developer you have designed and written your code with paradigms like clean code, TDD. Your code is clean, maintainable and well (unit) tested. But at the moment you deploying your function to the cloud, it does not work as you have expected. Would it not be great if you can locally run, debug and iterate fast. And when deploying to the cloud be 100% certain that your lambda will work smooth.
+Imagine you are building an AWS serverless function. As a good developer you have designed and written your code with paradigms like clean code and TDD. Your code is clean, maintainable and well (unit) tested. But the moment you deploy your function to the cloud, it does not work as you have expected. Would it not be great if you can locally run, debug and iterate fast. And when deploying to the cloud be 100% certain that your lambda will work smooth?
 
-So what is the problem. The real world is not so nicely isolated as your test environment for unit testing. There are no mocks, stubs, the environment could be different, the function is invoked differently and IAM permissions are applied. Of course, this is the difference mostly between a unit test and integration test environment.
+So what is the problem? The real world is not so nicely isolated as your test environment for unit testing. There are no mocks or stubs. The environment could be different. The function is invoked differently. And IAM permissions are applied once running in the cloud. Of course, this is the difference mostly between a unit test and integration test environment.
 
-Time to out how close can we get to behaviour in the real world, aka cloud while running as much locally.
+Time to find out how close can we get to behavior in the real world, aka cloud while running as much locally.
 
 ## Tools
 
@@ -57,7 +57,7 @@ For this post we use the following tools.
 
 ## A simple Lambda
 
-Let's first build a simple Lambda. We use TypeScript as language for the Lambda which requires a Node runtime environment for excution. This add an extra step between writing the code and running, we need to compile the TypeScript code to JavaScript.
+Let's first build a simple Lambda. We use TypeScript as language for the Lambda which requires a Node runtime environment for execution. This add an extra step between writing the code and running, we need to compile the TypeScript code to JavaScript.
 
 We write a [simple program](https://github.com/npalm/aws-lambda-run-local/blob/main/lambda/src/lambda.ts) that sends a message to a SQS queue, Amazon's Simple Queue Service. Actually it does not matter which AWS services we use. We only need integration points to the cloud, so we are also depending on the cloud services for local excution. For simplicity we limit ourselves to only one. 
 
@@ -67,13 +67,13 @@ Our tiny program will read the SQS queue url and a message from the environment.
 import { SendMessageCommand, SQSClient } from "@aws-sdk/client-sqs";
 import { Context, ScheduledEvent } from "aws-Lambda";
 
+const client = new SQSClient({});
+
 export async function handler(
   event: ScheduledEvent,
   context: Context
 ): Promise<void> {
 
-  const client = new SQSClient({});
-
   try {
 
     const queueUrl = getEnvVariable("QUEUE_URL");
@@ -126,7 +126,7 @@ The Lambda function above requires in terms of AWS the following resources.
 - [A SQS queue](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/welcome.html), the queue to which we publish message. Since the goal is to run the Lambda as realistic as possible, without any mocking, we need an actual SQS queue.
 - [An execution role](https://docs.aws.amazon.com/lambda/latest/dg/lambda-intro-execution-role.html), this is the role that defines which resources the Lambda can access. The Lambda needs to send messages to SQS. We also going to use this role locally.
 
-Today we have dozen ways to create cloud resources, manual via the web console, [AWS CloudFormation](https://aws.amazon.com/cloudformation/), [Terraform](https://www.terraform.io/), [AWS CDK](https://aws.amazon.com/cdk/), [Pulumi](https://www.pulumi.com/product/), [Serverless Framework](https://www.serverless.com/), e.g. Here we will use Terraform which is an IaC eco-system with no extra tooling to streamline Serverless development. When developing only a serverless application the SAM Framework, CDK or the Serverless Framework may seem a more logical choice. But using Terraform shows us how we can mix and match if we cannot chose every component.
+Today we have dozen of ways to create cloud resources, manually via the web console, [AWS CloudFormation](https://aws.amazon.com/cloudformation/), [Terraform](https://www.terraform.io/), [AWS CDK](https://aws.amazon.com/cdk/), [Pulumi](https://www.pulumi.com/product/), [Serverless Framework](https://www.serverless.com/), e.g. Here we will use Terraform which is an IaC eco-system with no extra tooling to streamline Serverless development. When developing only a serverless application the SAM Framework, CDK or the Serverless Framework may seem a more logical choice. But using Terraform shows us how we can mix and match if we cannot chose every component.
 
 Time to create the cloud resources with Terraform. This setup assumes you have an admin role. Clone the [repo](https://github.com/npalm/aws-lambda-run-local/tree/main/terraform) and cd in the Terraform directory to create the resources.
 
@@ -241,7 +241,7 @@ region=eu-west-1
 role_arn=arn:aws:iam::<ACCOUNT_ID>:role/test/blog-test
 ```
 
-As alterfnative of setting up a rol you can invoke the STS services to obtain credentials for the Lambda execution role.
+As alternative of setting up a role you can invoke the STS services to obtain credentials for the Lambda execution role.
 
 ```bash
 role=$(aws sts assume-role --role-arn "$role_arn" \