Reduce confusion wrt registry sections #800

* Rename “registry section” to “embedded registry”.
* Move paragraph about Patent Policy to its own section.
* Remove the words “purely documentational” because
  it's easy to confuse with “informative” / “non-normative”.
* Add “(only)” to the sentence making registries non-normative
  for Patent Policy purposes.

index.bs

@@ -2844,7 +2844,7 @@ Types of Technical Reports</h3>
 			in order to document collections of values or other data.
 			These are typically published in a separate [=registry report=],
 			although they can also be directly embedded in [=Recommendation Track=] documents
-			as a [=registry section=].
+			as a [=embedded registry=].
 			[=registry definition|Defining a registry=] requires [=wide review=] and [=consensus=],
 			but once set up, changes to registry entries are lightweight
 			and can even be done without a [=Working Group=].
@@ -4672,20 +4672,12 @@ Publishing Registries</h4>
 
 	[=Registries=] can be published either
 	as a stand-alone [=technical report=] on the [=Registry Track=] called a <dfn>registry report</dfn>,
-	or incorporated as part of a [=Recommendation=] as a <dfn>registry section</dfn>.
+	or incorporated as part of a [=Recommendation=] as a <dfn oldids="registry-section">embedded registry</dfn>.
 
-	A [=registry report=] or [=registry section=]
-	is purely documentational,
-	is not subject to the W3C Patent Policy,
-	and <em class=rfc2119>must not</em> contain any requirements on implementations.
-	For the purposes of the Patent Policy [[PATENT-POLICY]],
-	any [=registry section=] in a [=Recommendation track=] document
-	is not a normative portion of that specification.
-
-	The [=registry report=] or [=registry section=] <em class=rfc2119>must</em>:
+	The [=registry report=] or [=embedded registry=] <em class=rfc2119>must</em>:
 	<ul>
 		<li>
-			Clearly label the [=registry report=]/[=registry section|section=],
+			Clearly label the [=registry report=]/[=embedded registry=],
 			its [=registry tables|tables=],
 			and its [=registry definitions=] as such,
 			including a link to [[#registries]] in this Process.
@@ -4865,6 +4857,16 @@ Specifications that Reference Registries</h4>
 		(The Registry should nonetheless contain </code>Basic-Method</code> as an entry.)
 	</div>
 
+<h4 id=reg-pat>
+Registries and Patents</h4>
+
+	A [=registry report=] or [=embedded registry=]
+	is not subject to the W3C Patent Policy,
+	and <em class=rfc2119>must not</em> define any requirements on implementations.
+	For the purposes of the Patent Policy [[PATENT-POLICY]] (only),
+	any [=embedded registry=] in a [=Recommendation track=] document
+	is not a normative portion of that specification.
+
 <h3 id="switching-tracks">
 Switching Tracks</h3>
 
@@ -5696,6 +5698,11 @@ Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November
 		<li>
 			Stop citing the superseded TAG charter.
 			(See <a href="https://github.com/w3c/w3process/issues/794">Issue 794</a>)
+
+		<li>
+			Rename “registry sections” to [=embedded registries=]
+			to avoid confusion over whether they can be split across multiple sections of a [=Recommendation=].
+			(See <a href="https://github.com/w3c/w3process/issues/800">Issue 800</a>)
 	</ul>