diff --git a/docs/how-to/backup-your-databases.md b/docs/how-to/backup-your-databases.md
index 297cf4002..d847d22a4 100644
--- a/docs/how-to/backup-your-databases.md
+++ b/docs/how-to/backup-your-databases.md
@@ -209,9 +209,18 @@ to exclude are `/dev` and `/run`, but that may not be exhaustive.
 
 If you prefer to restore a database without the help of borgmatic, first
 [extract](https://torsion.org/borgmatic/docs/how-to/extract-a-backup/) an
-archive containing a database dump, and then manually restore the dump file
-found within the extracted `~/.borgmatic/` path (e.g. with `pg_restore`,
-`mysql`, or `mongorestore`, commands).
+archive containing a database dump.
+
+The dump file can then be found in the extracted destination path within the 
+`~/.borgmatic/` directory. The `~` here corresponds to the HOME directory of 
+the user with whom you created the backup. For example, if you created the 
+backup with the `root` user, then the dump will be in 
+`EXTRACTED_DESTINATION_PATH/root/.borgmatic`. This also means you will have 
+to backup the HOME directory of that user you use to run `borgmatic create` 
+(otherwise there the dump file will not be available).
+
+You can then use the dump file to manually restore it using the native database 
+commands like `pg_restore`, `mysql`, `mongorestore` or similar.
 
 
 ## Preparation and cleanup hooks