From 0825f18f7732b5b975eb7d297763b2b5387b8b39 Mon Sep 17 00:00:00 2001
From: Alan Dooley <a.dooley@f5.com>
Date: Mon, 21 Oct 2024 15:42:03 +0100
Subject: [PATCH] Update document to shift the subject focus the Policy object

---
 .../custom-resources/access-control/README.md    |  4 ++--
 site/content/configuration/access-control.md     | 16 +++++++---------
 2 files changed, 9 insertions(+), 11 deletions(-)

diff --git a/examples/custom-resources/access-control/README.md b/examples/custom-resources/access-control/README.md
index 9f4dd25618..30e5709c5e 100644
--- a/examples/custom-resources/access-control/README.md
+++ b/examples/custom-resources/access-control/README.md
@@ -1,3 +1,3 @@
-# Deploy an Access Control policy
+# Deploy a Policy for access control
 
-This is the example code used in the [Deploy an Access Control policy](https://docs.nginx.com/nginx-ingress-controller/configuration/access-control/) documentation.
+This is the example code used in the [Deploy a Policy for access control](https://docs.nginx.com/nginx-ingress-controller/configuration/access-control/) documentation.
diff --git a/site/content/configuration/access-control.md b/site/content/configuration/access-control.md
index cc5bcc6b87..2ff06fabc3 100644
--- a/site/content/configuration/access-control.md
+++ b/site/content/configuration/access-control.md
@@ -1,13 +1,11 @@
 ---
-title: Deploy an Access Control policy
+title: Deploy a Policy for access control
 weight: 900
 toc: true
 docs: DOCS-000
 ---
 
-This topic describes how to apply and update an Access Control policy with F5 NGINX Ingress Controller.
-
-It demonstrates this using an example application and a [VirtualServer custom resource]({{< ref "/configuration/virtualserver-and-virtualserverroute-resources.md" >}})
+This topic describes how to use F5 NGINX Ingress Controller to apply and update a Policy for access control. It demonstrates it using an example application and a [VirtualServer custom resource]({{< ref "/configuration/virtualserver-and-virtualserverroute-resources.md" >}}).
 
 ---
 
@@ -45,7 +43,7 @@ kubectl apply -f webapp.yaml
 
 ---
 
-## Deploy an Access Control policy
+## Deploy a Policy to create a deny rule
 
 Create a file named _access-control-policy-deny.yaml_. The highlighted _deny_ field will be used by the example application, and should be changed to the subnet of your machine.
 
@@ -93,13 +91,13 @@ The *403* response is expected, successfully blocking your machine.
 
 ---
 
-## Update the policy
+## Update the Policy to create an allow rule
 
-Create a new policy with the file _access-control-policy-allow.yaml_, updating the _allow_ field to the subnet of your machine.
+Update the Policy with the file _access-control-policy-allow.yaml_, setting the _allow_ field to the subnet of your machine.
 
 {{< ghcode "https://raw.githubusercontent.com/nginxinc/kubernetes-ingress/refs/heads/main/examples/custom-resources/access-control/access-control-policy-allow.yaml" "hl_lines=7-8" >}}
 
-Apply the policy:
+Apply the Policy:
 
 ```shell
 kubectl apply -f access-control-policy-allow.yaml
@@ -107,7 +105,7 @@ kubectl apply -f access-control-policy-allow.yaml
 
 ----
 
-## Verify the policy update
+## Verify the Policy update
 
 Attempt to access the application again: