More docs fixes

Author: lucacome

.github/release-drafter.yml

@@ -63,4 +63,4 @@ template: |
   ## Compatibility
 
   - NGINX Ingress Controller NIC_VERSION_REPLACE_ME!
-  - Openshift 4.5 or newer.
+  - OpenShift 4.5 or newer.

README.md

@@ -69,7 +69,7 @@ It is possible to run the operator in your local machine. This is useful for tes
 
 ### Run Operator locally
 
-1. Have access to a Kubernetes/Openshift cluster.
+1. Have access to a Kubernetes/OpenShift cluster.
 1. Apply the IC CRD:
    ```
     make install

docs/installation.md

@@ -1,7 +1,7 @@
 # Installation
 
 We currently support 2 methods of installation:
-1. [Installation in an Openshift cluster](./openshift-installation.md) using the [OLM](https://github.com/operator-framework/operator-lifecycle-manager).
-1. [Manual installation](./manual-installation.md) in a Kubernetes or Openshift cluster by manually deploying the operator manifests.
-   
+1. [Installation in an OpenShift cluster](./openshift-installation.md) using the [OLM](https://github.com/operator-framework/operator-lifecycle-manager).
+1. [Manual installation](./manual-installation.md) in a Kubernetes or OpenShift cluster by manually deploying the operator manifests.
+
 After installation, use the [sample CR definition](../config/samples/charts_v1alpha1_nginxingress.yaml) to deploy the NGINX Ingress Controller using the operator.

docs/manual-installation.md

@@ -11,7 +11,7 @@ This will deploy the operator in the `nginx-ingress-operator-system` namespace.
     git checkout v1.1.0
     ```
 
-   2. `Openshift` To deploy the Operator and associated resources to an OpenShift environment, run:
+   2. `OpenShift` To deploy the Operator and associated resources to an OpenShift environment, run:
     ```
     make deploy IMG=nginx/nginx-ingress-operator:1.1.0
     ```
@@ -29,8 +29,8 @@ This will deploy the operator in the `nginx-ingress-operator-system` namespace.
     nginx-ingress-operator-controller-manager   1/1     1            1           15s
     ```
 
-3. `Openshift` Additional steps:
+3. `OpenShift` Additional steps:
 
 In order to deploy NGINX Ingress Controller instances into OpenShift environments, a new SCC is required to be created on the cluster which will be used to bind the specific required capabilities to the NGINX Ingress service account(s). To do so, please run the following command (assuming you are logged in with administrator access to the cluster):
 
-`kubectl -f https://github.com/nginxinc/nginx-ingress-helm-operator/v1.1.0/resources/scc.yaml`
+`kubectl -f https://raw.githubusercontent.com//nginxinc/nginx-ingress-helm-operator/v1.1.0/resources/scc.yaml`

docs/openshift-installation.md

@@ -1,26 +1,26 @@
-# Installation in an Openshift cluster using the OLM
+# Installation in an OpenShift cluster using the OLM
 
-This installation method is the recommended way for Openshift users. **Note**: Openshift version must be 4.2 or higher.
+This installation method is the recommended way for OpenShift users. **Note**: OpenShift version must be 4.2 or higher.
 
 **Note: The `nginx-ingress-operator` supports `Basic Install` only - we do not support auto-updates. When you are installing the Operator using the OLM, the auto-update feature should be disabled to avoid breaking changes being auto-applied. In OpenShift, this can be done by setting the `Approval Strategy` to `Manual`. Please see the [Operator SDK docs](https://sdk.operatorframework.io/docs/advanced-topics/operator-capabilities/operator-capabilities/) for more details on the Operator Capability Levels.**
 
 The NGINX Ingress Operator is a [RedHat certified Operator](https://connect.redhat.com/en/partner-with-us/red-hat-openshift-operator-certification).
 
-1. In the Openshift dashboard, click `Operators` > `Operator Hub` in the left menu and use the search box to type `nginx ingress`:
+1. In the OpenShift dashboard, click `Operators` > `Operator Hub` in the left menu and use the search box to type `nginx ingress`:
 ![alt text](./images/openshift1.png "Operators")
 1. Click the `NGINX Ingress Operator` and click `Install`:
 ![alt text](./images/openshift2.png "NGINX Ingress Operator")
 1. Click `Subscribe`:
 ![alt text](./images/openshift3.png "NGINX Ingress Operator Install")
 
-Openshift will install the NGINX Ingress Operator:
+OpenShift will install the NGINX Ingress Operator:
 
 ![alt text](./images/openshift4.png "NGINX Ingress Operator Subscribe")
 
 Additional steps:
 
 In order to deploy NGINX Ingress Controller instances into OpenShift environments, a new SCC is required to be created on the cluster which will be used to bind the specific required capabilities to the NGINX Ingress service account(s). To do so, please run the following command (assuming you are logged in with administrator access to the cluster):
 
-`kubectl -f https://github.com/nginxinc/nginx-ingress-helm-operator/v1.1.0/resources/scc.yaml`
+`kubectl -f https://raw.githubusercontent.com/nginxinc/nginx-ingress-helm-operator/v1.1.0/resources/scc.yaml`
 
 You can now deploy the NGINX Ingress Controller instances.

examples/deployment-oss-min/README.md

@@ -12,31 +12,31 @@ If you would like to use TransportServers, refer to [this section](README.md#Tra
 1. Create a new namespace for our Ingress Controller instance:
     ```
     kubectl create -f ns.yaml
-    ```  
+    ```
 
-2. Create a new NginxIngressController resource that defines our NGINX Ingress Controller instance (**Note**: If using Openshift, change the `image.tag` to `edge-ubi`):
+2. Create a new NginxIngressController resource that defines our NGINX Ingress Controller instance (**Note**: If using OpenShift, change the `image.tag` to `edge-ubi`):
     ```
     kubectl create -f nginx-ingress-controller.yaml
     ```
 
- 
 
-This will deploy an NGINX Ingress Controller instance using a [Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) in the `my-nginx-controller` namespace. 
+
+This will deploy an NGINX Ingress Controller instance using a [Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) in the `my-nginx-controller` namespace.
 
 3. Check if all resources were deployed:
 
     ```
     kubectl -n my-nginx-ingress  get all
-    
+
     NAME                                               READY   STATUS    RESTARTS   AGE
     pod/my-nginx-ingress-controller-666854fb5f-f67fs   1/1     Running   0          3s
-    
+
     NAME                                  TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
     service/my-nginx-ingress-controller   NodePort   10.103.105.52   <none>        80:30298/TCP,443:32576/TCP   3s
-    
+
     NAME                                          READY   UP-TO-DATE   AVAILABLE   AGE
     deployment.apps/my-nginx-ingress-controller   1/1     1            1           4s
-    
+
     NAME                                                     DESIRED   CURRENT   READY   AGE
     replicaset.apps/my-nginx-ingress-controller-666854fb5f   1         1         1       4s
     ```
@@ -48,17 +48,17 @@ For more information about how to configure the NGINX Ingress Controller, check
 1. Delete the NginxIngressController:
     ```
     kubectl delete -f nginx-ingress-controller.yaml
-    ``` 
+    ```
 
 1. Delete the namespace:
     ```
     kubectl delete namespace my-nginx-ingress
     ```
-   
+
 ## TransportServers
 
-TransportServers provide support for TCP/UDP but are in active development and provided as a preview feature. 
-A GlobalConfiguration resource is used to specify the TCP/UDP listeners and is required by TransportServers. 
+TransportServers provide support for TCP/UDP but are in active development and provided as a preview feature.
+A GlobalConfiguration resource is used to specify the TCP/UDP listeners and is required by TransportServers.
 To use TransportServers, you must create a GlobalConfiguration resource *after* creating the namespace and *before* starting the Operator.
 
 

examples/deployment-plus-min/README.md

@@ -5,9 +5,9 @@ In this example we deploy the NGINX Ingress Controller (edge) as a [Deployment](
 ## Prerequisites
 
 1. Have the NGINX Ingress Operator deployed in your cluster. Follow [installation](../../README.md#installation) steps.
-2. Build the NGINX Ingress Controller for Plus image and push it to a private repository following 
-[these instructions](https://docs.nginx.com/nginx-ingress-controller/installation/building-ingress-controller-image/#building-the-image-and-pushing-it-to-the-private-registry) 
-(**Note**: For the build process, if using Openshift, use the `openshift-image-plus` or `openshift-image-nap-plus` targets). 
+2. Build the NGINX Ingress Controller for Plus image and push it to a private repository following
+[these instructions](https://docs.nginx.com/nginx-ingress-controller/installation/building-ingress-controller-image/#building-the-image-and-pushing-it-to-the-private-registry)
+(**Note**: For the build process, if using OpenShift, use the `openshift-image-plus` or `openshift-image-nap-plus` targets).
 
 If you would like to use TransportServers, refer to [this section](README.md#TransportServers) for additional pre-requisites.
 
@@ -16,29 +16,29 @@ If you would like to use TransportServers, refer to [this section](README.md#Tra
 1. Create a new namespace for our Ingress Controller instance:
     ```
     kubectl create -f ns.yaml
-    ```  
+    ```
 
 2. Create a new NginxIngressController resource that defines our NGINX Ingress Controller instance (**Note:** Update the `image.repository` field in the `nginx-ingress-controller.yaml` with your previously built image for NGINX Plus):
     ```
     kubectl create -f nginx-ingress-controller.yaml
     ```
 
-This will deploy an NGINX Ingress Controller instance using a [Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) in the `my-nginx-controller` namespace. 
+This will deploy an NGINX Ingress Controller instance using a [Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) in the `my-nginx-controller` namespace.
 
 3. Check if all resources were deployed:
 
     ```
     kubectl -n my-nginx-ingress  get all
-    
+
     NAME                                               READY   STATUS    RESTARTS   AGE
     pod/my-nginx-ingress-controller-666854fb5f-f67fs   1/1     Running   0          3s
-    
+
     NAME                                  TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
     service/my-nginx-ingress-controller   NodePort   10.103.105.52   <none>        80:30298/TCP,443:32576/TCP   3s
-    
+
     NAME                                          READY   UP-TO-DATE   AVAILABLE   AGE
     deployment.apps/my-nginx-ingress-controller   1/1     1            1           4s
-    
+
     NAME                                                     DESIRED   CURRENT   READY   AGE
     replicaset.apps/my-nginx-ingress-controller-666854fb5f   1         1         1       4s
     ```
@@ -50,7 +50,7 @@ For more information about how to configure the NGINX Ingress Controller, check
 1. Delete the NginxIngressController:
     ```
     kubectl delete -f nginx-ingress-controller.yaml
-    ``` 
+    ```
 
 1. Delete the namespace:
     ```