Merge pull request #419 from codecrafters-io/TropicolX-patch-64

Revise "Multi-replica propagation #hd5" (stage 54)

Author: TropicolX

stage_descriptions/replication-12-hd5.md

@@ -1,5 +1,11 @@
 In this stage, you'll extend your implementation of the master to support propagating commands to multiple replicas.
 
+### Command Propagation (Recap)
+
+Once a replica completes the handshake and loads the RDB file, it is ready to start receiving live updates from the master. 
+
+Every write command executed on the master must be forwarded to all connected replicas, not just one. This ensures that every replica stays in sync with the master.
+
 ### Tests
 
 The tester will execute your program like this:
@@ -8,21 +14,14 @@ The tester will execute your program like this:
 ./your_program.sh --port <PORT>
 ```
 
-It'll then start **multiple** replicas that connect to your server and execute the following commands:
-
-1. `PING` (expecting `+PONG\r\n` back)
-2. `REPLCONF listening-port <PORT>` (expecting `+OK\r\n` back)
-3. `REPLCONF capa psync2` (expecting `+OK\r\n` back)
-4. `PSYNC ? -1` (expecting `+FULLRESYNC <REPL_ID> 0\r\n` back)
-
-Each replica will expect to receive an RDB file from the master after the handshake is complete.
+It will then start **multiple** replicas that will each connect to your server, complete the handshake, and receive the initial RDB file.
 
-It'll then send `SET` commands to the master from a client (a separate Redis client, not the replicas).
+Next, the tester will send `SET` commands to the master from a separate client.
 
 ```bash
 $ redis-cli SET foo 1
 $ redis-cli SET bar 2
 $ redis-cli SET baz 3
 ```
 
-It'll then assert that each replica received those commands, in order.
+It will then assert that each replica received those commands in the correct order.