diff --git a/backup-Existing-Installation.md b/backup-Existing-Installation.md
index 5ffc4f7..a4c7b36 100644
--- a/backup-Existing-Installation.md
+++ b/backup-Existing-Installation.md
@@ -2,7 +2,8 @@
 
 Backup An Existing Installation
 =======
-step 1: backup database
+#### step 1: backup database
+
 Best practice for backing up your EGroupware instance database is by EGroupware's "Backup and Restore" tools. You can get access to "Backup and Restore" tools either from setup page (see figure1 and figure2) or from Admin app -> backup and Restore in sidebar.
 
 <table>
@@ -16,7 +17,8 @@ Best practice for backing up your EGroupware instance database is by EGroupware'
   </tr>
 </table>
 
-step2: backup files
+#### step2: backup files
+
 EGroupware stores created/uploaded files including backup files by default under `/var/lib/egroupware/`. You need to back them up in a safe place. This is more important if you are migrating your EGroupware instance from a server to another.<br>
 You may check the path of EGroupware's file storage in setup under configuration (see figure3).