Usage.md

@@ -18,7 +18,7 @@ This is the preferred way to use VKV in most cases, and is also the only way to
 
 - Execute
 ```
-docker run -tp 8080:80 -p 8443:443 registry.istandaarden.nl/kik-v/vkv/vkv/frontend:<version>
+docker run -tp 8080:80 -p 8443:443 registry.istandaarden.nl/kik-v/vkv/frontend:<version>
 ```
 where ``<version>`` is the desired version or ``latest`` to automatically start the latest version.
 
@@ -89,7 +89,7 @@ To run the VKV frontend using TLS scenario T1 (self-signed certificate), storing
 docker run -tp 8080:80 -p 8443:443 \
     -e VKV_HOSTNAME='localhost' \
     -v $( pwd ):/tls \
-    registry.istandaarden.nl/kik-v/vkv/vkv/frontend:<version>
+    registry.istandaarden.nl/kik-v/vkv/frontend:<version>
 ```
 
 Note: the `$( pwd )` syntax works on unix-like systems (Linux, Max OS X); on Windows provide the full path, e.g., `d:\\tls`.
@@ -105,7 +105,7 @@ docker run -tp 8080:80 -p 8443:443 \
     -v $( pwd )/tls:/tls \
     -v $( pwd )/data/uploads:/data/ephemeral \
     -v $( pwd )/data/central:/data/persistent \
-    registry.istandaarden.nl/kik-v/vkv/vkv/frontend:<version>
+    registry.istandaarden.nl/kik-v/vkv/frontend:<version>
 ```
 
 Note: the `$( pwd )` syntax works on unix-like systems (Linux, Max OS X); on Windows provide the full path, e.g., `d:\\tls`.
@@ -117,7 +117,7 @@ docker run -tp 8080:80 -p 8443:443 \
     -v $( pwd )/tls:/tls \
     -v $( pwd )/data/uploads:/data/ephemeral \
     -v $( pwd )/data/central:/data/persistent \
-    registry.istandaarden.nl/kik-v/vkv/vkv/frontend:<version>
+    registry.istandaarden.nl/kik-v/vkv/frontend:<version>
 ```
 
 As long as the `/tls` folder is bound to the same host path, VKV can figure out how to renew the certificate as needed.  If the VKV installation changes external name, just execute it with the new host name in `VKV_HOSTNAME` and the appropriate email in `VKV_EMAIL` to request and use a new certificate instead.