Original text:
domain(s). DV certificate validation commonly checks claims about properties <del> related to control of a domain name - properties that can be observed by the certificate issuer in an interactive process that can be conducted purely online.  That means that under typical </del>  circumstances, all steps in the request, verification, and issuance process can be represented and performed by Internet protocols with no out-of-band human intervention. The ACME client periodically contacts the CA to get updated certificates, stapled Online Certificate Status Protocol (OCSP) <del> responses, or whatever else would be required to keep the web server functional and its credentials up to date. </del>  In this way, it would be nearly as easy to deploy with a CA-issued certificate as with a self-signed certificate.  Furthermore, the 4. ACME allows a client to request certificate management actions using <del> a set of JavaScript Object Notation (JSON) messages carried over HTTPS RFC8259 RFC2818.  Issuance using ACME resembles a traditional CA's issuance process, in which a user creates an account, requests a </del>  certificate, and proves control of the domain(s) in that certificate in order for the CA to issue the requested certificate. 6.1. Each ACME function is accomplished by the client sending a sequence <del> of HTTPS requests to the server, carrying JSON messages RFC8259.  Use of HTTPS is REQUIRED.  Each subsection of certificate-management below describes the message formats used by the function and the order in which messages are sent. </del>  In most HTTPS transactions used by ACME, the ACME client is the HTTPS client and the ACME server is the HTTPS server.  The ACME server acts query, since the status of the challenge will not change until that time. <del> Clients can explicitly request a retry by resending their response to a challenge in a new POST request (with a new nonce, etc.).  This </del>  allows clients to request a retry when the state has changed (e.g., after firewall rules have been updated).  Servers SHOULD retry a request immediately on receiving such a POST request.  In order to

Reviewer comments:
Thanks NAME - diff looks fine to me.Looks fine to mepurely editorial, good for me.

Revised text:
domain(s). DV certificate validation commonly checks claims about properties  <ins> related to control of a domain name -- properties that can be observed by the certificate issuer in an interactive process that can be conducted purely online.  That means that under typical </ins> circumstances, all steps in the request, verification, and issuance process can be represented and performed by Internet protocols with no out-of-band human intervention. The ACME client periodically contacts the CA to get updated certificates, stapled Online Certificate Status Protocol (OCSP)  <ins> responses RFC6960, or whatever else would be required to keep the web server functional and its credentials up to date. </ins> In this way, it would be nearly as easy to deploy with a CA-issued certificate as with a self-signed certificate.  Furthermore, the 4. ACME allows a client to request certificate management actions using  <ins> a set of JavaScript Object Notation (JSON) messages RFC8259 carried over HTTPS RFC2818.  Issuance using ACME resembles a traditional CA's issuance process, in which a user creates an account, requests a </ins> certificate, and proves control of the domain(s) in that certificate in order for the CA to issue the requested certificate. 6.1. Each ACME function is accomplished by the client sending a sequence  <ins> of HTTPS requests to the server RFC2818, carrying JSON messages RFC8259.  Use of HTTPS is REQUIRED.  Each subsection of certificate- management below describes the message formats used by the function and the order in which messages are sent. </ins> In most HTTPS transactions used by ACME, the ACME client is the HTTPS client and the ACME server is the HTTPS server.  The ACME server acts query, since the status of the challenge will not change until that time.  <ins> Clients can explicitly request a retry by re-sending their response to a challenge in a new POST request (with a new nonce, etc.).  This </ins> allows clients to request a retry when the state has changed (e.g., after firewall rules have been updated).  Servers SHOULD retry a request immediately on receiving such a POST request.  In order to