diff --git a/Changing-persistent-data-location.md b/Changing-persistent-data-location.md
index 701d93b..97fec8b 100644
--- a/Changing-persistent-data-location.md
+++ b/Changing-persistent-data-location.md
@@ -3,7 +3,7 @@
 By default all persistent data is saved under `/data`, you can override this path by setting the `DATA_FOLDER` env variable:
 
 ```sh
-docker run -d --name bitwarden \
+docker run -d --name vaultwarden \
   -e DATA_FOLDER=/persistent \
   -v /vw-data/:/persistent/ \
   -p 80:80 \
@@ -17,10 +17,10 @@ Notice, that you need to adapt your volume mount accordingly.
 Default is `$DATA_FOLDER/db.sqlite3`, you can change the path specifically for database using `DATABASE_URL` variable:
 
 ```sh
-docker run -d --name bitwarden \
-  -e DATABASE_URL=/database/bitwarden.sqlite3 \
-  -v /bw-data/:/data/ \
-  -v /bw-database/:/database/ \
+docker run -d --name vaultwarden \
+  -e DATABASE_URL=/database/vaultwarden.sqlite3 \
+  -v /vw-data/:/data/ \
+  -v /vw-database/:/database/ \
   -p 80:80 \
   vaultwarden/server:latest
 ```
@@ -32,10 +32,10 @@ Note, that you need to remember to mount the volume for both database and other
 Default is `$DATA_FOLDER/attachments`, you can change the path using `ATTACHMENTS_FOLDER` variable:
 
 ```sh
-docker run -d --name bitwarden \
+docker run -d --name vaultwarden \
   -e ATTACHMENTS_FOLDER=/attachments \
-  -v /bw-data/:/data/ \
-  -v /bw-attachments/:/attachments/ \
+  -v /vw-data/:/data/ \
+  -v /vw-attachments/:/attachments/ \
   -p 80:80 \
   vaultwarden/server:latest
 ```
@@ -47,12 +47,12 @@ Note, that you need to remember to mount the volume for both attachments and oth
 Default is `$DATA_FOLDER/icon_cache`, you can change the path using `ICON_CACHE_FOLDER` variable:
 
 ```sh
-docker run -d --name bitwarden \
+docker run -d --name vaultwarden \
   -e ICON_CACHE_FOLDER=/icon_cache \
-  -v /bw-data/:/data/ \
+  -v /vw-data/:/data/ \
   -v /icon_cache/ \
   -p 80:80 \
   vaultwarden/server:latest
 ```
 
-Note, that in the above example we don't mount the volume locally, which means it won't be persisted during the upgrade unless you use intermediate data container using `--volumes-from`. This will impact performance as bitwarden will have to re-download the icons on restart, but might save you from having stale icons in cache as they are not automatically cleaned.
\ No newline at end of file
+Note, that in the above example we don't mount the volume locally, which means it won't be persisted during the upgrade unless you use intermediate data container using `--volumes-from`. This will impact performance as vaultwarden will have to re-download the icons on restart, but might save you from having stale icons in cache as they are not automatically cleaned.
\ No newline at end of file