Repo sync for protected branch

data-explorer/kusto/management/request-rate-limit-policy.md

@@ -1,9 +1,9 @@
 ---
 title: Request rate limit policy
 description: Learn how to use the request rate limit policy to limit the number of concurrent requests classified into a workload group.
-ms.reviewer: yonil
+ms.reviewer: yabenyaa
 ms.topic: reference
-ms.date: 01/02/2025
+ms.date: 07/01/2026
 ---
 # Request rate limit policy
 
@@ -34,7 +34,8 @@ A request rate limit of kind `ConcurrentRequests` includes the following propert
 
 > [!NOTE]
 >
-> * If a workload group doesn't have a specified limit on the maximum concurrent requests, it's subject to the default maximum value of `10000`.
+> * The `default` workload group includes a pre-configured `ConcurrentRequests` limit of `Cores-Per-Node x 10`. See [The `default` workload group](#the-default-workload-group).
+> * If a workload group doesn't have a specified limit on the maximum concurrent requests, it's subject to the default value of `10000`.
 
 When a request exceeds the limit on maximum number of concurrent requests:
 

data-explorer/kusto/management/request-rate-limits-enforcement-policy.md

@@ -1,9 +1,9 @@
 ---
 title: Request rate limits enforcement policy
 description: Learn how to use the request rate limits enforcement policy to enforce request rate limits.
-ms.reviewer: yonil
+ms.reviewer: yabenyaa
 ms.topic: reference
-ms.date: 01/02/2025
+ms.date: 07/01/2026
 ---
 # Request rate limits enforcement policy
 
@@ -31,11 +31,13 @@ Request rate limits can be enforced at one of the following levels:
 * `Database`:
   * Rate limits are enforced by the database admin node that manages the database the request was sent to.
   * If there are multiple database admin nodes, the configured rate limit is effectively multiplied by the number of database admin nodes.
+  * This multiplication applies to all [request rate limit policies](./request-rate-limit-policy.md).
 * `QueryHead`:
   * Rate limits for *queries* are enforced by the query head node that the query was routed to.
   * This option affects queries that are sent with either strong or weak [query consistency](../concepts/query-consistency.md).
     * Strongly consistent queries run on the database admin node, and the configured rate limit is effectively multiplied by the number of database admin nodes.
     * For weakly consistent queries, the configured rate limit is effectively multiplied by the number of query head nodes.
+  * The multiplication applies to all [request rate limit policies](./request-rate-limit-policy.md).
   * This option doesn't apply to *management commands*.
 
 > [!NOTE]
@@ -49,11 +51,13 @@ Request rate limits can be enforced at one of the following levels:
 * `Database`:
   * Rate limits are enforced by the database admin node that manages the database the request was sent to.
   * If there are multiple database admin nodes, the configured rate limit is effectively multiplied by the number of database admin nodes.
+  * This multiplication applies to all [request rate limit policies](./request-rate-limit-policy.md).
 * `QueryHead`:
   * Rate limits for *queries* are enforced by the query head node that the query was routed to.
   * This option affects queries that are sent with either strong or weak [query consistency](../concepts/query-consistency.md).
     * Strongly consistent queries run on the database admin node, and the configured rate limit is effectively multiplied by the number of database admin nodes.
     * For weakly consistent queries, the configured rate limit is effectively multiplied by the number of query head nodes.
+  * The multiplication applies to all [request rate limit policies](./request-rate-limit-policy.md).
   * This option doesn't apply to *management commands*.
 
 > [!NOTE]