diff --git a/build/appprotect/DockerfileWithAppProtectForPlus b/build/appprotect/DockerfileWithAppProtectForPlus
index 9476aa55e0..a440c84aed 100644
--- a/build/appprotect/DockerfileWithAppProtectForPlus
+++ b/build/appprotect/DockerfileWithAppProtectForPlus
@@ -117,7 +117,7 @@ COPY internal/configs/version1/nginx-plus.ingress.tmpl \
 # and use it as a certificate and key for the default server
 # ADD default.pem /etc/nginx/secrets/default
 
-# Uncomment the lines below if You want to install a custom CA certificate
+# Uncomment the lines below if you want to install a custom CA certificate
 # COPY build/appprotect/*.crt  /usr/local/share/ca-certificates/
 # RUN update-ca-certificates
 
diff --git a/build/appprotect/DockerfileWithAppProtectForPlusForOpenShift b/build/appprotect/DockerfileWithAppProtectForPlusForOpenShift
index 7d9f08b363..b60327b6fa 100644
--- a/build/appprotect/DockerfileWithAppProtectForPlusForOpenShift
+++ b/build/appprotect/DockerfileWithAppProtectForPlusForOpenShift
@@ -119,7 +119,7 @@ COPY internal/configs/version1/nginx-plus.ingress.tmpl \
 # and use it as a certificate and key for the default server
 # ADD default.pem /etc/nginx/secrets/default
 
-# Uncomment the lines below if You want to install a custom CA certificate
+# Uncomment the lines below if you want to install a custom CA certificate
 # COPY build/appprotect/*.crt  /etc/pki/ca-trust/source/anchors/
 # RUN update-ca-trust extract
 
diff --git a/deployments/common/ap-policy-definition.yaml b/deployments/common/ap-policy-definition.yaml
index dd10ada298..d03c77c847 100644
--- a/deployments/common/ap-policy-definition.yaml
+++ b/deployments/common/ap-policy-definition.yaml
@@ -259,7 +259,7 @@ spec:
                         type: object
                       type: array
                   type: object
-                blockingSettingsReference:
+                blockingSettingReference:
                   properties:
                     link:
                       pattern: ^http
diff --git a/deployments/helm-chart/crds/ap-logconf.yaml b/deployments/helm-chart/crds/ap-logconf.yaml
index 21d20f9dcb..aac18e0119 100644
--- a/deployments/helm-chart/crds/ap-logconf.yaml
+++ b/deployments/helm-chart/crds/ap-logconf.yaml
@@ -5,6 +5,8 @@ metadata:
     controller-gen.kubebuilder.io/version: v0.2.5
   creationTimestamp: null
   name: aplogconfs.appprotect.f5.com
+  labels:
+    app.kubernetes.io/name: "nginx-ingress"  
 spec:
   group: appprotect.f5.com
   names:
diff --git a/deployments/helm-chart/crds/ap-policy.yaml b/deployments/helm-chart/crds/ap-policy.yaml
index dd10ada298..1fc01816db 100644
--- a/deployments/helm-chart/crds/ap-policy.yaml
+++ b/deployments/helm-chart/crds/ap-policy.yaml
@@ -5,6 +5,8 @@ metadata:
     controller-gen.kubebuilder.io/version: v0.2.5
   creationTimestamp: null
   name: appolicies.appprotect.f5.com
+  labels:
+    app.kubernetes.io/name: "nginx-ingress"
 spec:
   group: appprotect.f5.com
   names:
@@ -259,7 +261,7 @@ spec:
                         type: object
                       type: array
                   type: object
-                blockingSettingsReference:
+                blockingSettingReference:
                   properties:
                     link:
                       pattern: ^http
diff --git a/docs-web/app-protect/troubleshooting.md b/docs-web/app-protect/troubleshooting.md
index 4295f778c2..a7659937f8 100644
--- a/docs-web/app-protect/troubleshooting.md
+++ b/docs-web/app-protect/troubleshooting.md
@@ -32,7 +32,7 @@ The table below categorizes some potential problems with the Ingress Controller
      - Too many Ingress Resources with App Protect enabled. Check the `NGINX fails to start/reload section <#nginx-fails-to-start-or-reload>`_ of the Known Issues. 
    * - Reload time.
      - The Ingress Controller NGINX Configuration timeout takes longer than usual.
-     - Check the HTTP resonse time to resources used in App Protect policy external references.
+     - Check the HTTP response time to resources used in App Protect policy external references.
      - The servers providing policy snippets have an increased response time due to load, or network Latency.      
 ```
 
@@ -108,10 +108,10 @@ This timeout should be more than enough to verify configurations. However, when
 
 You can increase this timeout by setting the `nginx-reload-timeout` [cli-argument](/nginx-ingress-controller/configuration/global-configuration/command-line-arguments/#cmdoption-nginx-reload-timeout).
 
-If You are using external references in Your Nginx App Protect policies, verify if the servers hosting the referenced resources are available and that their response time is as short as possible (see next paragraph).
-If the references are not available during ingress controller startup the pod will fail to startup. In case the resources are not available during a reload, the relod will fail, and ingress controller will process traffic with the previous correct coonfiguration.
+If you are using external references in your Nginx App Protect policies, verify if the servers hosting the referenced resources are available and that their response time is as short as possible (see next paragraph).
+If the references are not available during ingress controller startup the pod will fail to startup. In case the resources are not available during a reload, the reload will fail, and ingress controller will process traffic with the previous correct configuration.
 
-### Check the HTTP resonse time to resources used in App Protect policy external references.
+### Check the HTTP response time to resources used in App Protect policy external references.
 
 To check what servers host the external references: 
 ```