remove rate limiter from configuration-routing

Signed-off-by: Andrew Jandacek <[email protected]>
zowe · Nov 8, 2024 · 40980b6 · 40980b6
1 parent 8ecb1ce
commit 40980b6
Showing 1 changed file with 0 additions and 2 deletions.
diff --git a/docs/user-guide/api-mediation/configuration-routing.md b/docs/user-guide/api-mediation/configuration-routing.md
@@ -25,8 +25,6 @@ The Gateway retry policy, customizable through zowe.yaml, optimizes request hand
 
 To customize the Gateway retry policy, see [Customizing Gateway retry policy](./configuration-gateway-retry-policy.md).
 
-To configure a custom rate limiter, see [Configuring custom rate limiter](./customizing-gateway-rate-limiter.md).
-
 Additionally, API ML supports specific instance access and load balancer cache distribution, improving service identification and scalability. These configurations, including service ID adjustments for compatibility with Zowe v2, demonstrate Zowe's adaptability and robustness in API management.
 
 To configure a unique cookie name for each instance to prevent overwriting of the default cookie name in the case of multiple Zowe instances, or for more complex deployment strategies, see [Configuring a unique cookie name for a specific API ML instance](./configuration-unique-cookie-name-for-multiple-zowe-instances.md).