Update course definition to remove key expiry mention

Removed mention of automatic key expiry from SET and GET commands.

Author: TropicolX

course-definition.yml

@@ -53,7 +53,7 @@ marketing:
         * Responding to basic commands like `PING` and `ECHO`
         * Parsing the Redis Protocol (RESP) from client requests
         * Handling multiple clients concurrently
-        * Implementing the `SET` and `GET` commands to store and retrieve data, including automatic key expiry.
+        * Implementing the `SET` and `GET` commands to store and retrieve data.
         
         At this stage, your Redis will already feel real. You'll be able to connect with the official `redis-cli`, store data, and retrieve it. 
         
@@ -69,10 +69,10 @@ marketing:
       answer_markdown: |-
         In the first 7 stages, you'll learn:
         * How a TCP server binds to a port and accepts connections (it’s not magic!)
-        * What the Redis Serialization Protocol (RESP) is, and how to parse/encode messages
+        * What the Redis Protocol (RESP) is, and how to parse/encode messages
         * How to handle multiple clients concurrently
         * How to implement commands like `PING`, `ECHO`, `SET`, and `GET`
-        * How to manage a key-value storage
+        * How to manage a key-value store with automatic key expiry
         
         In the advanced stages, you'll discover new programming ideas, such as master-replica synchronization, atomic transactions, and specialized data structures like sorted sets and geospatial indices.
         
@@ -82,7 +82,7 @@ marketing:
       answer_markdown: |-
         Building your own Redis blends network programming, concurrent computing, and system design. If you've mostly built websites or apps, this project takes you a layer deeper to understand how caching and distributed systems work. 
         
-        You’ll build a core piece of infrastructure that applications rely on, such as [Twitter's timeline](https://blog.x.com/engineering/en_us/topics/infrastructure/2017/the-infrastructure-behind-twitter-scale#cache) and [Uber's integrated cache](https://www.uber.com/en-GB/blog/how-uber-serves-over-40-million-reads-per-second-using-an-integrated-cache/).
+        You’ll also be building a core piece of infrastructure that applications rely on, such as [Twitter's timeline](https://blog.x.com/engineering/en_us/topics/infrastructure/2017/the-infrastructure-behind-twitter-scale#cache) and [Uber's integrated cache](https://www.uber.com/en-GB/blog/how-uber-serves-over-40-million-reads-per-second-using-an-integrated-cache/).
         
         Beyond technical depth, there's something uniquely satisfying about understanding a tool used by millions of developers every day. You'll come out of it as a more confident and interesting developer.