Doc fixes (solo-io#9796)

* Doc fixes

* Create doc-fixes.yaml

* github doc issue template

---------

Co-authored-by: soloio-bulldozer[bot] <48420018+soloio-bulldozer[bot]@users.noreply.github.com>
Co-authored-by: Art Berger <[email protected]>

.github/ISSUE_TEMPLATE/DOCS-ISSUE.yml

@@ -10,36 +10,46 @@ body:
     id: version
     attributes:
       label: Version
-      description: Which version of the Gloo Edge docs does this affect?
+      description: Which version of the Gloo Gateway docs does this affect?
       options:
-        - main (1.17.x beta)
-        - 1.16.x (latest)
+        - main (1.18.x beta)
+        - 1.17.x (latest)
+        - 1.16.x
         - 1.15.x
         - 1.14.x
-        - 1.13.x 
+    validations:
+      required: true
+  - type: dropdown
+    id: gateway-api
+    attributes:
+      label: Gateway API
+      description: Which Gateway API does this use?
+      options:
+        - Kubernetes Gateway API
+        - Gloo Edge API
     validations:
       required: true
   - type: textarea
     id: change-details
     attributes:
       label: Describe the requested changes
-      description: List the desired changes to be made to the Gloo Edge docs
+      description: List the desired changes to be made to the Gloo Gateway docs.
   - type: textarea
     id: docs-links
     attributes:
       label: Link to any relevant existing docs
       placeholder: |
-        1. https://docs.solo.io/gloo-edge/latest...
-        2. ...
+        1. Edge API docs: https://docs.solo.io/gloo-edge/latest...
+        2. Kubernetes Gateway API docs: https://docs.solo.io/gateway/latest...
   - type: textarea
     id: browser-details
     attributes:
       label: Browser Information
       description:
         If the change isn't related to content, please include your browser version and any other relevant information 
-        (e.g., browser zoom) to help us reproduce docs-related bugs
+        (e.g., browser zoom) to help us reproduce docs-related bugs.
   - type: textarea
     id: additional-context
     attributes:
       label: Additional Context
-      description: Add any other context, screenshots, links to related issues or PRs, etc. about the docs request here
+      description: Add any other context, screenshots, links to related issues or PRs, etc. about the docs request here.

changelog/v1.18.0-beta10/doc-fixes.yaml

@@ -0,0 +1,5 @@
+changelog:
+  - type: NON_USER_FACING
+    description: >- 
+      Minor doc fixes (links, typos, etc). 
+      skipCI-kube-tests:true

docs/content/operations/upgrading/faq.md

@@ -48,9 +48,10 @@ Review the following changes made to Gloo Edge in version {{< readfile file="sta
 
 Gloo Gateway is now a fully conformant Kubernetes Gateway API implementation. The existing Gloo Edge APIs were not changed and continue to be fully supported. To deploy a gateway proxy that is based on the Kubernetes Gateway API, see the [docs](https://docs.solo.io/gateway). 
 
-### Breaking changes 
+### Breaking changes
 
-**ExtProc attribute processing** {#extproc}
+<a id="extproc"></a>
+**ExtProc attribute processing**
 
 The Gloo Gateway extProc filter implementation was changed to comply with the latest extProc implementation in Envoy. Previously, request and response attributes were included only in a [header processing request](https://www.envoyproxy.io/docs/envoy/latest/api-v3/service/ext_proc/v3/external_processor.proto#service-ext-proc-v3-httpheaders), and were therefore sent to the extProc server only when request header processing messages were configured to be sent. Starting in Gloo Gateway version 1.17.0, the Gloo extProc filter sends request and response attributes as part of the top level [processing request](https://www.envoyproxy.io/docs/envoy/latest/api-v3/service/ext_proc/v3/external_processor.proto#service-ext-proc-v3-processingrequest). That way, attributes can be processed on the first processing request regardless of its type.  
 

docs/content/static/content/version_geoss_n+1.md

@@ -1 +1 @@
-1.18.0-beta7
+1.18.0-beta8