Route destination protocols are no longer experimental

- For route destination endpoints and the manifest schema

[cloudfoundry/routing-release#200]

Co-authored-by: Greg Cobb <[email protected]>
Co-authored-by: Michael Oleske <[email protected]>

Author: 2 people

docs/v3/source/includes/resources/manifests/_object.md.erb

@@ -126,7 +126,7 @@ will be updated for any existing route mapping.
 Name | Type | Description
 ---- | ---- | -----------
 **route** | _string_ | **(Required)** The route URI. Example: `host.domain.com`
-**protocol** (*experimental*) | _string_ | Protocol to use for this route. Valid protocols are `http1`, `http2`, and `tcp`.
+**protocol** | _string_ | Protocol to use for this route. Valid protocols are `http1`, `http2`, and `tcp`.
 
 ####  <a name="space-manifest-service-level-configuration"></a> Service-level configuration
 This configuration is _creating_ new service bindings between the app and a service instance. The `services` field can

docs/v3/source/includes/resources/routes/_destination_object.md.erb

@@ -25,4 +25,4 @@ If a destination does not specify a port, the default port depends on the app li
 | **app.process.type**          | _string_                 | Type of the process belonging to the app to route traffic to                                                                      |
 | **port**                      | _integer_                | Port on the destination process to route traffic to
 | **weight** (*experimental*)   | _integer_ or `null`      | Percentage of traffic which will be routed to this destination; _this feature is only available via the BETA Service Mesh routing plane_ |
-| **protocol** (*experimental*) | _string_ or `null`       | Protocol to use for this destination. Valid protocols are `http1` or `http2` if route protocol is `http`, `tcp` if route protocol is `tcp`. A `null` value will set it either `http1` or `tcp` based on the route protocol; _this feature is only available if you turn it on in routing release_ |
+| **protocol** | _string_ or `null`       | Protocol to use for this destination. Valid protocols are `http1` or `http2` if route protocol is `http`, `tcp` if route protocol is `tcp`. A `null` value will set it either `http1` or `tcp` based on the route protocol; _this feature is only available if you turn it on in routing release_ |