More fixes for typos

Author: syedriko

documentation/modules/ROOT/pages/01-setup.adoc

@@ -21,7 +21,7 @@ The following CLI tools are required for running the exercises in this tutorial.
 
 | `git`
 | https://git-scm.com/download/mac
-| dnf install git
+| `dnf install git`
 |
 
 | https://maven.apache.org[Apache Maven]

documentation/modules/ROOT/pages/02-basic-fundas.adoc

@@ -88,7 +88,7 @@ NOTE: Sometimes the response might not be returned immediately especially when t
 [#basics-see-what-you-have-deployed]
 == See what you have deployed
 
-The service based deployment strategy that we did now will create many knative resources, the following commands will help you to query and find what has been deployed.
+The service-based deployment strategy that we did now will create many Knative resources, the following commands will help you to query and find what has been deployed.
 
 [#basics-show-knative-services]
 === service 

documentation/modules/ROOT/pages/04-scaling.adoc

@@ -234,7 +234,7 @@ oc -n knative-serving get configmap config-autoscaler -o yaml \
   | yq r - data.scale-to-zero-grace-period
 ----
 
-For better clarity and understanding let us <<scaling-cleanup,clean up>> the deployed knative resources before going to next section.
+For better clarity and understanding let us <<scaling-cleanup,clean up>> the deployed Knative resources before going to next section.
 
 [#scaling-auto-scaling]
 == Auto Scaling

documentation/modules/ROOT/pages/05-build/build-templates.adoc

@@ -7,9 +7,9 @@ The raw builds like what we did in xref:ROOT:05-build/build.adoc[previous chapte
  * Hard coding of build parameters 
  * Inability to make builds and services in synchronous i.e. services are deployed only after the related build is complete
 
-One of the solution to these problems is by using **Build Templates**.
+One of the solutions to these problems is **Build Templates**.
 
-Like the build spec the knative build template spec and knative service spec also needs some customizations before apply them.
+Similarly to the build spec, the Knative build template spec and the Knative service spec needs some customizations before being applied.
 
 [#build-template-prerequisite]
 == Prerequisite 

documentation/modules/ROOT/pages/05-build/build.adoc

@@ -19,7 +19,7 @@ Its required that you have container registry account which is needed during the
 You can get one for free at https://hub.docker.com[Docker Hub]
 ====
 
-As the Knative build and build template spec needs some customizations,such as creating a secret with your container registry credentials; we need to run following commands to create the needed kubernetes and knative resources with all your customizations. All the generated files will be placed in `$TUTORIAL_HOME/04-build/knative`.
+As the Knative build and build template specs need some customizations, such as creating a secret with your container registry credentials; we need to run the following commands to create the needed kubernetes and Knative resources with all your customizations. All the generated files will be placed in `$TUTORIAL_HOME/04-build/knative`.
 
 [#build-create-docker-secret]
 == Generate Docker Secret
@@ -76,7 +76,7 @@ For more details on why we need to do this please check https://github.com/knati
 
 [#build-generate-build-spec]
 == Generate Knative build spec
-The knative build spec is used to create and run the knative builds. You can find more details on Knative build https://github.com/knative/docs/tree/master/docs/build[here].
+The Knative build spec is used to create and run the Knative builds. You can find more details on Knative build https://github.com/knative/docs/tree/master/docs/build[here].
 
 [source,bash,subs="+macros,+attributes",linenums]
 ----
@@ -223,7 +223,7 @@ oc apply -n knativetutorial -f link:{github-repo}/{build-repo}/knative/kaniko-pv
 
 
 <1> The kubernetes secret called `basic-auth-pass`, check https://github.com/knative/docs/blob/master/docs/build/auth.md#basic-authentication-docker[here] for more details
-<2> The kubernetes service account called `build-bot` that wll run the build.  Only `build-bot` has access to the secret `basic-auth-pass`. Check https://github.com/knative/docs/blob/master/docs/build/auth.md#basic-authentication-docker[here] for more details
+<2> The kubernetes service account called `build-bot` that will run the build.  Only `build-bot` has access to the secret `basic-auth-pass`. Check https://github.com/knative/docs/blob/master/docs/build/auth.md#basic-authentication-docker[here] for more details
 <3> the kubernetes persistence volume claim used to cache maven artifacts, to make subsequent builds faster
 <4> the kubernetes persistence volume claim  that will be used to cache docker base images to make subsequent https://github.com/GoogleContainerTools/kaniko[Kaniko] docker builds faster
 

documentation/modules/ROOT/pages/06-eventing/eventing-src-sub.adoc

@@ -22,8 +22,8 @@ spec:
     name: in-memory-channel
 ----
 
-<1> The name of the channel, knative make it addressable i.e. resolveable to a target (a consumer service)
-<2> The channel provisioner which is responsible to provision this channel.Various messaging implementations provide their own channel(s) via __ClusterChannelProvisioner__.
+<1> The name of the channel. Knative makes it addressable, i.e. resolveable to a target (a consumer service)
+<2> The channel provisioner which is responsible for provisioning this channel. Various messaging implementations provide their own channel(s) via __ClusterChannelProvisioner__.
 
 Navigate to tutorial chapter's `knative` folder:
 

documentation/modules/ROOT/pages/06-eventing/eventing-src-svc.adoc

@@ -114,7 +114,7 @@ Navigate to tutorial chapter's `templates` folder:
 cd $TUTORIAL_HOME/05-eventing/knative/templates
 ----
 
-Run the following command to create the knative service that will be used as the subscriber for the cron events:
+Run the following command to create the Knative service that will be used as the subscriber for the cron events:
 
 [source,bash,subs="+macros,+attributes",linenums]
 ----

documentation/modules/ROOT/pages/_partials/minikube-setup.adoc

@@ -4,7 +4,7 @@
 [#start-minikube]
 ==== Configure and Start minikube 
 
-Before installing Knative and its components, we need to add few startup config to minikube.
+Before installing Knative and its components, we need to create the minikube virtual machine and deploy Kubernetes into it:
 
 [source,bash,subs="+macros,+attributes"]
 ----
@@ -20,7 +20,7 @@ minikube start -p knative --memory=8192 --cpus=4 \#<2>
 <1> Setting minikube profile to **knative** so that all future minikube commands are executed with this profile context
 <2> Starting a profile named **knative**
 <3> Minimum kubernetes version needs to be >= 1.12.0, refer to issue https://github.com/knative/serving/issues/3067 for more details.
-<4> If you are on linux then use `--vm-driver=kvm2`
+<4> On macOS. On Linux, please use `--vm-driver=kvm2`
 
 
 [#install-knative-istio]
@@ -34,15 +34,15 @@ kubectl apply --filename {knative-serving-repo}/{knative-serving-version}/istio.
 
 [NOTE]
 ====
-Installation of istio components will take some time and its highly recommended that you start Knative components installation only after you see all istio component pods are running. The istio pods can be watched using the command:
+Installation of istio components will take some time and it is highly recommended that you start Knative components installation only after you have verified that all istio component pods are running. The istio pods can be watched using the command:
 [source,bash,subs="+macros,+attributes"]
 ----
 kubectl -n istio-system get pods -w 
 ----
 You can use kbd:[CTRL + c ] to terminate the watch
 ====
 
-A successful istio install will have the pods running in `istio-system` namespace as shown below:
+A successful istio install will have the pods running in the `istio-system` namespace as shown below:
 
 [source,bash]
 ----
@@ -73,15 +73,15 @@ kubectl apply --filename {knative-serving-repo}/{knative-serving-version}/servin
 
 [NOTE]
 ====
-Installation of knative serving components will take some time, the status of the knative serving pods can be watched using the command:
+As the Knative serving components are getting installed, you can watch their status using the following command:
 [source,bash,subs="+macros,+attributes"]
 ----
 kubectl -n knative-serving get pods -w 
 ----
 You can use kbd:[CTRL + c ] to terminate the watch
 ====
 
-A successful Knative serving install will have the pods running in `knative-serving` as shown below:
+A successful Knative serving installation will have its pods running in the `knative-serving` namespace as shown below:
 
 [source,bash]
 ----
@@ -102,15 +102,15 @@ kubectl apply --filename {knative-build-repo}/{knative-build-version}/build.yaml
 
 [NOTE]
 ====
-Installation of knative build components will take some time, the status of the  knative serving pods can be watched using the command:
+As the Knative build components are getting installed, you can watch their status using the following command:
 [source,bash,subs="+macros,+attributes"]
 ----
 kubectl -n knative-build get pods -w 
 ----
 You can use kbd:[CTRL + c ] to terminate the watch
 ====
 
-A successful Knative build install will have the pods running in `knative-build` as shown below:
+A successful Knative build installation will have its pods running in the `knative-build` namespace as shown below:
 
 [source,bash]
 ----
@@ -131,7 +131,7 @@ kubectl apply --filename https://raw.githubusercontent.com/knative/serving/{knat
 
 [NOTE]
 ====
-Installation of knative eventing components will take some time, the status of the  knative serving pods can be watched using the command:
+As the Knative eventing components are getting installed, you can watch their status using the following commands:
 [source,bash,subs="+macros,+attributes"]
 ----
 kubectl -n knative-sources get pods -w 
@@ -140,7 +140,7 @@ kubectl -n knative-eventing get pods -w
 You can use kbd:[CTRL + c ] to terminate the watch
 ====
 
-A successful Knative eventing install will have the pods running `knative-eventing` and `knative-sources` in as shown below:
+A successful Knative eventing installation will have the following pods running in the `knative-eventing` and `knative-sources` namespaces:
 
 .knative-eventing namespace
 
@@ -173,7 +173,7 @@ kubectl create namespace knativetutorial
 
 [TIP]
 ====
-kubens utility installed as part of https://github.com/ahmetb/kubectx[kubectx], allows change the kubernetes namespace easily. 
+The kubens utility installed as part of https://github.com/ahmetb/kubectx[kubectx] allows for easy switching between kubernetes namespaces.
 
 [source,bash] 
 ----

documentation/modules/ROOT/pages/_partials/openshift-setup.adoc

@@ -34,7 +34,7 @@ Run the following commands to configure Knative with minishift:
 ./etc/scripts/install-on-minishift.sh #<1>
 -----
 
-<1> It will create a minishift profile and install knative.  It also assumes that you already have minishift and your computer has 10GB or more of memory
+<1> It will create a minishift profile and install Knative. It also assumes that you already have minishift and your computer has 10GB or more of memory.
 
 [#configure-openshift-project]
 ==== Configuring OpenShift project for Knative applications