diff --git a/README.org b/README.org
index 376d84d..78dc572 100644
--- a/README.org
+++ b/README.org
@@ -335,7 +335,7 @@ MYODOOSERVICENAME=odoo
 DBNAME="$MYODOOSERVICENAME"
 OUTPUTFILE=backup-odoo.zip
 cd /opt/apps/myc-deploy &&
-compose save "$MYODOOSERVICENAME" "$DBNAME" "$OUTPUT_FILE"
+compose save "$MYODOOSERVICENAME" "$DBNAME" "$OUTPUTFILE"
 #+END_SRC
 
 The backup file should be in the same directory.
@@ -343,9 +343,12 @@ The backup file should be in the same directory.
 ***** Restoring odoo account (filestore and database)
 
 There are still some quirks, so be sure:
+
 - to change your current directory to =/opt/apps/myc-deploy=
   and put your backup file in the same directory
 - your odoo instance should be already up.
+- an odoo base should not exist with the same name prior to restoring
+  if it is the case, =ODOOBASE=odoo && pgm rm "$ODOOBASE" -f && rm -rf
 - to have =admin-password= defined in your =compose.yml=, in your
   =odoo= service's =options=.
 
@@ -355,7 +358,7 @@ odoo:
     admin-password: XXXXXX
 #+END_SRC
 
-*IMPORTANT* you might want to consider the usage of docker-cutoff if
+*IMPORTANT* you might want to consider the usage of =docker-cutoff= if
 you are restoring a production odoo onto a dev or staging odoo that you
 don't want to allow to go mess around with sending mails or fetching mails.
 
diff --git a/bin/vps b/bin/vps
index 734f7de..c73af65 100755
--- a/bin/vps
+++ b/bin/vps
@@ -730,7 +730,7 @@ cmdline.spec:backup:cmd:mailcow:run() {
 
     local cmd_line cron_line cmd
 
-    for f in  mysql-backup mirror-dir; do
+    for f in mysql-backup mirror-dir; do
         [ -e "/etc/cron.d/$f" ] || {
             err "Can't find '/etc/cron.d/$f'."
             echo "  Have you forgotten to run 'vps install backup BACKUP_HOST' ?" >&2