diff --git a/source/core/sharding-data-partitioning.txt b/source/core/sharding-data-partitioning.txt
index 8b9dbfa6727..2841360599e 100644
--- a/source/core/sharding-data-partitioning.txt
+++ b/source/core/sharding-data-partitioning.txt
@@ -219,9 +219,9 @@ In some cases, chunks can grow beyond the :ref:`specified chunk size
 <sharding-chunk-size>` but cannot undergo a :ref:`split<sharding-chunk-split>`.
 The most common scenario is when a chunk represents a single shard key value.
 Since the chunk cannot split, it continues to grow beyond the chunk size,
-becoming a :ref:`jumbo chunk<jumbo-chunk>`. These jumbo chunks can become a
-performance bottleneck as they continue to grow, especially if the shard key
-value occurs with high :ref:`frequency<shard-key-frequency>`.
+becoming a jumbo chunk. These jumbo chunks can become a performance bottleneck
+as they continue to grow, especially if the shard key value occurs with high
+:ref:`frequency<shard-key-frequency>`.
 
 The addition of new data or new shards can result in data distribution
 imbalances within the cluster. A particular shard may acquire