diff --git a/draft-edm-protocol-greasing.md b/draft-edm-protocol-greasing.md
index b2b36a9..af61ed1 100644
--- a/draft-edm-protocol-greasing.md
+++ b/draft-edm-protocol-greasing.md
@@ -221,7 +221,8 @@ might end up special-casing grease values.
 The patterns for sending grease values can be made more effective by
 coordinating between devices sending the values. One example of coordination
 is having a "flag day" where implementations start sending grease values
-broadly, and measure to see where errors occur.
+broadly, and measure to see where errors occur.  See {{Section 3 of ?TRANSITION=RFC8710}}
+for more considerations concerning the use of a flag day.
 
 ## Don't Handle Grease Values as a Special Case
 
@@ -354,9 +355,13 @@ connections, or phases within a connection.
 
 # Considerations for Protocol Versions {#versions}
 
-There are intrinsic and well-documented issues related to testing version
+{{TRANSITION}} discusses considerations around planning for transitioning
+from an existing protocol, or protocol version, to a new one.
+There are also intrinsic and well-documented issues related to testing version
 negotiation of protocols; see {{?EXTENSIBILITY=RFC6709}} and {{Sections 2.1 and
-3.2 of VIABILITY}}. This section will be expanded with advice for protocol
+3.2 of VIABILITY}}.
+
+This section will be expanded with advice for protocol
 designers and implementers about how to approach these problems.
 
 # Security Considerations