Confusing lambda function name

[vhermecz]

While the function appears with the name cors-proxy, if you want to see AWS logs, you need to use sls logs -s dev -f lambda -t.
According to the doc, the name serverless uses is the direct child of the functions property, thus in this case lambda.
While this might be an error/bug in Serverless itself, would be nice to see how to query the aws logs in readme.md

The original error I got was:

$ node_modules/.bin/serverless logs -s dev -f cors-proxy -t
 
  Serverless Error ---------------------------------------
 
  Function "cors-proxy" doesn't exist in this Service

[Glifery]

Feel free to contribute!