docs: improve cross-referencing on request quotas page (#1098)

(cherry picked from commit 440217f)

Author: buger

api-management/request-quotas.mdx

@@ -7,7 +7,7 @@ sidebarTitle: "Request Quotas"
 
 ## Introduction
 
-Request Quotas in Tyk Gateway allow you to set a maximum number of API requests for a specific API key or Policy over longer, defined periods (e.g., day, week, month). This feature is distinct from rate limiting (which controls requests per second), and it is essential for managing API consumption, enforcing service tiers, and protecting your backend services from sustained overuse over time.
+Request Quotas in Tyk Gateway allow you to set a maximum number of API requests for a specific API key or [Security Policy](/api-management/policies) over longer, defined periods (e.g., day, week, month). This feature is distinct from [rate limiting](/api-management/rate-limit) (which controls requests per second), and it is essential for managing API consumption, enforcing service tiers, and protecting your backend services from sustained overuse over time.
 
 ```mermaid
 flowchart LR
@@ -33,7 +33,7 @@ flowchart LR
 
 ### Overview
 
-In this tutorial, we will configure Request Quotas on a Tyk Security Policy to limit the number of requests an API key can make over a defined period. Unlike rate limits (requests per second), quotas control overall volume. We'll set a low quota limit with a short renewal period for easy testing, associate a key with the policy, observe blocked requests once the quota is exhausted, and verify that the quota resets after the period elapses. This guide primarily uses the Tyk Dashboard for configuration.
+In this tutorial, we will configure Request Quotas on a [Tyk Security Policy](/api-management/policies) to limit the number of requests an API key can make over a defined period. Unlike [rate limits](/api-management/rate-limit) (requests per second), quotas control overall volume. We'll set a low quota limit with a short renewal period for easy testing, associate a key with the policy, observe blocked requests once the quota is exhausted, and verify that the quota resets after the period elapses. This guide primarily uses the Tyk Dashboard for configuration.
 
 ### Prerequisites
 
@@ -134,7 +134,7 @@ In this tutorial, we will configure Request Quotas on a Tyk Security Policy to l
         2. Click the **Add Policy** button.
         3. Under the **1. Access Rights** tab, in the **Add API Access Rule** section, select the `Request Quota Test` API.
         4. Scroll down to the **Global Limits and Quota** section (still under the **1. Access Rights** tab):
-            * **Important:** Disable **Rate Limiting** by selecting **Disable rate limiting** option, so it doesn't interfere with testing the quota.
+            * **Important:** Disable **[Rate Limiting](/api-management/rate-limit)** by selecting **Disable rate limiting** option, so it doesn't interfere with testing the quota.
             * Set the following values for `Usage Quotas`:
               * Uncheck the `Unlimited requests` checkbox
               * Enter `10` into the **Max Requests per period** field. (This is our low quota limit for testing).
@@ -388,7 +388,7 @@ Refer to the [Tyk Classic API Definition reference](/api-management/gateway-conf
 
 ### Configure via UI
 
-The Tyk Dashboard provides a straightforward interface to set request quota parameters on Security Policies and Access Keys.
+The Tyk Dashboard provides a straightforward interface to set request quota parameters on [Security Policies](/api-management/policies) and [Access Keys](/api-management/policies#access-key).
 
 <Tabs>
 
@@ -491,15 +491,15 @@ The above adds quotas to an access key. Any request made by the key will behave
 
 ### Important Considerations
 
-*   **Policy Precedence:** Quotas set on a Security Policy apply to all keys using that policy *unless* overridden by a specific quota set directly on the key (using the "Set per API Limits and Quota" option).
+*   **Policy Precedence:** Quotas set on a [Security Policy](/api-management/policies) apply to all keys using that policy *unless* overridden by a specific quota set directly on the key (using the "Set per API Limits and Quota" option).
 *   **Unlimited Quota:** Setting `quota_max` to `-1` grants unlimited requests for the quota period.
 *   **Event-Driven Resets:** Quotas reset *after* the `quota_renewal_rate` (in seconds) has passed *and* upon the next request using the key. They do not reset automatically on a fixed schedule (e.g., precisely at midnight or the 1st of the month) unless external automation updates the session object.
 *   **Response Headers:** When quotas are active, Tyk typically adds `X-RateLimit-Limit`, `X-RateLimit-Remaining`, and `X-RateLimit-Reset` headers to responses, allowing clients to track their usage. (Note: Header names might be configurable).
 
 ---
 ## How It Works
 
-Request Quotas in Tyk limit a client's total number of API requests within a defined period (hours, days, months). Unlike rate limits that control the frequency of requests over short intervals (like seconds or minutes) to prevent immediate system overload, Request Quotas control the total volume of requests allowed over much longer periods to manage overall consumption and align with service tiers. 
+Request Quotas in Tyk limit a client's total number of API requests within a defined period (hours, days, months). Unlike [rate limits](/api-management/rate-limit) that control the frequency of requests over short intervals (like seconds or minutes) to prevent immediate system overload, Request Quotas control the total volume of requests allowed over much longer periods to manage overall consumption and align with service tiers. 
 
 When clients reach their quota limit, further requests are rejected until the quota period renews. It helps API providers implement usage-based pricing tiers, prevent API abuse, control infrastructure costs, and ensure fair resource distribution among clients.
 
@@ -519,7 +519,7 @@ flowchart LR
 
 ### How Tyk Implements Quotas
 
-Tyk implements request quotas using a Redis-based counter mechanism with time-based expiration. Here's a detailed breakdown of the implementation:
+Tyk implements request quotas using a [Redis](/tyk-configuration-reference/redis-cluster-sentinel) based counter mechanism with time-based expiration. Here's a detailed breakdown of the implementation:
 
 ```mermaid
 graph LR
@@ -533,7 +533,7 @@ graph LR
 
 #### Core Components
 
-1. **Redis Storage**: Quotas are tracked in Redis using incrementing counters for each API key. The TTL is set to the quota renewal period, and the counter is reset to 0 on the next request after expiration.
+1. **[Redis Storage](/tyk-configuration-reference/redis-cluster-sentinel)**: Quotas are tracked in Redis using incrementing counters for each API key. The TTL is set to the quota renewal period, and the counter is reset to 0 on the next request after expiration.
 
     Here is a sample Redis key for a  Request Quota:
     ```
@@ -612,7 +612,7 @@ The available allowance (`QuotaRemaining`) for an API key is replenished back to
 
 #### Key Technical Aspects
 
-1. **Time-Based Reset**: Unlike rate limiting, which uses sliding windows, quotas have a fixed renewal time determined by `QuotaRenewalRate` (in seconds)
+1. **Time-Based Reset**: Unlike [rate limiting](/api-management/rate-limit), which uses sliding windows, quotas have a fixed renewal time determined by `QuotaRenewalRate` (in seconds)
 
 2. **Atomic Operations**: Redis pipelining is used to ensure atomic increment and expiration setting:
 
@@ -630,7 +630,7 @@ Request Quotas in Tyk limit the total number of API requests a client can make w
 
 <Accordion title='How do Request Quotas differ from Rate Limits?'>
 While both control API usage, they serve different purposes:
-- **Rate Limits** control the frequency of requests (e.g., 10 requests per second) to prevent traffic spikes and ensure consistent performance
+- **[Rate Limits](/api-management/rate-limit)** control the frequency of requests (e.g., 10 requests per second) to prevent traffic spikes and ensure consistent performance
 - **Request Quotas** control the total volume of requests over a longer period (e.g., 10,000 requests per month) to manage overall API consumption and often align with business/pricing models
 </Accordion>