Doc fixes (#10236)

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

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

@@ -0,0 +1,5 @@
+changelog:
+  - type: NON_USER_FACING
+    description: >- 
+      Weekly doc fixes such as links, grammar, typos, and version updates.
+      skipCI-kube-tests:true

docs/content/guides/traffic_management/destination_types/grpc/grpc-transcoding.md

@@ -68,7 +68,7 @@ To explore gRPC transcoding, you can use the Bookstore demo app in the Gloo Gate
 Proto descriptors are created by using the `protoc` tool and are based on the functions and the HTTP mappings that you added to your proto files. 
 
 {{% notice note %}}
-The instructions in this guide assume that you did not enable the Gloo Gateway Function Discovery Service (FDS) to automatically generate proto descriptors and put them on the gRPC upstream. If you want to enable FDS, you can skip [Step 2](#generate-proto-descriptors) and [Step 3](#add-descriptors-to-upstream) in this guide, and go to [Step 4](#grpc-routing) directly. To enable FDS, run the following command: `kubectl label upstream -n gloo-system default-bookstore-8080 discovery.solo.io/function_discovery=enable`. 
+The instructions in this guide assume that you did not enable the Gloo Gateway Function Discovery Service (FDS) to automatically generate proto descriptors and put them on the gRPC upstream. If you want to enable FDS, you can skip [Step 2](#generate-proto-descriptors) and [Step 3](#add-descriptors-to-upstream) in this guide, and go to [Step 4](#grpc-routing) directly. To enable FDS, run the following command: `kubectl label upstream -n gloo-system default-bookstore-8080 discovery.solo.io/function_discovery=enabled`. 
 {{% /notice %}}
 
 

docs/content/static/content/version_geoss_latest.md

@@ -1 +1 @@
-1.18.0-beta27
+1.18.0-beta28

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

@@ -1 +1 @@
-1.18.0-beta27
+1.18.0-beta28

projects/gateway/api/v1/route_table.proto

@@ -172,10 +172,11 @@ message RouteTable {
     // The list of routes for the route table
     repeated Route routes = 1;
 
-    // When a delegated route defines a `RouteTableSelector` that matches multiple route tables, Gloo will inspect this
-    // field to determine the order in which the route tables are to be evaluated. This determines the order in which
+    // When a delegated route in a VirtualService or RouteTable defines a `RouteTableSelector` that matches
+    // multiple route tables, Gloo will inspect this field to determine the order in which
+    // the route tables are to be evaluated. This determines the order in which
     // the routes will appear on the final `Proxy` resource. The field is optional; if no value is specified, the weight
-    // defaults to 0 (zero).
+    // defaults to 0 (zero). Note that this field is ignored if it is not used in a route delegation scenario.  
     //
     // Gloo will process the route tables matched by a selector in ascending order by weight and collect the routes of
     // each route table in the order they are defined. If multiple route tables define the same weight, Gloo will sort the