diff --git a/README.md b/README.md
index 2c64ed6f68a07af754f7e8c69d2880c9225c56db..31865ce8e073cc8106fddc8ed9044f546aece15d 100644
--- a/README.md
+++ b/README.md
@@ -21,12 +21,13 @@ AURA_PROTO=http
 to  the `.env` file.
 
 A better development setup for `steering`, that pulls the docker images for
-`dashboard` and `tank` from Docker Hub, builds the image for `steering` locally
-and exposes the ports can be achieved with `docker-compose.steering.yml` by
-adding this lines to the end of the `.env` file:
+`dashboard`, `dashboard-clock` and `tank` from Docker Hub, builds the image for
+`steering` locally and exposes the ports can be achieved with
+`docker-compose.steering.yml` by adding this lines to the end of the `.env`
+file:
 
 ```dotenv
-STEERING_VERSION=latest
+STEERING_VERSION=local
 TANK_VERSION=unstable
 DASHBOARD_VERSION=unstable
 DASHBOARD_CLOCK_VERSION=unstable
@@ -79,14 +80,14 @@ Or, if you prefer, you can just create a superuser after setting up the
 database:
 
 ```shell
-(venv) $ manage.py createsuperuser
+(venv) $ ./manage.py createsuperuser
 ```
 
 The only required fixtures are the recurrence rules, these are needed to create
 schedules:
 
 ```shell
-$ docker compose run django ./manage.py loaddata fixtures/program/rrule.json
+(venv) $ ./manage.py loaddata fixtures/program/rrule.json
 ```
 
 Then, you can create a RSA Key and the clients for `dashboard` and `tank`: