Updates for 2.2.2 compatability from user testing

labs/CiscoContainerPlatform-101/2.md

@@ -3,7 +3,7 @@ Cisco Container Platform 101
 # 2. Provider Settings and VIP Pools
 
 Clicking around the Cisco Cloud Platform UI, you'll notice a menu to the left.
-Here, an admin can configure users and groups (including Active Directory login authentication, allowing access to clusters based on the users AD group.) and define also define VIP pools under `Networks` > `Default Network`.
+Here, an admin can configure users and groups (including Active Directory login authentication, allowing access to clusters based on the users AD group.) and also define VIP pools under `Networks` > `Default Network`.
 
 VIP pools allow an administrator to define a "real world" range of IP addresses that clusters can use to integrate with the existing IT or Enterprise environment, each cluster can be created with a specific VIP pool, and Cisco Container Platform will manage allocations of addresses from that pool to each Kubernetes cluster when a developer requests an "external" IP, such as creating `LoadBalancer` service or `Ingress` style kubernetes objects.
 
@@ -70,9 +70,10 @@ For SSH Public Key, you can use your own SSH pubic key or paste in the key below
 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDIyJZfCNzDNJ+RupHpY8HhpvEq4YCz58FZONMxZCXY0RZB0uSTqu2fJ4KNDdOGggKPxaVkHam6GZoI8bBbclnViuI3yuo3rmeJoOlInGKXjAJ2KfnHHAXvmPj2UE4ritvdEOK+fJ0dGLKXCDFrolLKc8n4S1ck7cVmv1ruJ3+4iHJXhlp2Ea4irvIuwndgnZeKs4Zem5BZJh2trk6Cq7ctS1MgrjNy8fpFYIttjHuvWPSZ772IBI4jcjioEKJZYnayG9eVBBVuiLWHTuF8ZcaKvySlgrif0PG2Dj7zTsgOZtnJXhD36h2wOXJdUqsy1V7oHVPW1S16wantBN534QMz sandbox@CCP_SANDBOX_KEY
 ```
 
-Select the `10.10.20.0/24` subnet in the dropdown. Page three should look like the below image.
+Select the `default_network_subnet` subnet in the dropdown. Page three should look like the below image.
+In `Number of IP's` field. Choose 4
 
-Click `NEXT` through page 4, we wont enable a private docker registry for this test cluster!
+Click `NEXT` through page 4, we wont enable a private docker registry, Istio or AWS integration for this test cluster!
 
 Next, Click `FINISH` on the summary page!
 
@@ -95,7 +96,7 @@ Until the cluster is provisioned and healthy, shortcuts to access the cluster da
 Once both master and worker read `PROVISIONED`, we can download the token via the buttons in the screenshot above and also open the Kubernetes Dashboard.
 
 # 5. Access Your Kubernetes Cluster, by UI.
-Just like our previous cluster we accessed, If you click on your cluster within the Cisco Cloud Platform UI, you will see a number of buttons at the right hand side. Click on `DOWNLOAD TOKEN`, this will provide you a "Kubernetes Environment" file, which provides authentication to access your Kubernetes Cluster.
+Just like our previous cluster we accessed, If you click on your cluster within the Cisco Cloud Platform UI, you will see a number of buttons at the right hand side. Click on `DOWNLOAD KUBECONFIG`, this will provide you a "Kubernetes Environment" file, which provides authentication to access your Kubernetes Cluster.
 
   ![](assets/images/1234user-cluster-build-success.png)
 

labs/CiscoContainerPlatform-101/3.md

@@ -1,6 +1,6 @@
 # 6. API Cluster Creation.
 
-Time to create our second cluster! Re-Open swagger if you closed it and re-authenticate like we did earlier in the lab! [SWAGGER: https://10.10.20.30:30894/2/swaggerapi/](https://10.10.20.30:30894/2/swaggerapi/)
+Time to create our second cluster! Re-Open swagger if you closed it and re-authenticate like we did earlier in the lab! [SWAGGER: https://10.10.20.110/2/swaggerapi/](https://10.10.20.110/2/swaggerapi/)
 
 Click on `Expand Endpoints` in the swagger item entitled `2/clusters : List of cluster endpoints`.