Refactor stage descriptions for TCP server implementation and PING command support.

Author: rohitpaulk

stage_descriptions/base-01-jm1.md

@@ -1,27 +1,4 @@
-In this stage, you'll implement a TCP server that listens on port 6379.
-
-### TCP (Transmission Control Protocol)
-
-[TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol) is the underlying protocol used by protocols like HTTP, SSH, and others you're probably familiar with. Redis also uses TCP for communication between its clients and servers.
-
-Don't worry if you're unfamiliar with the TCP protocol, or what Redis clients & servers are. You'll learn more about this in the next stages.
-
-For this stage, your program should act as a basic TCP server that listens for incoming connections on port 6379.
-
-### Tests
-
-The tester will execute your program like this:
-
-```bash
-$ ./your_program.sh
-```
-
-It will then attempt to connect to your TCP server on port 6379. If the connection succeeds, you’ll pass this stage.
-
-### Notes
-
-- Port 6379 is the default port used by Redis.
-- If you already have a Redis server running on your machine, you’ll see a “port already in use” error. To fix this, stop the existing Redis server before running your code.
+Redis servers communicate over TCP, a protocol that enables reliable data exchange between clients and servers. In this stage, you’ll implement a TCP server that listens on port 6379, just like the real Redis.
 
 {{#reader_is_bot}}
 - In this stage, you can assume that you only need to handle a single client. We'll get to handling multiple clients & multiple requests per client in later stages.

stage_descriptions/base-02-rg2.md

@@ -1,16 +1,23 @@
 In this stage, you'll implement support for the [PING](https://redis.io/commands/ping) command.
 
+### TCP (Transmission Control Protocol)
+
+[TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol) is the underlying protocol used by protocols like HTTP, SSH, and others you're probably familiar with. Redis also uses TCP for communication between its clients and servers.
+
+Don't worry if you're unfamiliar with the TCP protocol, or what Redis clients & servers are. You'll learn more about this in the next stages.
+
 ### Redis Commands
 
 Redis clients communicate with Redis servers by sending [commands](https://redis.io/commands/). For each command, a Redis server sends a response back to the client.
 
 For example:
+
 ```bash
 $ redis-cli SET name Alice
 OK
 ```
-Here, the client sends a [`SET`](https://redis.io/docs/latest/commands/set/) command to store the key `name` with the value `Alice`. The server responds with `OK`, confirming that the action was successful.
 
+Here, the client sends a [`SET`](https://redis.io/docs/latest/commands/set/) command to store the key `name` with the value `Alice`. The server responds with `OK`, confirming that the action was successful.
 
 Both commands and responses are encoded using the [Redis serialization protocol (RESP)](https://redis.io/docs/latest/develop/reference/protocol-spec/). We'll learn more about this in later stages.
 
@@ -46,7 +53,7 @@ Your server should respond with `+PONG\r\n`, which is `PONG` encoded as a [simpl
 ### Notes
 
 - You can ignore the data that the tester sends you for this stage. We'll get to parsing
-client input in later stages. For now, you can just hardcode `+PONG\r\n` as the response.
+  client input in later stages. For now, you can just hardcode `+PONG\r\n` as the response.
 - You can also ignore handling multiple clients and handling multiple PING commands in this stage—we'll get to that in later stages.
 - The exact bytes your program will receive won't just be `PING`. Instead, you'll receive something like this: `*1\r\n$4\r\nPING\r\n`,
-which is the Redis protocol encoding of the `PING` command. We'll learn more about this in later stages.
+  which is the Redis protocol encoding of the `PING` command. We'll learn more about this in later stages.