diff --git a/Readme.md b/Readme.md
index de4456e0..e2e2f757 100644
--- a/Readme.md
+++ b/Readme.md
@@ -24,7 +24,7 @@ This command will pull, create, and start the container:
 ```
 docker run -d -p 8080:9392 --name gvm securecompliance/gvm
 ```
-You can use whatever `--name` you'd like but for the sake of this guide we're using openvas.
+You can use whatever `--name` you'd like but for the sake of this guide we're using gvm.
 
 The `-p 8080:9392` switch will port forward `8080` on the host to `9392` (the default web interface port) in the docker container. Port `8080` was chosen only to avoid conflicts with any existing installation. You can change `8080` to any available port that you'd like.
 
@@ -34,10 +34,10 @@ Depending on your hardware, it can take anyhwere from a few seconds to 10 minute
 
 There is no easy way to estimate the remaining NVT loading time, but you can check if the NVTs have finished loading by running:
 ```
-docker logs GVM
+docker logs gvm
 ```
 
-If you see "Your GVM container is now ready to use!" then, you guessed it, your container is ready to use.
+If you see "Your gvm container is now ready to use!" then, you guessed it, your container is ready to use.
 
 ## Accessing Web Interface
 
@@ -52,19 +52,19 @@ Password: admin
 
 This command will show you the GVM processes running inside the container:
 ```
-docker top GVM
+docker top gvm
 ```
 
 ## Checking the GVM Logs
 
 All the logs from /usr/local/var/log/gvm/* can be viewed by running:
 ```
-docker logs GVM
+docker logs gvm
 ```
 
 ## Updating the NVTs
 
 The NVTs will update every time the container starts. Even if you leave your container running 24/7, the easiest way to update your NVTs is to restart the container.
 ```
-docker restart GVM
+docker restart gvm
 ```