diff --git a/cfg/rippled-example.cfg b/cfg/rippled-example.cfg
index 86b8f52dbc..5db008431d 100644
--- a/cfg/rippled-example.cfg
+++ b/cfg/rippled-example.cfg
@@ -979,19 +979,19 @@
 #
 #       nudb_block_size     EXPERIMENTAL: Block size in bytes for NuDB storage.
 #                           Must be a power of 2 between 4096 and 32768. Default is 4096.
-#                           
+#
 #                           This parameter controls the fundamental storage unit
 #                           size for NuDB's internal data structures. The choice
 #                           of block size can significantly impact performance
 #                           depending on your storage hardware and filesystem:
-#                           
+#
 #                           - 4096 bytes: Optimal for most standard SSDs and
 #                             traditional filesystems (ext4, NTFS, HFS+).
 #                             Provides good balance of performance and storage
 #                             efficiency. Recommended for most deployments.
 #                             Minimizes memory footprint and provides consistent
 #                             low-latency access patterns across diverse hardware.
-#                           
+#
 #                           - 8192-16384 bytes: May improve performance on
 #                             high-end NVMe SSDs and copy-on-write filesystems
 #                             like ZFS or Btrfs that benefit from larger block
@@ -999,21 +999,21 @@
 #                             databases. Offers better sequential throughput and
 #                             reduced I/O operations at the cost of higher memory
 #                             usage per operation.
-#                           
+#
 #                           - 32768 bytes (32K): Maximum supported block size
 #                             for high-performance scenarios with very fast
 #                             storage. May increase memory usage and reduce
 #                             efficiency for smaller databases. Best suited for
 #                             enterprise environments with abundant RAM.
-#                           
+#
 #                           Performance testing is recommended before deploying
 #                           any non-default block size in production environments.
-#                           
+#
 #                           Note: This setting cannot be changed after database
 #                           creation without rebuilding the entire database.
 #                           Choose carefully based on your hardware and expected
 #                           database size.
-#                           
+#
 #                           Example: nudb_block_size=4096
 #
 #       These keys modify the behavior of online_delete, and thus are only