From fa1d9680d809668fef2ec9386769c79486029f04 Mon Sep 17 00:00:00 2001 From: Jose Ulises Nino Rivera Date: Mon, 13 Feb 2017 18:03:10 -0800 Subject: [PATCH] Fix linking (#478) --- docs/configuration/overview/rate_limit.rst | 2 +- docs/intro/arch_overview/global_rate_limiting.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuration/overview/rate_limit.rst b/docs/configuration/overview/rate_limit.rst index f0a7e2b34094..2189d53bdb52 100644 --- 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 `_. diff --git a/docs/intro/arch_overview/global_rate_limiting.rst b/docs/intro/arch_overview/global_rate_limiting.rst index 803e2a46e3d7..b15ef05c1414 100644 --- 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 `_ 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