docs: fix code block formatting in numbered lists

Author: edmondas

docs/configuration/mail.md

@@ -87,13 +87,14 @@ Check your web server error log or PHP error log for debug output.
 If you're experiencing issues with TLS encryption:
 
 1. **Verify encryption setting:**
-   ```php
-   'encryption' => 'tls',  // For STARTTLS on port 587
-   // or
-   'encryption' => 'ssl',  // For SMTPS on port 465
-   // or
-   'encryption' => null,   // For unencrypted connections (not recommended)
-   ```
+
+```php
+'encryption' => 'tls',  // For STARTTLS on port 587
+// or
+'encryption' => 'ssl',  // For SMTPS on port 465
+// or
+'encryption' => null,   // For unencrypted connections (not recommended)
+```
 
 2. **Common port and encryption combinations:**
    - **Port 587** with `'encryption' => 'tls'` (STARTTLS) - Most common
@@ -119,9 +120,11 @@ This particularly affects:
 
 1. **Verify credentials:** Double-check username and password
 2. **Test SMTP connectivity:**
-   ```bash
-   telnet smtp.example.com 587
-   ```
+
+```bash
+telnet smtp.example.com 587
+```
+
 3. **Check firewall rules:** Ensure outbound SMTP ports are open
 4. **Review server logs:** Enable `'debug' => true` for detailed logging
 5. **Try alternative ports:** Test port 465 (SSL) or 25 if 587 fails

docs/installation/debian.md

@@ -35,9 +35,9 @@ Apache is usually pre-installed and configured on Debian systems. You'll need to
 
 1. Enable the required Apache modules:
 
-    ```bash
-    a2enmod rewrite
-    ```
+```bash
+a2enmod rewrite
+```
 
 2. Either place Poweradmin in the default webroot (`/var/www/html/`) or create a virtual host configuration.
 

docs/installation/ubuntu.md

@@ -35,9 +35,9 @@ Apache is usually pre-installed and configured on Ubuntu systems. You'll need to
 
 1. Enable the required Apache modules:
 
-    ```bash
-    a2enmod rewrite
-    ```
+```bash
+a2enmod rewrite
+```
 
 2. Either place Poweradmin in the default webroot (`/var/www/html/`) or create a virtual host configuration.
 

docs/maintenance/index.md

@@ -50,26 +50,26 @@ To prevent logs from consuming excessive disk space:
 
 1. **Database Logs**: Implement a log rotation strategy for Poweradmin's database logs:
 
-    ```sql
-    -- Example log cleanup (retain only the last 90 days)
-    DELETE FROM log_users WHERE created < DATE_SUB(NOW(), INTERVAL 90 DAY);
-    DELETE FROM log_zones WHERE created < DATE_SUB(NOW(), INTERVAL 90 DAY);
-    ```
+```sql
+-- Example log cleanup (retain only the last 90 days)
+DELETE FROM log_users WHERE created < DATE_SUB(NOW(), INTERVAL 90 DAY);
+DELETE FROM log_zones WHERE created < DATE_SUB(NOW(), INTERVAL 90 DAY);
+```
 
 2. **System Logs**: Configure log rotation for your web server and PHP logs:
 
-    ```
-    # Example logrotate configuration (/etc/logrotate.d/poweradmin)
-    /var/log/apache2/poweradmin-*.log {
-        rotate 14
-        daily
-        compress
-        delaycompress
-        missingok
-        notifempty
-        create 640 www-data adm
-    }
-    ```
+```
+# Example logrotate configuration (/etc/logrotate.d/poweradmin)
+/var/log/apache2/poweradmin-*.log {
+    rotate 14
+    daily
+    compress
+    delaycompress
+    missingok
+    notifempty
+    create 640 www-data adm
+}
+```
 
 ### Backup Procedures
 

docs/upgrading/index.md

@@ -23,11 +23,11 @@ For patch releases within the same minor version (e.g., 4.0.0 → 4.0.3, or 4.0.
 4. **Check release notes for SQL updates** - Only run database migration scripts if explicitly mentioned in the release notes for that version
 5. **Clear PHP opcache** - If your environment uses opcache, restart PHP-FPM or your web server to clear cached bytecode:
 
-    ```bash
-    sudo systemctl restart php-fpm
-    # or
-    sudo systemctl restart apache2
-    ```
+```bash
+sudo systemctl restart php-fpm
+# or
+sudo systemctl restart apache2
+```
 
 6. **Verify functionality** - Test login and basic operations
 

docs/upgrading/v4.0.0.md

@@ -48,12 +48,13 @@ After successfully running the migration script and verifying your new configura
    - Delete it once you're confident everything works: `rm inc/config.inc.php.bak`
 
 2. **If you kept the original file (answered "n"):**
-   ```bash
-   # Backup and remove the old config
-   mv inc/config.inc.php inc/config.inc.php.backup
-   # Store it safely outside the web root
-   mv inc/config.inc.php.backup ~/poweradmin-backups/config.inc.php.$(date +%Y%m%d)
-   ```
+
+```bash
+# Backup and remove the old config
+mv inc/config.inc.php inc/config.inc.php.backup
+# Store it safely outside the web root
+mv inc/config.inc.php.backup ~/poweradmin-backups/config.inc.php.$(date +%Y%m%d)
+```
 
 3. **Clean up other legacy files:**
    - You can safely remove `.old`, `.bak`, or other backup files from the `inc/` directory

docs/upgrading/v4.1.0.md

@@ -356,14 +356,14 @@ If you experience slow queries:
 
 1. Check database indexes are present:
 
-    ```sql
-    -- MySQL
-    SHOW INDEX FROM zones;
-    SHOW INDEX FROM records;
-
-    -- PostgreSQL
-    \di
-    ```
+```sql
+-- MySQL
+SHOW INDEX FROM zones;
+SHOW INDEX FROM records;
+
+-- PostgreSQL
+\di
+```
 
 2. Analyze query performance: Enable slow query log
 3. Consider adding indexes for frequently filtered columns