cleaning up some HoL references to DockerCon setup

ManoMarks · ManoMarks · commit a1d53ea4c53d · 2017-05-12T13:10:01.000-07:00
diff --git a/dockercon-us-2016/README.md b/dockercon-us-2016/README.md
diff --git a/dockercon-us-2017/README.md b/dockercon-us-2017/README.md
@@ -135,10 +135,3 @@ This lab is aimed at ops and system admins. It steps through packaging an ASP.NE
 > - Package an existing ASP.NET MSI so the app runs in Docker, without any application changes.
 > - Create an upgraded package with application updates and Windows patches.
 > - Update and rollback the running application in a production environment with zero downtime.
-
-
----
-
-## Contribute Your Own Labs
-
-If you have an awesome tutorial/lab and would like to add it here. Please open a PR. We would love to add more exciting tutorials to the list!
diff --git a/dockercon-us-2017/docker-cloud/README.md b/dockercon-us-2017/docker-cloud/README.md
@@ -7,7 +7,7 @@
 
 In this lab, you will learn how to configure a continuous integration (CI) pipeline for a web application using Docker Cloud's automated build features. You will complete the following tasks as part of the lab:
 
-> - [Task 0: Configure the prerequisites](#prerequisits)
+> - [Task 0: Configure the prerequisites](#prerequisites)
 > - [Task 1: Configure Docker Cloud to Automatically Build Docker Images](#deploy_app)
 >  - [Task 1.1: Configure Docker Cloud Autobuilds](#autobuild)
 >  - [Task 1.2: Trigger an Autobuild](#test_autobuild)
@@ -30,9 +30,9 @@ You may be asked to SSH into various nodes. These nodes are referred to as **nod
 In order to complete this lab, you will need the following:
 
 - A Docker ID
-- A management host (for this lab you'll use Linux **node0**)
+- A management host (for this lab you'll need a Linux named **node0**)
 - A GitHub account
-- Git installed (It hould already be installed in your Azure VM)
+- Git installed
 
 ### Obtain a Docker ID
 
@@ -88,7 +88,7 @@ Now that you've got Docker Cloud linked to your GitHub account, we'll start by f
 
 Next, we'll clone the repository into our local Docker environment. The following commands will be executed in the terminal or command window from Linux **node0**
 
-1. If you have not already log into your Azure VM. For example (be sure to use the actual node name supplied in your email):
+1. If you have not already, log into your Azure VM. For example:
 
 	```ssh ubuntu@node0-gvs0mgc0216.southcentralus.cloudapp.azure.com```
 
diff --git a/dockercon-us-2017/docker-enterprise/README.md b/dockercon-us-2017/docker-enterprise/README.md
@@ -57,7 +57,7 @@ The following task will guide you through how to create a UCP cluster on your ho
 
 ### <a name="task1.1"></a>Task 1.1: Installing the UCP Manager
 
-1. Log in to `node0` of the three nodes you have been given for this lab.  The username for all of the Linux nodes is `ubuntu` and the node will have a unique password that should be in your email. You may be prompted whether you want to continue. Answer `yes` and then enter the password.
+1. Log in to `node0` of the three nodes you have been given for this lab. You may be prompted whether you want to continue. Answer `yes` and then enter the password.
 
 ```
 $ ssh ubuntu@node0-smwqii1akqh.southcentralus.cloudapp.azure.com
diff --git a/dockercon-us-2017/docker-networking/README.md b/dockercon-us-2017/docker-networking/README.md
@@ -22,7 +22,7 @@ When you encounter a phrase in between `<` and `>`  you are meant to substitute
 
 For instance if you see `ssh <username>@<hostname>` you would actually type something like `ssh ubuntu@node0-a.ivaf2i2atqouppoxund0tvddsa.jx.internal.cloudapp.net`
 
-You will be asked to SSH into various nodes. These nodes are referred to as **node0-a**, **node1-b**, **node2-c**, etc. These tags correspond to the very beginning of the hostnames found on the hands on labs welcome card you were given. 
+You will be asked to SSH into various nodes. These nodes are referred to as **node0-a**, **node1-b**, **node2-c**, etc.
 
 ## <a name="prerequisites"></a>Prerequisites
 
@@ -830,4 +830,4 @@ Lets also run `docker swarm leave --force` on **node1-b**.
 $ docker swarm leave --force
 ```
 
-Congratulations! You've completed this lab. Feel free to try any of the other labs.
+Congratulations! You've completed this lab!
diff --git a/dockercon-us-2017/docker-orchestration/README.md b/dockercon-us-2017/docker-orchestration/README.md
@@ -23,7 +23,7 @@ When you encounter a phrase in between `<` and `>`  you are meant to substitute
 
 For instance if you see `ssh <username>@<hostname>` you would actually type something like `ssh ubuntu@node0-a.ivaf2i2atqouppoxund0tvddsa.jx.internal.cloudapp.net`
 
-You will be asked to SSH into various nodes. These nodes are referred to as **node0-a**, **node1-b**, **node2-c**, etc. These tags correspond to the very beginning of the hostnames found on the hands on labs welcome card you were given. 
+You will be asked to SSH into various nodes. These nodes are referred to as **node0-a**, **node1-b**, **node2-c**, etc. 
 
 ## <a name="prerequisites"></a>Prerequisites
 
@@ -230,7 +230,7 @@ You will perform the following procedure from **node0-a**.
 
 Our `sleep` application is becoming very popular on the internet (due to hitting Reddit and HN). People just love it. So, you are going to have to scale your application to meet peak demand. You will have to do this across multiple hosts for high availability too. We will use the concept of *Services* to scale our application easily and manage many containers as a single entity.
 
-> *Services* are a new concept in Docker 1.12. They work with swarms and are intended for long-running containers.
+> *Services* were a new concept in Docker 1.12. They work with swarms and are intended for long-running containers.
 
 You will perform this procedure from **node0-a**.
 
@@ -430,4 +430,4 @@ Finally, run `docker swarm leave --force` on **node2-c**.
 $ docker swarm leave --force
 ```
 
-Congratulations! You've completed this lab. You now know how to build a swarm, deploy applications as collections of services, and scale individual services up and down. Feel free to try any of the other labs.
+Congratulations! You've completed this lab. You now know how to build a swarm, deploy applications as collections of services, and scale individual services up and down.
diff --git a/dockercon-us-2017/windows-101/README.md b/dockercon-us-2017/windows-101/README.md
@@ -28,11 +28,11 @@ When you encounter a phrase in between `<` and `>`  you are meant to substitute
 
 For instance if you see `$ip = <ip-address>` you would actually type something like `$ip = '10.0.0.4'`
 
-You will be asked to RDP into various servers. You will find the actual server names to use in your welcome email. 
+You will be asked to RDP into various servers. 
 
 ## <a name="prerequisites"></a>Prerequisites
 
-You will be provided a set of Windows Server 2016 virtual machines running in Azure, which are already configured with Docker and the Windows base images. You do not need Docker running on your laptop, but you will need a Remote Desktop client to connect to the VMs. 
+You will need a set of Windows Server 2016 virtual machines running in Azure, which are already configured with Docker and the Windows base images. You do not need Docker running on your laptop, but you will need a Remote Desktop client to connect to the VMs. 
 
 - Windows - use the built-in Remote Desktop Connection app.
 - Mac - install [Microsoft Remote Desktop](https://itunes.apple.com/us/app/microsoft-remote-desktop/id715768417?mt=12) from the app store.
diff --git a/dockercon-us-2017/windows-modernize-aspnet-dev/README.md b/dockercon-us-2017/windows-modernize-aspnet-dev/README.md
@@ -43,11 +43,11 @@ When you encounter a phrase in between `<` and `>`  you are meant to substitute
 
 For instance if you see `$ip = <ip-address>` you would actually type something like `$ip = '10.0.0.4'`
 
-You will be asked to RDP into various servers. You will find the actual server names to use in your welcome email. 
+You will be asked to RDP into various servers.
 
 ## <a name="prerequisites"></a>Prerequisites
 
-You will be provided a set of Windows Server 2016 virtual machines running in Azure, which are already configured with Docker and the Windows base images. You do not need Docker running on your laptop, but you will need a Remote Desktop client to connect to the VMs. 
+You need a set of Windows Server 2016 virtual machines running in Azure, which are already configured with Docker and the Windows base images. You do not need Docker running on your laptop, but you will need a Remote Desktop client to connect to the VMs. 
 
 - Windows - use the built-in Remote Desktop Connection app.
 - Mac - install [Microsoft Remote Desktop](https://itunes.apple.com/us/app/microsoft-remote-desktop/id715768417?mt=12) from the app store.
diff --git a/dockercon-us-2017/windows-modernize-aspnet-ops/README.md b/dockercon-us-2017/windows-modernize-aspnet-ops/README.md
@@ -46,7 +46,7 @@ You will be asked to RDP into various servers. You will find the actual server n
 
 ## <a name="prerequisites"></a>Prerequisites
 
-You will be provided a set of Windows Server 2016 virtual machines running in Azure, which are already configured with Docker and the Windows base images. You do not need Docker running on your laptop, but you will need a Remote Desktop client to connect to the VMs. 
+You will need a set of Windows Server 2016 virtual machines running in Azure, which are already configured with Docker and the Windows base images. You do not need Docker running on your laptop, but you will need a Remote Desktop client to connect to the VMs. 
 
 - Windows - use the built-in Remote Desktop Connection app.
 - Mac - install [Microsoft Remote Desktop](https://itunes.apple.com/us/app/microsoft-remote-desktop/id715768417?mt=12) from the app store.
