diff --git a/draft-ietf-acme-onion.xml b/draft-ietf-acme-onion.xml
index 4b63d68..5aa631e 100644
--- a/draft-ietf-acme-onion.xml
+++ b/draft-ietf-acme-onion.xml
@@ -106,17 +106,17 @@
         </section>
         <section>
           <name>Existing "http-01" Challenge</name>
-          <t>The "http-01" challenge is defined as in <xref target="RFC8555" section="8.3"/> can be used to validate a
+          <t>The "http-01" challenge as defined in <xref target="RFC8555" section="8.3"/> can be used to validate a
             ".onion" Special-Use Domain Names, with the modifications defined in this standard, namely
-            <xref target="client-auth" format="title"/> and <xref target="caa" format="title"/>.</t>
+            <xref target="client-auth" format="title"/>, and <xref target="caa" format="title"/>.</t>
           <t>The ACME server <bcp14>SHOULD</bcp14> follow redirects; note that these <bcp14>MAY</bcp14> be redirects to
             non ".onion" services, and the server <bcp14>SHOULD</bcp14> honour these.</t>
         </section>
         <section>
           <name>Existing "tls-alpn-01" Challenge</name>
-          <t>The "tls-alpn-01" challenge is defined as in <xref target="RFC8737"/> can be used to validate a ".onion"
+          <t>The "tls-alpn-01" challenge as defined in <xref target="RFC8737"/> can be used to validate a ".onion"
             Special-Use Domain Names, with the modifications defined in this standard, namely
-            <xref target="client-auth" format="title"/> and <xref target="caa" format="title"/>.</t>
+            <xref target="client-auth" format="title"/>, and <xref target="caa" format="title"/>.</t>
         </section>
       </section>
       <section>