From aee2a26d2fdef488832e1a7c261fbfffd8258c09 Mon Sep 17 00:00:00 2001
From: Shlomo Sagir <51323195+shsagir@users.noreply.github.com>
Date: Tue, 3 Dec 2024 09:30:45 +0200
Subject: [PATCH] Update partitioning-policy.md

---
 data-explorer/kusto/management/partitioning-policy.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/data-explorer/kusto/management/partitioning-policy.md b/data-explorer/kusto/management/partitioning-policy.md
index 754b0cc168..f6bd0dd46f 100644
--- a/data-explorer/kusto/management/partitioning-policy.md
+++ b/data-explorer/kusto/management/partitioning-policy.md
@@ -217,7 +217,7 @@ You can monitor the partitioning status of tables with defined policies in a dat
 
 * If there's a high ingestion throughput, or a large enough number of tables that have a partitioning policy defined, then the [Extents partition capacity](../management/capacity-policy.md#extents-partition-capacity) may gradually increase, so that [the process of partitioning extents](#the-data-partitioning-process) can keep up.
 
-::: moniker range = "azure-data-explorer"
+::: moniker range="azure-data-explorer"
 * To avoid consuming too many resources, these dynamic increases are capped. You may be required to gradually and linearly increase them beyond the cap, if they're used up entirely.
   * If increasing the capacities causes a significant increase in the use of the cluster's resources, you can scale the cluster
     [up](/azure/data-explorer/manage-cluster-vertical-scaling)/[out](/azure/data-explorer/manage-cluster-horizontal-scaling), either manually, or by enabling autoscale.