Fix linking (#478)

envoyproxy · Feb 14, 2017 · fa1d968 · fa1d968
1 parent cb70b9d
commit fa1d968
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/configuration/overview/rate_limit.rst b/docs/configuration/overview/rate_limit.rst
@@ -34,4 +34,4 @@ gRPC service IDL
 
 Envoy expects the rate limit service to support the gRPC IDL specified in
 :repo:`/source/common/ratelimit/ratelimit.proto`. See the IDL documentation for more information
-on how the API works. See Lyft's reference implementation [here](https://github.com/lyft/ratelimit)
+on how the API works. See Lyft's reference implementation `here <https://github.com/lyft/ratelimit>`_.
diff --git a/docs/intro/arch_overview/global_rate_limiting.rst b/docs/intro/arch_overview/global_rate_limiting.rst
@@ -14,7 +14,7 @@ normally during typical request patterns but still prevent cascading failure whe
 to fail. Global rate limiting is a good solution for this case.
 
 Envoy integrates directly with a global gRPC rate limiting service. Although any service that
-implements the defined RPC/IDL protocol can be used, Lyft provides a [reference implementation](https://github.com/lyft/ratelimit)
+implements the defined RPC/IDL protocol can be used, Lyft provides a `reference implementation <https://github.com/lyft/ratelimit>`_
 written in Go which uses a Redis backend. Envoy’s rate limit integration has the following features:
 
 * **Network level rate limit filter**: Envoy will call the rate limit service for every new