Clarify master handshake process details

Author: TropicolX

stage_descriptions/replication-08-fj0.md

@@ -4,17 +4,17 @@ In this stage, we'll start implementing support for receiving a replication hand
 
 Up until now, we've been implementing the handshake from the replica's perspective. Now we'll implement the same handshake on the master side.
 
-As a recap, the master receives the following for the handshake process:
+As a recap, the master receives the following from the replica during the handshake process:
 
-1. A `PING` from the replica
-2. `REPLCONF` twice from the replica
-3. `PSYNC` from the replica
+1. A `PING` command
+2. Two `REPLCONF` commands
+3. A `PSYNC` command
 
-Your Redis server already supports the `PING` command, so there's no additional work to do for the first part.
+Your Redis server already supports the `PING` command, so there's no additional work to do for the first step.
 
-In this stage, you'll add support for receiving the `REPLCONF` command from the replica as a master.
+In this stage, you'll add support for receiving the two `REPLCONF` commands as a master.
 
-You'll receive `REPLCONF` twice from the replica. For the purposes of this challenge, you can safely ignore the arguments for both commands and simply respond with `+OK\r\n`. That's the string `OK` encoded as a [simple string](https://redis.io/docs/latest/develop/reference/protocol-spec/#simple-strings)
+For the purposes of this challenge, you can safely ignore the arguments for both commands and simply respond with `+OK\r\n`. That's the string `OK` encoded as a [simple string](https://redis.io/docs/latest/develop/reference/protocol-spec/#simple-strings)
 
 ### Tests