Fix typos in the Ingress Controller docs

docs-web/configuration/configuration-examples.md

@@ -1,5 +1,5 @@
 # Configuration Examples
 
-Out [GitHub repo](https://github.com/nginxinc/kubernetes-ingress) includes as number of configuration examples:
+Our [GitHub repo](https://github.com/nginxinc/kubernetes-ingress) includes a number of configuration examples:
 * [*Examples*](https://github.com/nginxinc/kubernetes-ingress/tree/v1.7.0/examples) show how to use advanced NGINX features in Ingress resources with annotations.
 * [*Examples of Custom Resources*](https://github.com/nginxinc/kubernetes-ingress/tree/v1.7.0/examples-of-custom-resources) show how to use VirtualServer and VirtualServerResources for a few use cases.

docs-web/installation/building-ingress-controller-image.md

@@ -33,7 +33,7 @@ We build the image using the make utility and the provided `Makefile`. Let’s c
       ```
       `myregistry.example.com/nginx-ingress` defines the repo in your private registry where the image will be pushed. Substitute that value with the repo in your private registry.
 
-      As the result, the image **myregistry.example.com/nginx-ingress:1.7.0** is built and pushed to the registry. Note that the tag `1.7.0` comes from the `VERSION` variable, defined in the Makefile.
+      As a result, the image **myregistry.example.com/nginx-ingress:1.7.0** is built and pushed to the registry. Note that the tag `1.7.0` comes from the `VERSION` variable, defined in the Makefile.
 
     * For NGINX Plus, first, make sure that the certificate (`nginx-repo.crt`) and the key (`nginx-repo.key`) of your license are located in the root of the project:
       ```
@@ -46,7 +46,7 @@ We build the image using the make utility and the provided `Makefile`. Let’s c
       ```
       `myregistry.example.com/nginx-plus-ingress` defines the repo in your private registry where the image will be pushed. Substitute that value with the repo in your private registry.
 
-      As the result, the image **myregistry.example.com/nginx-plus-ingress:1.7.0** is built and pushed to the registry. Note that the tag `1.7.0` comes from the `VERSION` variable, defined in the Makefile.
+      As a result, the image **myregistry.example.com/nginx-plus-ingress:1.7.0** is built and pushed to the registry. Note that the tag `1.7.0` comes from the `VERSION` variable, defined in the Makefile.
 
 Next you will find the details about available Makefile targets and variables.