From 4374fa7b8cd76e7cd738b6d495eb36b88ee9bf1f Mon Sep 17 00:00:00 2001 From: Colin Eberhardt Date: Wed, 10 May 2017 06:22:16 +0100 Subject: [PATCH] Fixed typo - Labmda => Lambda --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index db241c89..669d5d7e 100644 --- a/README.md +++ b/README.md @@ -36,7 +36,7 @@ $ node-lambda deploy #### setup -Initializes the `event.json`, `context.json`, `.env`, `deploy.env` files, and `event_sources.json` files. `event.json` is where you mock your event. `context.json` is where you can add additional mock data to the context passed to your lambda function. `.env` is where you place your deployment configuration. `deploy.env` has the same format as `.env`, but is used for holding any environment/config variables that you need to be deployed with your code to Lambda but you don't want in version control (e.g. DB connection info). `event_sources.json` is used to set the event source of the Labmda function (Not all event sources available in Lambda are supported). +Initializes the `event.json`, `context.json`, `.env`, `deploy.env` files, and `event_sources.json` files. `event.json` is where you mock your event. `context.json` is where you can add additional mock data to the context passed to your lambda function. `.env` is where you place your deployment configuration. `deploy.env` has the same format as `.env`, but is used for holding any environment/config variables that you need to be deployed with your code to Lambda but you don't want in version control (e.g. DB connection info). `event_sources.json` is used to set the event source of the Lambda function (Not all event sources available in Lambda are supported). ``` $ node-lambda setup --help