Merge pull request #57 from DennisTraub/aliases-intro

Fixed typo and formatting in aliases-intro.md

Author: mwunderl

doc_source/aliases-intro.md

@@ -8,6 +8,7 @@ AWS Lambda aliases enable the following use cases:
 + **Easier support for promotion of new versions of Lambda functions and rollback when needed** – After initially creating a Lambda function \(the `$LATEST` version\), you can publish a version 1 of it\. By creating an alias named PROD that points to version 1, you can now use the PROD alias to invoke version 1 of the Lambda function\. 
 
   Now, you can update the code \(the `$LATEST` version\) with all of your improvements, and then publish another stable and improved version \(version 2\)\. You can promote version 2 to production by remapping the PROD alias so that it points to version 2\. If you find something wrong, you can easily roll back the production version to version 1 by remapping the PROD alias so that it points to version 1\.
+
 + **Simplify management of event source mappings** – Instead of using Amazon Resource Names \(ARNs\) for Lambda function in event source mappings, you can use an alias ARN\. This approach means that you don't need to update your event source mappings when you promote a new version or roll back to a previous version\. 
 
 Both the Lambda function and alias are AWS Lambda resources, and like all other AWS resources they both have unique ARNs\. The following example shows a Lambda function \(the `$LATEST` version\), with one published version\. Each version has an alias pointing to it\.
@@ -49,7 +50,7 @@ You publish a version from the `$LATEST` and have another alias \(BETA\) point t
 
 ![\[Image NOT FOUND\]](http://docs.aws.amazon.com/lambda/latest/dg/images/alias_scenario_2_20.png)
 
-**You next promote the Lambda function version in production to work with event sources in production environment\.**  
+**You then promote the Lambda function version in production to work with event sources in production environment\.**  
 After testing the BETA version of the function, you can define the production version by creating an alias that maps to version 1\. In this approach, you point your production event sources to this specific version\. You do this by creating a PROD alias and using the PROD alias ARN in all of your production event source mappings\.  
 
 ![\[Image NOT FOUND\]](http://docs.aws.amazon.com/lambda/latest/dg/images/alias_scenario_2_30.png)