modify gep 713 to accout for the chage

Signed-off-by: huabing zhao <[email protected]>

Author: zhaohuabing

geps/gep-713.md

@@ -683,11 +683,11 @@ the same behavior and semantics, although they may not be able to support
 attachment of all types of policy at all potential attachment points.
 
 ### Apply Policies to Sections of a Resource
-Policies can be targeted at specific matches within nested objects. For example, 
-it's useful to attach policies to a specific Gateway listeners.
+Policies can target specific matches within nested objects. For instance, rather than
+applying a policy to the entire Gateway, we may want to attach it to a particular Gateway listener.
 
-For example, an optional `sectionName` field can be set in the `targetRef` of a policy
-to refer to a specific listener in the target Gateway.
+To achieve this, an optional `sectionName` field can be set in the `targetRef` of a policy
+to refer to a specific listener within the target Gateway.
 
 ```yaml
 apiVersion: networking.acme.io/v1alpha2
@@ -709,7 +709,7 @@ The `sectionName` field could also be used to target a specific section of other
 * xRoute.Rules.Name
 * Service.Ports.Name
 
-This would require adding a `Name` field to those sub-resources that don't have a name yet. For example,
+This would require adding a `Name` field to those sub-resources that currently lack a name. For example,
 a `Name` field could be added to the `RouteRule` object:
 ```go
 type RouteRule struct {