docs: fix missing ref in xDS docs and runTime case (#7784)

Signed-off-by: Daniel Hochman <danielhochman@users.noreply.github.com>

Mirrored from https://github.com/envoyproxy/envoy @ c586af9d3f5940acc73d6a5fd0fdc2c521b6243d

envoy/service/discovery/v2/rtds.proto

@@ -14,7 +14,7 @@ import "google/protobuf/struct.proto";
 
 import "validate/validate.proto";
 
-// [#protodoc-title: runTime Discovery Service (RTDS)]
+// [#protodoc-title: Runtime Discovery Service (RTDS)]
 // RTDS :ref:`configuration overview <config_runtime_rtds>`
 
 // [#not-implemented-hide:] Not configuration. Workaround c++ protobuf issue with importing

xds_protocol.rst

@@ -135,7 +135,7 @@ versioning across resource types. When ADS is not used, even each
 resource of a given resource type may have a distinct version, since the
 Envoy API allows distinct EDS/RDS resources to point at different :ref:`ConfigSources <envoy_api_msg_core.ConfigSource>`.
 
-.. xds_protocol_resource_update:
+.. _xds_protocol_resource_update:
 
 Resource Update
 ~~~~~~~~~~~~~~~
@@ -463,7 +463,7 @@ messages. ADS is not available for REST-JSON polling.
 When the poll period is set to a small value, with the intention of long
 polling, then there is also a requirement to avoid sending a
 :ref:`DiscoveryResponse <envoy_api_msg_DiscoveryResponse>` unless a change to the underlying resources has
-occurred <Resource Update>.
+occurred via a :ref:`resource update <xds_protocol_resource_update>`.
 
 .. |Multiple EDS requests on the same stream| image:: diagrams/eds-same-stream.svg
 .. |Multiple EDS requests on distinct streams| image:: diagrams/eds-distinct-stream.svg