Skip to content

Commit

Permalink
typo
Browse files Browse the repository at this point in the history
  • Loading branch information
gojko committed Jul 21, 2016
1 parent 6b9fe89 commit b7b472d
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion FAQ.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ AWS Lambda and API Gateway are incredibly flexible, but they can be tedious to s

Claudia automates all those steps for you, and uses the standard NPM packaging conventions, so you do not have to change your project layout. Just call `claudia create` and Claudia will pack up and post-process your code, grab all the dependencies, clean up irrelevant resources, upload to Lambda, set-up web APIs, and update version aliases. In addition, Claudia automatically configures the Lambda function for commonly useful tasks, allowing `console.log` to pipe to CloudWatch, helping you add event sources with correct IAM privileges and manage different versions for production, development and testing easily.

[Claudia API Builder](https://github.com/claudiajs/claudia-api-builder) helps you use API Gateway as if it was a typical JavaScript web server, so you do not have to learn Swagger or manage separate interface definition files. Claudia automatically sets up API Gateway resources the way JavaScript developers expect them to work, enabling CORS for all endpoints (so your users' browsers can call the APIs directly), making query string, form post and request headers directly available (instead of having to specify API Gateway models and templates), and routing errors to HTTP response code 500 (instead of the default 200 which breaks Promise-like request libraries).
[Claudia API Builder](https://github.com/claudiajs/claudia-api-builder) helps you use API Gateway as if it were a typical JavaScript web server, so you do not have to learn Swagger or manage separate interface definition files. Claudia automatically sets up API Gateway resources the way JavaScript developers expect them to work, enabling CORS for all endpoints (so your users' browsers can call the APIs directly), making query string, form post and request headers directly available (instead of having to specify API Gateway models and templates), and routing errors to HTTP response code 500 (instead of the default 200 which breaks Promise-like request libraries).

## How does it compare to ...?

Expand Down

0 comments on commit b7b472d

Please sign in to comment.