Nit: indent yaml lists at the same level as their container objects

This seems to be the prevailing style among k8s projects.

This commit should be a no-op in terms of the meaning of the YAML
docs, i.e., it should be style only.

site-src/geps/gep-1058.md

@@ -524,8 +524,8 @@ spec:
       - type: RequestHeaderModifier
         requestHeaderModifier:
           add:
-            - name: my-source
-              value: store
+          - name: my-source
+            value: store
     allowedRoutes:
       namespaces:
         from: Selector
@@ -564,10 +564,10 @@ metadata:
   namespace: store-ns
 spec:
   parentRefs:
-    - kind: HTTPRoute
-      name: my-example
-      namespace: prod-gw
-      sectionName: store
+  - kind: HTTPRoute
+    name: my-example
+    namespace: prod-gw
+    sectionName: store
   rules:
   - matches:
     - path:
@@ -585,26 +585,26 @@ spec:
       port: 8080
 status:
   parents:
+  - parentRef:
+      kind: HTTPRoute
+      name: my-example
+      namespace: prod-gw
+      sectionName: store
+    controllerName: prod-gw
+    conditions:
+    - type: Attached
+      status: true
+      reason: Attached
+      message: Successfully attached to `store` section.
+    grandparents:
     - parentRef:
-        kind: HTTPRoute
-        name: my-example
-        namespace: prod-gw
-        sectionName: store
-      controllerName: prod-gw
+        kind: Gateway
+        name: prod-web-gw
       conditions:
-      - type: Attached
+      - type: Accepted
         status: true
-        reason: Attached
-        message: Successfully attached to `store` section.
-      grandparents:
-      - parentRef:
-          kind: Gateway
-          name: prod-web-gw
-        conditions:
-        - type: Accepted
-          status: true
-          reason: Accepted
-          Message: Route successfully attached to parent and gateway.
+        reason: Accepted
+        Message: Route successfully attached to parent and gateway.
 ---
 kind: HTTPRoute
 metadata:
@@ -650,13 +650,13 @@ status:
       message: Successfully attached to `store` section.      
     grandparents:
     - parentRef:
-          kind: Gateway
-          name: prod-web-gw
-        conditions:
-        - type: Accepted
-          status: true
-          reason: Accepted
-          Message: Route successfully attached to parent and gateway.
+        kind: Gateway
+        name: prod-web-gw
+      conditions:
+      - type: Accepted
+        status: true
+        reason: Accepted
+        Message: Route successfully attached to parent and gateway.
   - parentRef:
       kind: HTTPRoute
       name: my-example
@@ -670,13 +670,13 @@ status:
       message: Successfully attached to `api` section.
     grandparents:
     - parentRef:
-          kind: Gateway
-          name: prod-web-gw
-        conditions:
-        - type: Accepted
-          status: true
-          reason: Accepted
-          Message: Route successfully attached to parent and gateway.
+        kind: Gateway
+        name: prod-web-gw
+      conditions:
+      - type: Accepted
+        status: true
+        reason: Accepted
+        Message: Route successfully attached to parent and gateway.
 ```
 
 This is pretty verbose, but the extra information will be very important once we
@@ -779,22 +779,22 @@ status:
       reason: GrandparentConfigError
       message: Some configuration was not accepted in the attachment process. See grandparents for more details.
     grandparents:
-      - controllerName: somevalue
-        parentRef:
-          name: gateway-a
-        conditions:
-        - type: Accepted
-          status: true
-          reason: Accepted
-          message: Successfully accepted
-      - controllerName: somevalue
-        parentRef:
-          name: gateway-b
-        conditions:
-        - type: Accepted
-          status: false
-          reason: HostnameMismatch
-          message: The route could not be accepted because of a hostname mismatch - `testdomain.example.com` does not match `subdomain.example.com`.
+    - controllerName: somevalue
+      parentRef:
+        name: gateway-a
+      conditions:
+      - type: Accepted
+        status: true
+        reason: Accepted
+        message: Successfully accepted
+    - controllerName: somevalue
+      parentRef:
+        name: gateway-b
+      conditions:
+      - type: Accepted
+        status: false
+        reason: HostnameMismatch
+        message: The route could not be accepted because of a hostname mismatch - `testdomain.example.com` does not match `subdomain.example.com`.
 
 ```
 ### Multiple Gateways, different GatewayClasses, domain match error
@@ -842,14 +842,14 @@ spec:
   - name: gateway-b
     sectionName: http
   rules:
-    - allowedRoutes:
-        kinds: 
-          - kind: HTTPRoute
-        namespaces:
-          from: Same
-    - backendRefs:
-      - name: default-svc
-        port: 8080
+  - allowedRoutes:
+      kinds: 
+        - kind: HTTPRoute
+      namespaces:
+        from: Same
+  - backendRefs:
+    - name: default-svc
+      port: 8080
 status:
   parents:
   - controllerName: acme
@@ -878,11 +878,11 @@ spec:
   - name: gateway-a
     sectionName: http
   hostnames:
-    - testdomain.example.com
+  - testdomain.example.com
   rules:
-    - backendRefs:
-      - name: foo-svc
-        port: 8080
+  - backendRefs:
+    - name: foo-svc
+      port: 8080
 status:
   parents:
   - controllerName: acme
@@ -894,13 +894,13 @@ status:
       reason: Accepted
       message: Accepted successfully
     grandparents:
-      - parentRef:
-          name: gateway-a
-        conditions:
-        - type: Accepted
-          status: true
-          reason: Accepted
-          message: Successfully accepted
+    - parentRef:
+        name: gateway-a
+      conditions:
+      - type: Accepted
+        status: true
+        reason: Accepted
+        message: Successfully accepted
   - controllerName: nadir
     parentRef:
       name: http-parent
@@ -910,13 +910,13 @@ status:
       reason: GrandparentConfigError
       message: Some configuration was not accepted in the attachment process. See grandparents for more details.
     grandparents:
-      - parentRef:
-          name: gateway-b
-        conditions:
-        - type: Accepted
-          status: false
-          reason: HostnameMismatch
-          message: The route could not be accepted because of a hostname mismatch - `testdomain.example.com` does not match `subdomain.example.com`.
+    - parentRef:
+        name: gateway-b
+      conditions:
+      - type: Accepted
+        status: false
+        reason: HostnameMismatch
+        message: The route could not be accepted because of a hostname mismatch - `testdomain.example.com` does not match `subdomain.example.com`.
 ```