diff --git a/manual-install/readme.md b/manual-install/readme.md
index 05d4b8c7..c104b061 100644
--- a/manual-install/readme.md
+++ b/manual-install/readme.md
@@ -23,16 +23,16 @@ Then copy the sample.conf to a new file, e.g. `cp sample.conf my.conf`, open the
 
 Now copy the provided yaml file to a docker-compose file by running on x64 `cp latest.yml docker-compose.yml` and on arm64 `cp latest-arm64.yml docker-compose.yml`.
 
-Now you should be ready to go with `sudo docker-compose up --env-file my.conf`.
+Now you should be ready to go with `sudo docker-compose --env-file my.conf up`.
 
 ## How to update?
 Since the AIO containers may change in the future, it is highly recommended to strictly follow the following procedure whenever you want to upgrade your containers.
-1. Run `sudo docker-compose down --env-file my.conf` to stop all running containers
+1. Run `sudo docker-compose --env-file my.conf down` to stop all running containers
 1. Back up all important files and folders
 1. Run `git pull` in order to get the updated yaml files from the repository. Now bring your `docker-compose.yml` file up-to-date with the updated one from the repository. You can use `diff docker-compose.yml latest.yml` on x64 and `diff docker-compose.yml latest-arm64.yml` on arm64 for comparing.
 1. Also have a look at the `sample.conf` if any variable was added or renamed and add that to your conf file as well. Here may help the diff command as well.
-1. After the file update was successful, simply run `sudo docker-compose pull --env-file my.conf` to pull the new images.
-1. At the end run `sudo docker-compose up --env-file my.conf` in order to start and update the containers with the new configuration.
+1. After the file update was successful, simply run `sudo docker-compose --env-file my.conf pull` to pull the new images.
+1. At the end run `sudo docker-compose --env-file my.conf up` in order to start and update the containers with the new configuration.
 
 ## FAQ
 ### Backup and restore?