diff --git a/docs/database/database-metrics.md b/docs/database/database-metrics.md
index 270d5c0800..09750777fb 100644
--- a/docs/database/database-metrics.md
+++ b/docs/database/database-metrics.md
@@ -483,7 +483,7 @@ Explaining bucket configuration:
 
 1. 10, 50, 100: These buckets are useful for capturing scenarios where only a small number of items are returned. Such small queries are common in real-time or interactive applications where performance and quick responses are critical.
 2. 250, 500, 1000: These values represent typical workloads where moderate amounts of data are returned in each query.
-3. 2000, 5000: These boundaries capture scenarios where the query returns large datasets. These larger page sizes can potentially increase memory or CPU usage and may lead to longer query execution times, making it important to track performance in these ranges. 
+3. 2000, 5000: These boundaries capture scenarios where the query returns large datasets. These larger page sizes can potentially increase memory or CPU usage and may lead to longer query execution times, making it important to track performance in these ranges.
 4. 10000: This boundary is included to capture rare, very large response sizes. Such queries can put significant strain on system resources, including memory, CPU, and network bandwidth, and can often lead to performance issues such as high latency or even network drops.
 
 Refer `db.cosmosdb.operation.request_charge` metrics for dimensions.