Apply suggestions from code review

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Author: AlinsRan

api/v2/apisixroute_types.go

@@ -418,7 +418,7 @@ type ApisixRouteHTTPMatchExprSubject struct {
 	// Supported values: `Header`, `Query`, `Path`, `Cookie`, `Variable`, `Body`.
 	// When Scope is `Path`, Name will be ignored.
 	// When Scope is `Body`, Name supports dot-notation JSON path (e.g., "model.version",
-	// "messages[*].role") and maps to APISIX's post_arg.<name> variable, which works with
+	// "messages[*].role") and maps to APISIX's `post_arg.<name>` variable, which works with
 	// application/json, application/x-www-form-urlencoded, and multipart/form-data.
 	// +kubebuilder:validation:Enum=Header;Query;Path;Cookie;Variable;Body
 	Scope string `json:"scope" yaml:"scope"`

config/crd/bases/apisix.apache.org_apisixroutes.yaml

@@ -217,7 +217,7 @@ spec:
                                       Supported values: `Header`, `Query`, `Path`, `Cookie`, `Variable`, `Body`.
                                       When Scope is `Path`, Name will be ignored.
                                       When Scope is `Body`, Name supports dot-notation JSON path (e.g., "model.version",
-                                      "messages[*].role") and maps to APISIX's post_arg.<name> variable, which works with
+                                      "messages[*].role") and maps to APISIX's `post_arg.{name}` variable, which works with
                                       application/json, application/x-www-form-urlencoded, and multipart/form-data.
                                     enum:
                                     - Header

docs/en/latest/reference/api-reference.md

@@ -1119,7 +1119,7 @@ ApisixRouteHTTPMatchExprSubject describes the subject of a route matching expres
 
 | Field | Description |
 | --- | --- |
-| `scope` _string_ | Scope specifies the subject scope. Supported values: `Header`, `Query`, `Path`, `Cookie`, `Variable`, `Body`. When Scope is `Path`, Name will be ignored. When Scope is `Body`, Name supports dot-notation JSON path (e.g., "model.version", "messages[*].role") and maps to APISIX's post_arg.<name> variable, which works with application/json, application/x-www-form-urlencoded, and multipart/form-data. |
+| `scope` _string_ | Scope specifies the subject scope. Supported values: `Header`, `Query`, `Path`, `Cookie`, `Variable`, `Body`. When Scope is `Path`, Name will be ignored. When Scope is `Body`, Name supports dot-notation JSON path (e.g., "model.version", "messages[*].role") and maps to APISIX's `post_arg.<name>` variable, which works with application/json, application/x-www-form-urlencoded, and multipart/form-data. |
 | `name` _string_ | Name is the name of the subject within the given scope: the header name, query parameter name, cookie name, Nginx variable name, or body field name (dot-notation JSON path supported for Body scope). Optional when Scope is Path. |