Update memory-limit.md

Author: mich-elle-luna

content/operate/rs/databases/memory-performance/memory-limit.md

@@ -97,19 +97,11 @@ When resharding multiple shards (for example, expanding from 4 to 8 shards), thi
 Resharding is an atomic operation that cannot be interrupted. Database corruption can occur if the process fails or stops unexpectedly. Minimizing resharding time reduces this risk.
 {{< /note >}}
 
-Flexible sharding optimizes the key trimming stage, significantly reducing the time required to remove unnecessary keys from original shards.
-
 ### Resharding duration factors
 
-Resharding duration increases linearly with the number of keys in your database. Flexible sharding, key length, and network traffic affect resharding duration:
-
-Flexible sharding improves resharding duration compared to standard sharding. 
-
-Key length directly affects resharding duration. Longer keys require more time to process due to increased hash calculation overhead per key. The decrease in duration provided by flex sharding varies based on key length:
+Resharding duration increases linearly with the number of keys in your database. Key length and network traffic affect resharding duration:
 
-- **Short keys (10 bytes)**: Flexible sharding provides up to 50% improvement
-- **Long keys (2000 KB)**: Flexible sharding provides minimal improvement (approximately 11%)
-- **Critical threshold**: Between 50-100 bytes, flex sharding advantages begin to diminish
+Key length directly affects resharding duration. Longer keys (2000 KB) require more time to process due to increased hash calculation overhead per key compared to short keys (10 bytes). 
 
 Network traffic has a measurable but limited effect on resharding duration. Since resharding operations typically don't reach CPU limits, the impact on both resharding time and ongoing traffic remains minimal.