fix: fix typos in docs.

docs/user-guide/configmap.md

@@ -148,7 +148,7 @@ By default this is disabled.
 
 #### enable-owasp-modsecurity-crs
 
-Eenables the OWASP ModSecurity Core Rule Set (CRS)
+Enables the OWASP ModSecurity Core Rule Set (CRS)
 By default this is disabled.
 
 #### disable-ipv6
@@ -346,7 +346,7 @@ Sets the time during which the specified number of unsuccessful attempts to comm
 
 Enables or disables compression of HTTP responses using the ["gzip" module](http://nginx.org/en/docs/http/ngx_http_gzip_module.html).
 
-The default mime type list to compress is: `application/atom+xml application/javascript aplication/x-javascript application/json application/rss+xml application/vnd.ms-fontobject application/x-font-ttf application/x-web-app-manifest+json application/xhtml+xml application/xml font/opentype image/svg+xml image/x-icon text/css text/plain text/x-component`.
+The default mime type list to compress is: `application/atom+xml application/javascript application/x-javascript application/json application/rss+xml application/vnd.ms-fontobject application/x-font-ttf application/x-web-app-manifest+json application/xhtml+xml application/xml font/opentype image/svg+xml image/x-icon text/css text/plain text/x-component`.
 
 #### use-http2
 

docs/user-guide/custom-errors.md

@@ -6,11 +6,11 @@ Each request to the default backend includes two headers:
 - `X-Code` indicates the HTTP code to be returned to the client.
 - `X-Format` the value of the `Accept` header.
 
-**Important:** the custom backend must return the correct HTTP status code to be returned. NGINX do not changes the reponse from the custom default backend.
+**Important:** the custom backend must return the correct HTTP status code to be returned. NGINX do not changes the response from the custom default backend.
 
 Using this two headers is possible to use a custom backend service like [this one](https://github.com/kubernetes/ingress-nginx/tree/master/examples/customization/custom-errors/nginx) that inspect each request and returns a custom error page with the format expected by the client. Please check the example [custom-errors](examples/customization/custom-errors/README.md)
 
-NGINX sends aditional headers that can be used to build custom response:
+NGINX sends additional headers that can be used to build custom response:
 
 - X-Original-URI
 - X-Namespace

docs/user-guide/default-ssl-certificate.md

@@ -1,6 +1,6 @@
 # Default SSL Certificate
 
-NGINX provides the option to configure a server as a cath-all with [server name _](http://nginx.org/en/docs/http/server_names.html) for requests that do not match any of the configured server names. This configuration works without issues for HTTP traffic.
+NGINX provides the option to configure a server as a catch-all with [server name _](http://nginx.org/en/docs/http/server_names.html) for requests that do not match any of the configured server names. This configuration works without issues for HTTP traffic.
 In case of HTTPS, NGINX requires a certificate.
 For this reason the Ingress controller provides the flag `--default-ssl-certificate`. The secret behind this flag contains the default certificate to be used in the mentioned scenario. If this flag is not provided NGINX will use a self signed certificate.
 

docs/user-guide/opentracing.md

@@ -37,6 +37,6 @@ $ curl -v http://$(minikube ip)
 $ curl -v http://$(minikube ip)
 ```
 
-In the zipkin inteface we can see the details:
+In the zipkin interface we can see the details:
 
 ![zipkin screenshot](../images/zipkin-demo.png "zipkin collector screenshot")

docs/user-guide/tls.md

@@ -9,7 +9,7 @@
 
 ## Default SSL Certificate
 
-NGINX provides the option to configure a server as a cath-all with [server name _](http://nginx.org/en/docs/http/server_names.html) for requests that do not match any of the configured server names. This configuration works without issues for HTTP traffic.
+NGINX provides the option to configure a server as a catch-all with [server name _](http://nginx.org/en/docs/http/server_names.html) for requests that do not match any of the configured server names. This configuration works without issues for HTTP traffic.
 In case of HTTPS, NGINX requires a certificate.
 For this reason the Ingress controller provides the flag `--default-ssl-certificate`. The secret behind this flag contains the default certificate to be used in the mentioned scenario. If this flag is not provided NGINX will use a self signed certificate.