diff --git a/development/roadmap.mdx b/development/roadmap.mdx
index 0b1cbf4..4e4649c 100644
--- a/development/roadmap.mdx
+++ b/development/roadmap.mdx
@@ -5,7 +5,7 @@ description: Our plans for evolving Model Context Protocol (H1 2025)
 
 The Model Context Protocol is rapidly evolving. This page outlines our current thinking on key priorities and future direction for **the first half of 2025**, though these may change significantly as the project develops.
 
-<Note>The ideas presented here are not commitments—we may solve these challenges differently than described, or some may not materialize at all.</Note>
+<Note>The ideas presented here are not commitments—we may solve these challenges differently than described, or some may not materialize at all. This is also not an _exhaustive_ list; we may incorporate work that isn't mentioned here.</Note>
 
 We encourage community participation! Each section links to relevant discussions where you can learn more and contribute your thoughts.
 
@@ -17,7 +17,7 @@ Our top priority is enabling [remote MCP connections](https://github.com/modelco
 
 - [**Service Discovery**](https://github.com/modelcontextprotocol/specification/discussions/69): Defining how clients can discover and connect to remote MCP servers.
 
-- [**Stateless Operations**](https://github.com/modelcontextprotocol/specification/discussions/102): Ensuring MCP servers can operate in serverless environments, where they will need to be mostly stateless.
+- [**Stateless Operations**](https://github.com/modelcontextprotocol/specification/discussions/102): Thinking about whether MCP could encompass serverless environments too, where they will need to be mostly stateless.
 
 ## Reference Implementations