docs: Fix 2 links format typos on 'rst' documents (#34272)

Signed-off-by: labile <[email protected]>

docs/root/intro/arch_overview/upstream/load_balancing/load_balancers.rst

@@ -39,7 +39,7 @@ same or different weights.
   choices). The P2C load balancer has the property that host weights will decrease as the number of
   active requests on those hosts increases. P2C selection is particularly useful for load
   balancer implementations due to its resistance to
-  [herding behavior](https://en.wikipedia.org/wiki/Thundering_herd_problem).
+  `herding behavior <https://en.wikipedia.org/wiki/Thundering_herd_problem>`_.
 * *all weights not equal*:  If two or more hosts in the cluster have different load balancing
   weights, the load balancer shifts into a mode where it uses a weighted round robin schedule in
   which weights are dynamically adjusted based on the host's request load at the time of selection.

docs/root/intro/life_of_a_request.rst

@@ -460,7 +460,7 @@ The router filter is responsible for all aspects of upstream request lifecycle m
 stream allocated from the HTTP connection pool. It also is responsible for request timeouts, retries
 and affinity.
 
-The router filter is also responsible for the creation and running of the `Upstream HTTP filter <arch_overview_http_filters>`
+The router filter is also responsible for the creation and running of the :ref:`Upstream HTTP filter <arch_overview_http_filters>`
 chain. By default, upstream HTTP filters will start running immediately after headers arrive at the router
 filter, however C++ filters can pause until the upstream connection is established if they need to
 inspect the upstream stream or connection. Upstream HTTP filter chains are by default configured via cluster