diff --git a/postgresql/procedures/README.md b/postgresql/procedures/README.md
index 835c0d0..466dd8c 100644
--- a/postgresql/procedures/README.md
+++ b/postgresql/procedures/README.md
@@ -2,13 +2,13 @@
 
 This is the declarative (PostgreSQL procedures based) partitioning implementation for Zabbix `history`, `trends`, and `auditlog` tables on PostgreSQL. This solution is intended to replace standard Zabbix housekeeping for the configured tables. Partitioning is very useful for large environments because it completely eliminates the housekeeper from the process. Instead of huge DELETE queries on several million rows, fast DDL queries (ALTER TABLE) are executed, which drop an entire partition. 
 
-4: 
-5: > [!CRITICAL]
-6: > **High-Load Environments**:
-7: > 1.  **Data Visibility**: After enabling partitioning, old data remains in `*_old` tables and is **NOT visible** in Zabbix. You must migrate data manually if needed.
-8: > 2.  **Disable Housekeeping**: You **MUST** disable Zabbix Housekeeper for History and Trends in *Administration -> General -> Housekeeping*. Failure to do so will cause massive `DELETE` loads.
-9: 
-10: ## Architecture
+
+> [!CRITICAL]
+> **High-Load Environments**:
+> 1.  **Data Visibility**: After enabling partitioning, old data remains in `*_old` tables and is **NOT visible** in Zabbix. You must migrate data manually if needed.
+> 2.  **Disable Housekeeping**: You **MUST** disable Zabbix Housekeeper for History and Trends in *Administration -> Housekeeping*. Failure to do so will cause massive `DELETE` loads.
+
+## Architecture
 
 The solution uses PostgreSQL native declarative partitioning (`PARTITION BY RANGE`).
 All procedures, information, statistics and configuration are stored in the `partitions` schema to maintain full separation from Zabbix schema.