Replace docker-compose (V1) with docker compose (V2)

src/guide/advanced/running-iroha-on-bare-metal.md

@@ -353,8 +353,8 @@ ports need to be adjusted so there are no collisions. See the
 
 ## Deploy a minimal BFT network
 
-Both of there approaches are messy and error-prone, which is why the
-tutorial uses `docker-compose`. However, this brings you closer to the
+Both of the following approaches could be messy and error-prone, which is why the [Quick Start](../get-started/quick-start.md) tutorial suggests using the `docker compose` command.
+tutorial uses `docker compose`. However, this brings you closer to the
 experience of actually maintaining a functional Iroha peer.
 
 ### Using Environment Variables

src/guide/get-started/python.md

@@ -53,7 +53,7 @@ $ cp -vfr ~/Git/iroha/configs/client/config.json example/config.json
 ::: tip
 
 You can also use the provided `config.json` in the `example` folder if you
-also call `docker-compose up` from that same folder. This has to do with
+also call `docker compose up` from that same folder. This has to do with
 the fact that the configuration for the Docker files in Iroha Python is
 slightly different.
 

src/guide/get-started/quick-start.md

@@ -7,12 +7,10 @@
 
 2. [Install Iroha from GitHub](./install.md).
 
-3. Run `docker-compose` to bring up a network of 4 containerised peers:
-
-   <!-- Check Docker releases: `docker compose` is going to replace `docker-compose` -->
+3. Run `docker compose` to bring up a network of 4 containerised peers:
 
    ```bash
-   $ docker-compose up
+   $ docker compose up
    ```
 
    Depending on your set-up, this might either