Adds final thoughts and ref links

source/high-availability/aws/index.html.md

@@ -165,14 +165,14 @@ subnet and security group and
 ## Initiate AMI
 We are going to launch an EC2 instance and bake an image so that we can 
-later use it for autoscaling. We'll also take this opportunity to add an 
+later use it for auto scaling. We'll also take this opportunity to add an 
 extension to our RDS through this temporary EC2 instance.
 ### EC2 Instance 
 Look for the EC2 option and choose to create an instance. We'll need at 
 least a t2.medium type and for this article we'll choose an Ubuntu 14.04
-HVM 64-bit. In the Configure Instance section choose our gitlab VPC and 
+HVM 64-bit. In the Configure Instance section choose our GitLab VPC and 
 a public subnet. I'd choose at least 10GB of storage. 
  
 In the security group we'll create a new one considering that we need to 
@@ -200,7 +200,7 @@ and add a custom TCP rule for port 6379 accessible within itself.
 ### Install GitLab 
 To connect through SSH you will need to have the `pem` file which you 
-chose available and with the correct permissions sich as `400`. 
+chose available and with the correct permissions such as `400`. 
 After accessing your server don't forget to update and install the nfs 
 client.
@@ -292,7 +292,7 @@ momentarily as we'll be using the image we where creating. We will keep
 the Enable Cross-Zone and Enable Connection Draining active.
 After we finish creating the Load Balancer we can re visit our Security 
-Groups to improve access only through the ELB and any other requiremnt 
+Groups to improve access only through the ELB and any other requirement 
 you might have.
 *** 
@@ -314,8 +314,8 @@ On the security group section we can chosse our existing
 After this is launched we are able to start creating our Auto Scaling 
 Group. Start by giving it a name and assinging it our VPC and private 
 subnets. We also want to always start with two instances and if you 
-scroll down to Advanced Details we can choose to Revie traffic from ELBs. 
-LEts enable that option and select our ELB. We also want to use the ELB's 
+scroll down to Advanced Details we can choose to receive traffic from ELBs. 
+Lets enable that option and select our ELB. We also want to use the ELB's 
 health check.
 ![Network and Security](/images/high-availability/auto-scaling-det.png)
@@ -334,5 +334,18 @@ You'll notice that after we save this AWS starts launching our two
 instances in different AZs and without a public IP which is exactly what 
 we where aiming for. 
-
+*** 
+## Final Thoughts
+ 
+After you're done with the policies section have some fun trying to break 
+instances. You should be able to see how the Auto Scaling Group and the 
+EC2 screen start bringing them up again. 
+
+High Availability is a very big area, we went mostly through scaling and 
+some redundancy options but it might also imply Geographic replication. 
+There is a lot of ground yet to cover so have a read through these other 
+resources and feel free to open an issue to request additional material.
+ 
+ * [GitLab High Availability](http://docs.gitlab.com/ce/administration/high_availability/README.html#sts=High Availability)
+ * [GitLab Geo](http://docs.gitlab.com/ee/gitlab-geo/README.html)