docs: Automatic docs update

Author: DO! DevOps bot

README.md

@@ -102,19 +102,19 @@ See [https://github.com/dodevops/kc](the kc website) for details.
 
 ## Usage
 
-*CloudControl* can be used best with docker-compose. Check out the `sample` directory in a flavour for a sample
+*CloudControl* can be used best with `docker compose`. Check out the `sample` directory in a flavour for a sample
 compose file and to convenience scripts. It includes a small web server written in Go and Vuejs-client dubbed
 "CloudControlCenter", which is used as a status screen. It listens to port 8080 inside the container.
 
 Copy the compose file and configure it to your needs. Check below for configuration options per flavour and feature.
 
-Run `init.sh`. This script basically just runs `docker-compose up -d` and tells you the URL for CloudControlCenter.
+Run `init.sh`. This script basically just runs `docker compose up -d` and tells you the URL for CloudControlCenter.
 Open it and wait for *CloudControl* to finish initializing.
 
 The initialization process will download and configure the additional tools and completes with a message when its done.
 It will run each time when the stack is recreated.
 
-After the initialization process you can simply run `docker-compose exec cli /usr/local/bin/cloudcontrol run` to jump
+After the initialization process you can simply run `docker compose exec cli /usr/local/bin/cloudcontrol run` to jump
 into the running container and work with the installed features.
 
 If you need to change any of the configuration environment variables, rerun the init script afterwards to apply
@@ -178,7 +178,7 @@ provided base images for all architectures (e.g. the Apple ARM-based processors)
 for the available platforms per flavour.
 
 As a workaround this, you can use the [`platform`](https://docs.docker.com/compose/compose-file/compose-file-v2/#platform)
-parameter for docker-compose or the `--platform` parameter for `docker run` to specify a compatible architecture
+parameter for `docker compose` or the `--platform` parameter for `docker run` to specify a compatible architecture
 (e.g. linux/amd64 on Apple ARM-based machines).
 
 ### How can I add an informational text for users of *CloudControl*?
@@ -191,8 +191,8 @@ set the environment variable `MOTD_DISPLAY_DEFAULT` to *yes*.
 
 If you'd like to forward traffic into a cluster using `kubectl port-forward` you can do the following:
 
-* Add a ports key to the cli-service in your docker-compose file to forward a free port on your host to a defined
-port in your container. The docker-compose-files in the sample directories already use port 8081 for this.
+* Add a ports key to the cli-service in your docker-compose.yaml file to forward a free port on your host to a defined
+port in your container. The docker-compose.yaml-files in the sample directories already use port 8081 for this.
 
 * Inside *CloudControl*, check the IP of the container:
 
@@ -218,7 +218,7 @@ kubectl port-forward --address 172.21.0.2 svc/my-service 8081:8080
 * Check out, which host port docker bound to the private port you set up (e.g. 8081)
 
 ```
-docker-compose port cli 8081
+dockercompose port cli 8081
 ```
 
 * Connect to localhost:[host port] on your host
@@ -239,7 +239,7 @@ Also, to not enter your passphrase every time you use the key, you should mount
 container and set the environment variable SSH_AUTH_SOCK to that path. *CloudControl* will automatically fix the
 permissions of that file so the *CloudControl* user can use it.
 
-Here are snippets for your docker-compose file for convenience:
+Here are snippets for your docker-compose.yaml file for convenience:
 
     (...)
     volumes:
@@ -271,15 +271,14 @@ messages look like this:
 It's hard to identify from that who the other *CloudControl* user is, that may have opened a lock. The system
 user can't be changed, but it's possible to set a better hostname than the one Docker autogenerated.
 
-See this docker-compose snippet on how to set a better hostname:
+See this docker-compose.yaml snippet on how to set a better hostname:
 
-    version: "3"
     services:
-    cli:
-    image: "dodevops/cloudcontrol-azure:latest"
-    hostname: "[TODO yourname]"
-    volumes:
-    (...)
+      cli:
+        image: "dodevops/cloudcontrol-azure:latest"
+        hostname: "[TODO yourname]"
+      volumes:
+      (...)
 
 If you set hostname in that snippet to "alice", the state lock will look like this now:
 
@@ -313,7 +312,7 @@ Use the `docker logs` command with the failed container to see the complete log
 installation.
 
 If you are really stuck, you can convince the container to keep running by setting "CONTINUE_ON_ERROR=yes" as an
-environment variable in the docker-compose file. Then you can debug with the running container.
+environment variable in the docker-compose.yaml file. Then you can debug with the running container.
 
 ## Flavours