11372 - Updates and QA (#443)

* typos and full path images

* updated ords

* New images, tested

* linted

* grammer

kubernetes-for-oracledbas/access-cluster/access-cluster.md

@@ -43,7 +43,7 @@ This lab assumes you have:
 
 ### Notes about the Kubeconfig File
 
-The authentication token generated by the command in the kubeconfig file are short-lived, cluster-scoped, and specific to your account. As a result, you cannot share this kubeconfig file with other users to access the Kubernetes cluster.
+The authentication token generated by the command in the kubeconfig file is short-lived, cluster-scoped, and specific to your account. As a result, you cannot share this kubeconfig file with other users to access the Kubernetes cluster.
 
 > the authentication token could expire resulting in an error
 
@@ -113,28 +113,28 @@ In an Oracle Database, schema's provide a mechanism for isolating database objec
     </copy>
     ```
 
-3. Create a new *Namespace* called `sqldev-web`:
+3. Create a new *Namespace* called `ords`:
 
     ```bash
     <copy>
-    kubectl create namespace sqldev-web
+    kubectl create namespace ords
     </copy>
     ```
 
-4. Create a new context that points to the `sqldev-web` *namespace*:
+4. Create a new context that points to the `ords` *namespace*:
 
     ```bash
     <copy>
-    kubectl config set-context sqldev-web \
-    --namespace=sqldev-web \
+    kubectl config set-context ords \
+    --namespace=ords \
     --cluster=$(kubectl config get-clusters | tail -1) \
     --user=$(kubectl config get-users | tail -1)
     </copy>
     ```
 
-    You'll use the `sqldev-web` *namespace* later in the Workshop to deploy your Microservice Application.
+    You'll use the `ords` *namespace* later in the Workshop to deploy your Microservice Application.
 
-5. You should now have two contexts, one named `demo` and one named `sqldev-web`:
+5. You should now have two contexts, one named `demo` and one named `ords`:
 
     ```bash
     <copy>
@@ -157,6 +157,18 @@ In an Oracle Database, schema's provide a mechanism for isolating database objec
 
 For Production clusters, you may consider storing its context in an entirely different kubeconfig file to limit access and prevent mistakes.  Using the `production` context would be a matter of setting the `KUBECONFIG` environment variable to its location.
 
+### Fun Fact?
+
+You'll often see example commands online where `kubectl` is shortened to just `k`: `k get contexts; k create namespace ords`, etc.
+
+This is a heavily used practice implemented by creating an alias:
+
+```bash
+<copy>
+alias k="kubectl"
+</copy>
+```
+
 You may now **proceed to the next lab**
 
 ## Learn More

kubernetes-for-oracledbas/bind-adb/bind-adb.md

@@ -101,7 +101,11 @@ If it were set to `true` then deleting the resource from Kubernetes *WOULD* dele
 
     ![kubectl get AutonomousDatabase adb-existing](images/kubectl_get_adb.png "kubectl get AutonomousDatabase adb-existing")
 
-2. Describe the `adb-existing` resource (`kubectl describe <resource_type> <resource_name> [-n <namespace>]`) to get more details.  Use the resource_type alias `adb` for `AutonomousDatabase` to save some typing.  You can view all the resource_type alias short names by running: `kubectl api-resources`
+2. Describe the `adb-existing` resource (`kubectl describe <resource_type> <resource_name> [-n <namespace>]`) to get more details.
+
+    Use the resource_type alias `adb` for `AutonomousDatabase` to save some typing.
+
+    You can view all the resource_type alias short names by running: `kubectl api-resources`
 
     ```bash
     <copy>
@@ -257,7 +261,7 @@ Now that you've defined two *Secrets* in Kubernetes, redefine the `adb-existing`
 
     ![kubectl describe secrets adb-tns-admin](images/adb_tns_admin.png "kubectl describe secrets adb-tns-admin")
 
-    You'll see what equates to a `TNS_ADMIN` directory, and in fact, this *Secret* will be used by applications for just that purpose.
+    You'll see what equates to a `TNS_ADMIN` directory, and in fact, this *Secret* can be used by Microservice applications for just that purpose.
 
 You may now **proceed to the next lab**