Adjusted per PR recommendations

docs/walkthrough.md

@@ -20,12 +20,11 @@ Since the Service Catalog provides a Kubernetes-native interface to an
 server, we'll need to install one in order to proceed with a demo.
 
 We plan on using the minibroker for demo purposes. The codebase for that broker is
-[here](https://github.com/osbkit/minibroker).
+[here](https://github.com/kubernetes-sigs/minibroker).
 
 We're going to deploy the minibroker to our Kubernetes cluster before
-proceeding, and we'll do so with the minibroker helm chart. You can find details about
-that chart in the chart's
-[README](https://github.com/osbkit/minibroker#install-minibroker).
+proceeding, and we'll do so with the minibroker helm chart. You can find details about the chart in the minibroker README
+[README](https://github.com/kubernetes-sigs/minibroker#install-minibroker).
 
 Otherwise, to install with sensible defaults, run the following command:
 
@@ -96,7 +95,9 @@ Plans:
                      heavy-load production systems   
                      as well as for embedding into   
                      mass-deployed software. 
-
+.
+.
+.
 $ kubectl get clusterserviceclasses mariadb -o yaml
 apiVersion: servicecatalog.k8s.io/v1beta1
 kind: ClusterServiceClass
@@ -154,7 +155,9 @@ $ svcat get plans
                                               heavy-load production systems    
                                               as well as for embedding into    
                                               mass-deployed software.          
-
+.
+.
+.
 $ kubectl get clusterserviceplans
 NAME                       EXTERNAL-NAME      BROKER       CLASS        AGE                                                                                                                                                                                                    
 mariadb-10-1-26            10-1-26            minibroker   mariadb      34m                                                                                                                                                                                                    
@@ -214,7 +217,7 @@ status:
 
 # Step 4 - Creating a New ServiceInstance
 
-Now that a `ClusterServiceClass` named `10-1-26` exists within our
+Now that a `ClusterServiceClass` named `mariadb` exists within our
 cluster's service catalog, we can create a `ServiceInstance` that points to
 it.
 
@@ -404,6 +407,7 @@ mini-binding            Opaque                                8      91s
 ```
 
 Notice that a new `Secret` named `mini-binding` has been created.
+At this point,we could use this secret to connect the running MariaDB instance to our application running on Kubernetes.
 
 # Step 6 - Deleting the ServiceBinding