Added commas, etc.

draft-ietf-jose-fully-specified-algorithms.xml

@@ -661,13 +661,17 @@
 	</t>
       </section>
 
-			<section anchor="KEMs" title="KEMs and Encapsulated Keys">
+      <section anchor="KEMs" title="KEMs and Encapsulated Keys">
 	<t>
-    All key encapsulation mechanisms (KEM) algorithms as described in <xref target="NIST.PQC-API"/> provide three functions: KeyGen(), Encapsulate(), and Decapsulate().
-		In order to consider a KEM algorithm fully specified,
-		there MUST be a single KDF used per KEM Algorithm.
-		For example, the HPKE KEM "0x0010 or DHKEM(P-256, HKDF-SHA256)" as defined in <xref target="RFC9180"/> is fully specified,
-		because it uses a single elliptic curve (secp256r1) and a single KDF (HKDF with SHA256) as described in <xref target="RFC5869"/>.
+	  All key encapsulation mechanisms (KEM) algorithms,
+	  as described in <xref target="NIST.PQC-API"/>,
+	  provide three functions: KeyGen(), Encapsulate(), and Decapsulate().
+	  In order to consider a KEM algorithm fully specified,
+	  there MUST be a single KDF used per KEM Algorithm.
+	  For example, the HPKE KEM "0x0010 or DHKEM(P-256, HKDF-SHA256)",
+	  as defined in <xref target="RFC9180"/>, is fully specified,
+	  because it uses a single elliptic curve (secp256r1) and
+	  a single KDF (HKDF with SHA256), as described in <xref target="RFC5869"/>.
 	</t>
       </section>
 
@@ -850,20 +854,18 @@
         [[ to be removed by the RFC Editor before publication as an RFC ]]
       </t>
 
-			<t>
+      <t>
         -02
         <list style="symbols">
           <t>
-	    Expand references for KEMs
+	    Expanded references for KEMs.
           </t>
-					<t>
-	    Add example of fully specified KEM.
+	  <t>
+	    Added example of a fully-specified KEM.
           </t>
-
         </list>
       </t>
 
-
       <t>
         -01
         <list style="symbols">