Original text:
identifier for that key and the HPKE algorithms that are used with that key. <del> The identity of an that will accept relay requests carrying an encapsulated request as its content and forward the content in these requests to a single . See proxy-state for more information about the mapping between . </del>  This information allows the to make a request of a with that resource having only a limited ability to correlate that request with the IP 3. A needs to acquire information about the of the in order to send <del> encapsulated requests.  In order to ensure that do not encapsulate </del>  messages that other entities can intercept, the MUST be authenticated and have integrity protection. Errors detected by the after successfully removing encapsulation and errors detected by the MUST be sent in an .  This might be because <del> the request is malformed or the does not produce a response.  In either case the can generate a response with an appropriate error status code (such as 400 (Bad Request) or 504 (Gateway Timeout); see HTTP and HTTP, respectively).  This response is encapsulated in the same way as a successful response. </del>  Errors in the encapsulation of requests mean that responses cannot be encapsulated.  This includes cases where the is incorrect or Connections between the , Oblvious Relay Resource, and MUST use HTTPS in order to provide unlinkability in the presence of a network <del> observer.  The scheme of the encapsulated request determines what is used between the Oblivious Gateway and Target Resources, though using HTTPS is RECOMMENDED; see server-responsibilities. </del>  To achieve the stated privacy goals, the cannot be operated by the same entity as the . However, colocation of the and simplifies the

Reviewer comments:
We weren't always capitalizing "Encapsulated Request". This does more, in direct opposition to the changes in . If we don't take that (it seems we at an impasse there), then we should at least be consistent.
NAME I resolved conflicts, but please double check the intro paragraph that had Mark's proposed changes.

Revised text:
identifier for that key and the HPKE algorithms that are used with that key.  <ins> The identity of an that will accept relay requests carrying an as its content and forward the content in these requests to a single . See proxy-state for more information about the mapping between . </ins> This information allows the to make a request of a with that resource having only a limited ability to correlate that request with the IP 3. A needs to acquire information about the of the in order to send  <ins> Encapsulated Requests.  In order to ensure that do not encapsulate </ins> messages that other entities can intercept, the MUST be authenticated and have integrity protection. Errors detected by the after successfully removing encapsulation and errors detected by the MUST be sent in an .  This might be because  <ins> the is malformed or the does not produce a response.  In either case the can generate a response with an appropriate error status code (such as 400 (Bad Request) or 504 (Gateway Timeout); see HTTP and HTTP, respectively).  This response is encapsulated in the same way as a successful response. </ins> Errors in the encapsulation of requests mean that responses cannot be encapsulated.  This includes cases where the is incorrect or Connections between the , Oblvious Relay Resource, and MUST use HTTPS in order to provide unlinkability in the presence of a network  <ins> observer.  The scheme of the determines what is used between the Oblivious Gateway and Target Resources, though using HTTPS is RECOMMENDED; see server-responsibilities. </ins> To achieve the stated privacy goals, the cannot be operated by the same entity as the . However, colocation of the and simplifies the