diff --git a/draft-ietf-sidrops-8210bis.xml b/draft-ietf-sidrops-8210bis.xml
index 4ed4b6b..f2a3c29 100644
--- a/draft-ietf-sidrops-8210bis.xml
+++ b/draft-ietf-sidrops-8210bis.xml
@@ -176,17 +176,18 @@
           </t>
           <t hangText="Serial Number:">
             "Serial Number" is a 32-bit strictly increasing unsigned
-            integer which wraps from 2^32-1 to 0.  It denotes the
-            logical version of a cache.  A cache increments the value
-            when it successfully updates its data from a parent cache or
-            from primary RPKI data.  While a cache is receiving updates,
-            new incoming data and implicit deletes are associated with
-            the new Serial Number but MUST NOT be sent until the fetch
-            is complete.  A Serial Number is not commensurate between
-            different caches or different protocol versions, nor need it
-            be maintained across resets of the cache server.  See <xref
+            integer which wraps from 2^32-1 to 0.  See <xref
             target="RFC1982"/> on DNS Serial Number Arithmetic for too
-            much detail on the topic.
+            much detail on serial number wrapping.  The Serial Number
+            denotes the logical version of a cache.  A cache increments
+            the value when it successfully updates its data from a
+            parent cache or from primary RPKI data.  While a cache is
+            receiving updates, new incoming data and implicit deletes
+            are associated with the new Serial Number but MUST NOT be
+            sent until the fetch is complete.  A Serial Number is not
+            commensurate between different caches or different protocol
+            versions, nor need it be maintained across resets of the
+            cache server.
           </t>
           <t hangText="Session ID:">
             When a cache server is started, it generates a Session ID