minor fixes in 101 and 102

Author: dalbhanj

01-path-basics/101-start-here/readme.adoc

@@ -20,7 +20,7 @@ Click on the "Deploy to AWS" button and follow the CloudFormation prompts to beg
 
 [NOTE]
 AWS Cloud9 is currently available in 5 regions, and EKS is currently available in 2 regions (us-east-1 and us-west-2).
-Please choose the region closest to you.  If you choose a region for Cloud9 that does not support EKS, you will need to change the `AWS_DEFAULT_REGION` environment variable later.
+Please choose the region closest to you.  If you choose a region for Cloud9 that does not support EKS, you need to create VPC resources and change environment variables. We have not tested this configuration yet
 
 |===
 
@@ -69,6 +69,7 @@ To install the script, run this command in the "bash" terminal tab of the Cloud9
 
 image:cloud9-run-script.png[Running the script in Cloud9 Terminal]
 
+
 At this point you can restart the Cloud9 IDE terminal session to ensure that the kubectl completion is enabled. Once a new terminal window is opened, type `kubectl ver` and press `Tab` to autocomplete and press `Enter`. This will ensure that the `kubectl` tool is installed on the command line correctly and can autocomplete.
 
 [NOTE]

01-path-basics/102-your-first-cluster/readme.adoc

@@ -80,6 +80,12 @@ Once the cluster has moved to the `ACTIVE` state, download and run the `create-k
 
 This will create a configuration file at `$HOME/.kube/config` and update the necessary environment variable for default access.
 
+You can test your kubectl configuration using 'kubectl get service'
+
+    $ kubectl get service
+    NAME         TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
+    kubernetes   ClusterIP   10.100.0.1   <none>        443/TCP   8m
+
 === Create the worker nodes
 
 Now that your EKS master nodes are created, you can launch and configure your worker nodes.
@@ -115,6 +121,20 @@ To enable worker nodes to join your cluster, download and run the `aws-auth-cm.s
 Watch the status of your nodes and wait for them to reach the `Ready` status.
 
     $ kubectl get nodes --watch
+    NAME                                            STATUS     ROLES     AGE       VERSION
+    ip-192-168-223-116.us-west-2.compute.internal   NotReady   <none>    0s        v1.10.3
+    ip-192-168-223-116.us-west-2.compute.internal   NotReady   <none>    0s        v1.10.3
+    ip-192-168-223-116.us-west-2.compute.internal   NotReady   <none>    0s        v1.10.3
+    ip-192-168-147-168.us-west-2.compute.internal   NotReady   <none>    0s        v1.10.3
+    ip-192-168-147-168.us-west-2.compute.internal   NotReady   <none>    0s        v1.10.3
+    ip-192-168-102-172.us-west-2.compute.internal   NotReady   <none>    0s        v1.10.3
+    ip-192-168-102-172.us-west-2.compute.internal   NotReady   <none>    0s        v1.10.3
+    ip-192-168-223-116.us-west-2.compute.internal   NotReady   <none>    10s       v1.10.3
+    ip-192-168-147-168.us-west-2.compute.internal   NotReady   <none>    10s       v1.10.3
+    ip-192-168-102-172.us-west-2.compute.internal   NotReady   <none>    10s       v1.10.3
+    ip-192-168-223-116.us-west-2.compute.internal   Ready     <none>    20s       v1.10.3
+    ip-192-168-147-168.us-west-2.compute.internal   Ready     <none>    20s       v1.10.3
+    ip-192-168-102-172.us-west-2.compute.internal   Ready     <none>    20s       v1.10.3
 
 == Kubernetes Cluster Context