diff --git a/doc/source/docker/tutorial-deploy-on-multiple-machines.rst b/doc/source/docker/tutorial-deploy-on-multiple-machines.rst
index 1b2afb29f866..2ad40f0a4924 100644
--- a/doc/source/docker/tutorial-deploy-on-multiple-machines.rst
+++ b/doc/source/docker/tutorial-deploy-on-multiple-machines.rst
@@ -3,8 +3,8 @@ Deploying Flower on Multiple Machines using Docker Compose
 
 This guide will help you set up a Flower project on multiple machines using Docker Compose.
 
-You will learn how to run the Flower client and server components on two different machines,
-with Flower running with TLS enabled and with persisted SuperLink state.
+You will learn how to run the Flower client and server components on two separate machines,
+with Flower configured to use TLS encryption and persist SuperLink state across restarts.
 
 This guide assumes that you have already completed the :doc:`tutorial-quickstart-docker-compose` tutorial.
 It is highly recommended to follow and understand the contents of that tutorial before
@@ -16,8 +16,8 @@ Prerequisites
 Before you begin, make sure you have the following prerequisites:
 
 - The ``flwr`` CLI is :doc:`installed <../how-to-install-flower>` locally.
-- The Docker daemon is running on your local and remote machines.
-- Docker Compose is on both your local and remote machines.
+- The Docker daemon is running on your local machine and the remote machine.
+- Docker Compose is installed on both your local machine and the remote machine.
 - You have an existing Flower project. You can use ``flwr new`` to create one.
 - You can connect to the remote machine from your local machine.
 - Ports ``9091`` and ``9093`` are accessible on the remote machine.
@@ -41,7 +41,7 @@ Step 1: Set Up
                   && mv _tmp/src/docker/complete . \
                   && rm -rf _tmp && cd distributed
 
-#. Get the ip address from the remote machine and save it for later.
+#. Get the IP address from the remote machine and save it for later.
 
 #. If you don't have any certificates, you can generate self-signed certificates using the ``certs.yml``
    Compose file. If you have certificates you can continue with Step 2.
@@ -54,7 +54,7 @@ Step 1: Set Up
       to obtain your certificates.
 
    First, set the environment variable ``SUPERLINK_IP`` and ``SUPEREXEC_IP`` with the IP address
-   from the remote machine. For example, if the IP is ``192.168.2.33``, use:
+   from the remote machine. For example, if the IP is ``192.168.2.33``, execute:
 
    .. code-block:: bash
 
@@ -87,7 +87,7 @@ For example, you can use ``scp`` to copy the directories:
 Step 3: Start the Flower Server Components
 ------------------------------------------
 
-Log into the remote machine using, for example, ssh and run the following command to start the
+Log into the remote machine using ssh and run the following command to start the
 SuperLink and SuperExec services:
 
 .. code-block:: bash
@@ -107,7 +107,7 @@ Go back to your terminal on your local machine.
 Step 4: Start the Flower Client Components
 ------------------------------------------
 
-On your local machine, run the following command to start the SuperNode services:
+On your local machine, run the following command to start the client components:
 
 .. code-block:: bash
 
@@ -138,6 +138,9 @@ To run the project, execute:
 
    $ flwr run quickstart-docker-compose remote-superexec
 
+That's it! With these steps, you've set up Flower on two separate machines, and you're ready to
+start using it.
+
 Step 6: Clean Up
 -----------------