address feedback

Author: sylwang

content/includes/nginx-one/nap-policy-matching-types.md renamed to content/includes/nginx-one/waf-policy-matching-types.md

@@ -6,12 +6,12 @@ nd-content-type: how-to
 nd-product: NGINX One Console
 ---
 
-# Managing Cookies in NAP Policy
+# Managing Cookies in F5 WAF Policy
 Cookies can be configured and managed directly within the policy editor by selecting the **Cookies** option.
 
 ## Cookie Properties and Types
 Each cookie configuration includes:
-- `Cookie Type`: `Explicit` or `Wildcard`. For details on explicit and wildcard matching, see the [Matching Types: Explicit vs Wildcard]({{< ref "/nginx-one/nap-policy-matching-types.md" >}}) section.
+- `Cookie Type`: `Explicit` or `Wildcard`. For details on explicit and wildcard matching, see the [Matching Types: Explicit vs Wildcard]({{< ref "/nginx-one/waf-policy-matching-types.md" >}}) section.
 - `Cookie Name`: The name of the cookie to be monitored or protected
 - `Enforcement Type`: 
   - **Allow**: Permits the cookie with optional attack signature checks
@@ -44,18 +44,17 @@ See the [Supported Violations]({{< ref "/waf/policies/violations.md#supported-vi
 1. Choose Cookie Type:
    - Select either `Explicit` for exact cookie matching or `Wildcard` for pattern-based matching
 
-2. Configure Basic Properties:
+1. Configure Basic Properties:
    - Enter the `Cookie Name`
    - Choose whether to mask the cookie value in logs
 
-3. Set Enforcement:
+1. Set Enforcement:
    - Choose whether to allow or disallow the cookie
    - If `Allow Cookie` is selected, you can optionally enable attack signatures
+   - **⚠️ Important:** Attack signatures cannot be enabled for disallowed cookies.
 
-**⚠️ Important:** Attack signatures cannot be enabled for disallowed cookies.
-
-4. Optional: Configure Attack Signatures
+1. Optional: Configure Attack Signatures
    - If enabled, you can overwrite attack signatures for this specific cookie
    - For details on signature configuration, refer to the documentation on [Add Signature Sets]({{< ref "/nginx-one/nap-integration/add-signature-sets.md/" >}})
 
-5. Click **Add Cookie** to save your configuration
+1. Click **Add Cookie** to save your configuration

content/nginx-one/nap-integration/add-cookies.md

@@ -6,12 +6,12 @@ nd-content-type: how-to
 nd-product: NGINX One Console
 ---
 
-# Managing Parameters in NAP Policy
+# Managing Parameters in F5 WAF Policy
 Parameters can be configured and managed directly within the policy editor by selecting the **Parameters** option.
 
 ## Parameter Properties and Types
 Each parameter configuration includes:
-- `Parameter Type`: `Explicit` or `Wildcard`. For details on explicit and wildcard matching, see the [Matching Types: Explicit vs Wildcard]({{< ref "/nginx-one/nap-policy-matching-types.md" >}}) section.
+- `Parameter Type`: `Explicit` or `Wildcard`. For details on explicit and wildcard matching, see the [Matching Types: Explicit vs Wildcard]({{< ref "/nginx-one/waf-policy-matching-types.md" >}}) section.
 - `Name`: The name of the parameter
 - `Location`: Where the parameter is expected (URL query string, POST data, etc.)
 - `Value Type`: The expected type of the parameter value (e.g., alpha-numeric, integer, email)
@@ -50,18 +50,18 @@ See the [Supported Violations]({{< ref "/waf/policies/violations.md#supported-vi
 1. Choose Parameter Type:
    - Select either `Explicit` for exact parameter matching or `Wildcard` for pattern-based matching
 
-2. Configure Basic Properties:
+1. Configure Basic Properties:
    - Enter the parameter `Name`
    - Select the `Location` where the parameter is expected
    - Choose the `Value Type` (alpha-numeric, integer, email, etc.)
    - Set the `Data Type` if applicable
 
-3. Set Security Options:
+1. Set Security Options:
    - Choose whether to enable attack signatures
    - Decide if parameter value should be masked in logs which sets `sensitiveParameter` in [Parameter Configuration Reference]({{< ref "/waf/policies/parameter-reference.md" >}})
 
-4. Optional: Configure Attack Signatures
+1. Optional: Configure Attack Signatures
    - If enabled, you can overwrite attack signatures for this specific parameter
    - For details on signature configuration, refer to the documentation on [Add Signature Sets]({{< ref "/nginx-one/nap-integration/add-signature-sets.md/" >}})
 
-5. Click **Add Parameter** to save your configuration
+1. Click **Add Parameter** to save your configuration

content/nginx-one/nap-integration/add-parameters.md

@@ -29,7 +29,7 @@ A **signature exception** allows you to explicitly enable or disable individual
 From NGINX One Console, select **App Protect > Policies**. In the screen that appears, select **Add Policy**. That action opens a screen where you can:
 
 1. In **General Settings**, name and describe the policy.
-2. Navigate to the **Web Protection** tab and select **Attack Signature Sets**. Here, you can:
+1. Navigate to the **Web Protection** tab and select **Attack Signature Sets**. Here, you can:
    - View all enabled attack signature sets, including the default ones
    - Add new signature sets
    - Modify existing signature sets
@@ -64,58 +64,58 @@ To remove a signature set from your policy, you have two options:
 
 1. Disable the set by setting both `alarm` and `block` to `false`:
 
-```json
-{
-    "policy": {
-        "name": "no_xpath_policy",
-        "template": { "name": "POLICY_TEMPLATE_NGINX_BASE" },
-        "signature-sets": [
-            {
-                "name": "XPath Injection Signatures",
-                "block": false,
-                "alarm": false
-            }
-        ]
+    ```json
+    {
+        "policy": {
+            "name": "no_xpath_policy",
+            "template": { "name": "POLICY_TEMPLATE_NGINX_BASE" },
+            "signature-sets": [
+                {
+                    "name": "XPath Injection Signatures",
+                    "block": false,
+                    "alarm": false
+                }
+            ]
+        }
     }
-}
-```
-
-2. Use the `$action` meta-property to delete the set (preferred for better performance):
-
-```json
-{
-    "policy": {
-        "name": "no_xpath_policy",
-        "template": { "name": "POLICY_TEMPLATE_NGINX_BASE" },
-        "signature-sets": [
-            {
-                "name": "XPath Injection Signatures",
-                "$action": "delete"
-            }
-        ]
+    ```
+
+1. Use the `$action` meta-property to delete the set (preferred for better performance):
+
+    ```json
+    {
+        "policy": {
+            "name": "no_xpath_policy",
+            "template": { "name": "POLICY_TEMPLATE_NGINX_BASE" },
+            "signature-sets": [
+                {
+                    "name": "XPath Injection Signatures",
+                    "$action": "delete"
+                }
+            ]
+        }
     }
-}
-```
+    ```
 
 ## Add signature exceptions
 
 From the **Web Protection** tab, select **Attack Signature Exceptions**. This section allows you to override settings for individual signatures.
 
 1. Click **Add Item** to create a new exception.
-2. Select the signature(s) you want to modify.
-3. Configure the exception. For example, to disable a specific signature:
+1. Select the signature(s) you want to modify.
+1. Configure the exception. For example, to disable a specific signature:
 
-```json
-{
-    "signatures": [
-        {
-            "name": "_mem_bin access",
-            "enabled": false,
-            "signatureId": 200100022
-        }
-    ]
-}
-```
+    ```json
+    {
+        "signatures": [
+            {
+                "name": "_mem_bin access",
+                "enabled": false,
+                "signatureId": 200100022
+            }
+        ]
+    }
+    ```
 
 ### Advanced exception configuration
 
@@ -172,8 +172,8 @@ To exclude multiple signatures, add each as a separate entity:
 After configuring signature sets and exceptions:
 
 1. Select **Save Policy**. The policy JSON will be updated with your changes.
-2. Your policy will appear in the list under the name you provided.
-3. You can then [deploy]({{< ref "/nginx-one/nap-integration/deploy-policy.md/" >}}) the policy to either:
+1. Your policy will appear in the list under the name you provided.
+1. You can then [deploy]({{< ref "/nginx-one/nap-integration/deploy-policy.md/" >}}) the policy to either:
    - An instance
    - A Config Sync Group
 

content/nginx-one/nap-integration/add-signature-sets.md

@@ -6,12 +6,12 @@ nd-content-type: how-to
 nd-product: NGINX One Console
 ---
 
-# Managing URLs in NAP Policy
+# Managing URLs in F5 WAF Policy
 URLs can be configured and managed directly within the policy editor by selecting the **URLs** option.
 
 ## URL Properties and Types
 Each URL configuration includes:
-- `URL Type`: `Explicit` or `Wildcard`. For details on explicit and wildcard matching, see the [Matching Types: Explicit vs Wildcard]({{< ref "/nginx-one/nap-policy-matching-types.md" >}}) section
+- `URL Type`: `Explicit` or `Wildcard`. For details on explicit and wildcard matching, see the [Matching Types: Explicit vs Wildcard]({{< ref "/nginx-one/waf-policy-matching-types.md" >}}) section
 - `Method`: Specifies which HTTP methods are allowed (`GET`, `POST`, `PUT`, etc.)
 - `Protocol`: The protocol for the URL (`HTTP`/`HTTPS`)
 - `Enforcement Type`: 
@@ -44,19 +44,18 @@ See the [Supported Violations]({{< ref "/waf/policies/violations.md#supported-vi
 1. Choose URL Type:
    - Select either `Explicit` for exact URL matching or `Wildcard` for pattern-based matching
 
-2. Configure Basic Properties:
+1. Configure Basic Properties:
    - Enter the `URL` path
    - Select allowed `Method(s)` (e.g., `GET`, `POST`, *)
    - Choose the `Protocol` (`HTTP`/`HTTPS`)
 
-3. Set Enforcement:
+1. Set Enforcement:
    - Choose whether to allow or disallow the URL
    - If `Allow URL` is selected, you can optionally enable attack signatures
+   - **⚠️ Important:** Attack signatures cannot be enabled for disallowed URLs.
 
-**⚠️ Important:** Attack signatures cannot be enabled for disallowed URLs.
-
-4. **Optional**: Configure Attack Signatures
+1. **Optional**: Configure Attack Signatures
    - If enabled, you can overwrite attack signatures for this specific URL
    - For details on signature configuration, refer to the documentation on [Add Signature Sets]({{< ref "/nginx-one/nap-integration/add-signature-sets.md/" >}})
 
-5. Click **Add URL** to save your configuration
+1. Click **Add URL** to save your configuration