Fix typos and links version (#3264)

Co-authored-by: Jcahilltorre <[email protected]>

Author: lucacome

docs/content/installation/installation-with-operator.md

@@ -17,8 +17,8 @@ This document describes how to install the NGINX Ingress Controller in your Kube
     * For NGINX Plus Ingress Controller, see [here](/nginx-ingress-controller/installation/pulling-ingress-controller-image) for details on how to pull the image from the F5 Docker registry.
     * To pull from the F5 Container registry, configure a docker registry secret using your JWT token from the MyF5 portal by following the instructions from [here](/nginx-ingress-controller/installation/using-the-jwt-token-docker-secret).
     * It is also possible to build your own image and push it to your private Docker registry by following the instructions from [here](/nginx-ingress-controller/installation/building-ingress-controller-image).
-2. Install the NGINX Ingress Operator following the [instructions](https://github.com/nginxinc/nginx-ingress-helm-operator/blob/v1.0.0/docs/installation.md).
-3. Create the default server secret and SecurityContextConstraint as oulined in the [instructions](https://github.com/nginxinc/nginx-ingress-helm-operator/blob/v1.0.0/docs/installation.md).
+2. Install the NGINX Ingress Operator following the [instructions](https://github.com/nginxinc/nginx-ingress-helm-operator/blob/v1.2.1/docs/installation.md).
+3. Create the default server secret and SecurityContextConstraint as outlined in the [instructions](https://github.com/nginxinc/nginx-ingress-helm-operator/blob/v1.2.1/docs/installation.md).
 
 ## 1. Create the NginxIngressController manifest
 
@@ -56,4 +56,4 @@ $ kubectl apply -f nginx-ingress-controller.yaml
 
 A new instance of the NGINX Ingress Controller will be deployed by the NGINX Ingress Operator in the `default` namespace with default parameters.
 
-To configure other parameters of the NginxIngressController resource, check the [documentation](https://github.com/nginxinc/nginx-ingress-helm-operator/blob/v1.0.0/docs/nginx-ingress-controller.md).
+To configure other parameters of the NginxIngressController resource, check the [documentation](https://github.com/nginxinc/nginx-ingress-helm-operator/blob/v1.2.1/docs/nginx-ingress-controller.md).

docs/content/intro/how-nginx-ingress-controller-works.md

@@ -309,7 +309,7 @@ A reload involves multiple steps:
 2. Assuming the command succeeds, the Ingress Controller periodically checks for the config version by sending an HTTP request to the config version server on  `unix:/var/lib/nginx/nginx-config-version.sock`.
 3. Once the Ingress Controller sees the correct config version returned by NGINX, it considers the reload successful. If it doesn't see the correct config version after the configurable timeout (see `-nginx-reload-timeout` [cli argument](/nginx-ingress-controller/configuration/global-configuration/command-line-arguments), the Ingress Controller considers the reload failed.
 
-> The [Ingress Controler Control Loop](#the-control-loop) stops during a reload so that it cannot change any configuration files or reload NGINX until the current reload succeeds or fails.
+> The [Ingress Controller Control Loop](#the-control-loop) stops during a reload so that it cannot change any configuration files or reload NGINX until the current reload succeeds or fails.
 
 ### When the Ingress Controller Reloads NGINX
 

examples/custom-resources/externalname-services/transport-server/README.md

@@ -8,7 +8,7 @@ An ExternalName service is defined by an external DNS name that is resolved into
 
 # Prerequisites
 
-For the illustration purpose we will run NGINX Ingress Controller (refered as NIC in the examples) with the ```-watch-namespace=nginx-ingress,default``` option. The option enables NIC to watch selected namespaces.
+For illustration purposes, we will run NGINX Ingress Controller (referred to as NIC in the examples) with the ```-watch-namespace=nginx-ingress,default``` option. The option enables NIC to watch selected namespaces.
 
 Any application deployed in other namespaces will be treated as an external service.
 

internal/externaldns/controller.go

@@ -22,7 +22,7 @@ import (
 )
 
 const (
-	// ControllerName is the name of the externaldns controler.
+	// ControllerName is the name of the externaldns controller.
 	ControllerName = "externaldns"
 )
 

pkg/apis/dos/validation/dos.go

@@ -89,7 +89,7 @@ func validateResourceReference(ref string) error {
 	return nil
 }
 
-// checkAppProtectDosLogConfContentField check conetent field doesnt appear in dos log
+// checkAppProtectDosLogConfContentField check content field doesn't appear in dos log
 func checkAppProtectDosLogConfContentField(obj *unstructured.Unstructured) string {
 	_, found, err := unstructured.NestedMap(obj.Object, "spec", "content")
 	if err == nil && found {

tests/suite/test_dos.py

@@ -435,7 +435,7 @@ def test_dos_arbitrator_different_ns(
         Test App Protect Dos: Check new IC pod get learning info with arbitrator from different namespace
         """
 
-        print("Remove dos arbitrator from namesapce: ", ingress_controller_prerequisites.namespace)
+        print("Remove dos arbitrator from namespace: ", ingress_controller_prerequisites.namespace)
         delete_dos_arbitrator(
             kube_apis.v1, kube_apis.apps_v1_api, "appprotect-dos-arb", ingress_controller_prerequisites.namespace
         )