Nit: punctuation

site-src/geps/gep-1058.md

@@ -185,9 +185,9 @@ spec:
 Here are the changes and related rules:
 
 1. Support for Parent/child Route relationships is an "Extended" feature in the
-   Gateway API specification
+   Gateway API specification.
 2. Add `AllowedRoutes` to [HTTPRouteRule][HTTPRouteRule] as optional
-    1. Default value is nil
+    1. Default value is nil.
     2. A single `RouteRule` can contain `BackendRefs` OR `AllowedRoutes`, not both.
     3. A parent `Route` may include `RouteRules` that use `BackendRefs` **AND**
        `RouteRules` that use `AllowedRoutes`.
@@ -202,10 +202,10 @@ Here are the changes and related rules:
     1. `Kind` is required when the `ParentRefs` is a route. `Kind` will default to
        `gateway` (current behavior).
 4. Add `Name` (type is [SectionName][sectionName]) to
-   [HTTPRouteRule][HTTPRouteRule] as optional
+   [HTTPRouteRule][HTTPRouteRule] as optional.
     1. The `Name` field is expected to be added in the implementation of
-       [GEP-995 - Add Name to HTTPRouteRule and HTTPRouteMatch][gep-995]
-    2. Default value is nil
+       [GEP-995 - Add Name to HTTPRouteRule and HTTPRouteMatch][gep-995].
+    2. Default value is nil.
     3. A child route may include a `SectionName` when its `ParentRef` is a route.
         1. A child route “attaches" to the parent route’s `RouteRule` that matches
            that `SectionName`. The child route must also match the criteria
@@ -225,7 +225,7 @@ Here are the changes and related rules:
        avoid cycles.
     2. If an implementation chooses to not enforce this limitation, that must be
        documented along with how many tiers of parent/child route relationships
-       are allowed
+       are allowed.
 7. A Route’s `ParentRefs` can list more than one type of parent.
     1. Example: A `HTTPRoute`’s ParentRefs can list one (or more) `Gateways` and
        one (or more) `HTTPRoutes` at the same time.
@@ -391,7 +391,7 @@ diagram from being even larger than it is, the routing configuration for the
 ### Summary of Changes, Requirements and Constraints: Binding and Reconciling Routes
 
 1. The process of binding a child route to a parent route is treated as a single
-   transaction
+   transaction.
    1. Any non-recoverable error encountered in the process of reconciling and
       binding the two routes, is treated as fatal to the transaction and the
       entire transaction fails.
@@ -943,7 +943,7 @@ The first draft of this GEP was presented in the document [K8s Gateway API -
 Route inclusion and delegation][first-draft]. It includes many comments from the
 Gateway API community.
 
-There are multiple other documents, GitHub Issues and discussions that are
+There are multiple other documents, GitHub Issues, and discussions that are
 directly related to this topic and influenced the design of this GEP. This
 includes the following: