update links to doc ref

Author: sylwang

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

@@ -11,7 +11,7 @@ Cookies can be configured and managed directly within the policy editor by selec
 
 ## 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/waf-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/nap-integration/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

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

@@ -11,7 +11,7 @@ Parameters can be configured and managed directly within the policy editor by se
 
 ## 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/waf-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/nap-integration/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)

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

@@ -11,7 +11,7 @@ URLs can be configured and managed directly within the policy editor by selectin
 
 ## 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/waf-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/nap-integration/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`: 

content/nginx-one/nap-integration/security-policy-api.md

@@ -1,6 +1,6 @@
 ---
 title: "Set security policies through the API"
-weight: 800
+weight: 900
 toc: true
 type: reference
 product: NGINX One

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

@@ -1,3 +1,11 @@
+---
+title: "Matching types: Explicit vs Wildcard"
+weight: 800
+toc: true
+nd-content-type: how-to
+nd-product: NGINX One Console
+---
+
 # Matching Types: Explicit vs Wildcard
 
 In F5 WAF for NGINX (formerly known as NGINX App Protect WAF), matching can be defined in two ways: