diff --git a/docs/self-managed/operational-guides/data-purge/data-purge.md b/docs/self-managed/operational-guides/data-purge/data-purge.md
index 04dccfc84fe..98b88e3ce55 100644
--- a/docs/self-managed/operational-guides/data-purge/data-purge.md
+++ b/docs/self-managed/operational-guides/data-purge/data-purge.md
@@ -8,11 +8,13 @@ The data purge feature allows you to delete all runtime and historical data from
 
 The purge operation performs two main actions:
 
+
 1. **Runtime Data Deletion**: Removes all live data from brokers, for example process definitions, instances, and jobs.
 2. **Historical Data Purge**: Clears exported data from configured exporters
 
 The data purge feature can be used to:
 
+
 - Delete data between test runs and therefore enabling reuse of the same cluster for multiple tests.
 - Resetting development or staging environments to a clean state.
 
@@ -116,6 +118,7 @@ The response is a JSON object. See detailed specs [here](https://github.com/camu
 }
 ```
 
+
 </details>
 
 The purging is done asynchronously.