Update revisions, introduce additional "current" status

Author: jspahrsummers

docs/specification/revisions/2024-11-05.md

@@ -1,5 +1,5 @@
 ---
-title: 2024-11-05 (Final)
+title: 2024-11-05 (Current)
 weight: 1
 ---
-This is the initial version of the specification. This revision has been finalized.
+This is the current version of the specification. This revision may continue to receive backwards compatible changes.

docs/specification/revisions/_index.md

@@ -3,6 +3,11 @@ title: Revisions
 cascade:
   type: docs
 ---
-The Model Context Protocol uses revisions that define specific protocol behaviors for each version. Each protocol revision provides guarantees about the functionality and semantics available. The protocol version is exchanged during initialization (see [Versioning]({{< relref "../basic/versioning.md" >}})).
 
-Revisions can be marked as either DRAFT (in-progress specifications) or FINAL (completed specifications). DRAFT revisions may change at any time, while FINAL revisions remain stable once published.
+This page lists the different revisions of the Model Context Protocol. See [Versioning]({{< ref "/specification/basic/versioning" >}}) for more information about how the protocol is versioned.
+
+Revisions may be marked as:
+
+* **Draft**: in-progress specifications, not yet ready for consumption.
+* **Current**: the current protocol version, which is ready for use and may continue to receive [backwards compatible changes]({{< ref "/specification/basic/versioning" >}}).
+* **Final**: past, complete specifications that will not be changed.