edits to getting started

Author: nficano

README.rst

@@ -34,38 +34,33 @@ Requirements
 * Virtualenv (~15.0.0)
 * Virtualenvwrapper (~4.7.1)
 
-Installation
-============
+Getting Started
+===============
 
-Create a new folder for your project and create a virtualenv.
+Begin by creating a new virtualenv and project folder.
 
 .. code:: bash
 
-    $ mkdir my_microservice
     $ mkvirtualenv my_microservice
+    (my_microservice) $ mkdir my_microservice
 
-Next Download using pip via pypi.
+Next, download *Python-Lambda* using pip via pypi.
 
 .. code:: bash
 
     (my_microservice) $ pip install python-lambda
 
-Getting Started
-===============
-
-The following will walk you through writing your first microservice with *Python-lambda*.
-
 From your ``my_microservice`` directory, run the following to bootstrap your project.
 
 .. code:: bash
 
     (my_microservice) $ lambda init
 
-If you look at the directory you will see four files were created: ``event.json``, ``__init__.py``, ``service.py``, and ``config.yaml``.
+This will create the following files: ``event.json``, ``__init__.py``, ``service.py``, and ``config.yaml``.
 
-Let's begin by taking a look at ``config.yaml`` in your favorite text editor. For the purpose of this tutorial, the only thing required to be entered is ``aws_access_key_id`` and ``aws_secret_access_key``. You can find these by logging into the AWS management console.
+Let's begin by opening ``config.yaml`` in the text editor of your choice. For the purpose of this tutorial, the only required information is ``aws_access_key_id`` and ``aws_secret_access_key``. You can find these by logging into the AWS management console.
 
-Next let's open ``service.py``, in it you'll find the following function:
+Next let's open ``service.py``, in here you'll find the following function:
 
 .. code:: python
 
@@ -77,28 +72,30 @@ Next let's open ``service.py``, in it you'll find the following function:
         return e + pi
 
 
-This is the hander function; this is what AWS Lambda will invoke in response to an event. You will notice that in the sample code provided ``e`` and ``pi`` are values looked up in a ``dict``. AWS Lambda uses the ``event`` parameter to pass in event data to the handler.
+This is the hander function; this is the function AWS Lambda will invoke in response to an event. You will notice that in the sample code ``e`` and ``pi`` are values in a ``dict``. AWS Lambda uses the ``event`` parameter to pass in event data to the handler.
 
 So if for example your function is responding to an http request, ``event`` will be the ``POST`` JSON data and if your function returns something, the contents will be in your http response payload.
 
-Now let's open the ``event.json`` file. Here you'll find the values of ``e`` and ``pi`` that are being referenced in the sample code.
+Next let's open the ``event.json`` file. Here you'll find the values of ``e`` and ``pi`` that are being referenced in the sample code.
 
 If you now try and run:
 
 .. code:: bash
 
     (my_microservice) $ lambda invoke
 
-"your test handler was successfully invoked!" should print out in your console.  You've probably already put together that the ``lambda invoke`` command passes the values stored in the ``event.json`` file to your function.
+"your test handler was successfully invoked!" should print out in your console.
+
+As you probably put together, the ``lambda invoke`` command grabs the values stored in the ``event.json`` file and passes them to your function.
 
-The ``event.json`` file should help you develop your Lambda service locally.
+The ``event.json`` file should help you develop your Lambda service locally. You can specify an alternate ``event.json`` file by passing the ``--event=<filename>.json`` argument to ``lambda invoke``.
 
-When you're ready to deploy your code to lambda simply run:
+When you're ready to deploy your code to Lambda simply run:
 
 .. code:: bash
 
     (my_microservice) $ lambda deploy
 
-The deploy script will evaluate your virtualenv and identify your project dependencies (actually just pip freeze). It will package these up along with your handler function to a zip file that it then uploads to AWS Lambda.
+The deploy script will evaluate your virtualenv and identify your project dependencies. It will package these up along with your handler function to a zip file that it then uploads to AWS Lambda.
 
-You can now log into the AWS Lambda management console to verify the code deployed successfully and wire it up to respond to an event.
+You can now log into the AWS Lambda management console to verify the code deployed successfully.