diff --git a/caw/deployment-impact/draft-ietf-tls-esni.html b/caw/deployment-impact/draft-ietf-tls-esni.html
index 6a31864e..c7909b9d 100644
--- a/caw/deployment-impact/draft-ietf-tls-esni.html
+++ b/caw/deployment-impact/draft-ietf-tls-esni.html
@@ -2650,7 +2650,7 @@
client-facing and backend server requires care, as deployment mistakes
can lead to compatibility issues. These are discussed in Section 8.1.¶
Beyond coordination difficulties, ECH deployments may also induce challenges
-for use cases of information that ECH is designed to encrypt. In particular,
+for use cases of information that ECH protects. In particular,
use cases which depend on this unencrypted information may no longer work
as desired. This is elaborated upon in Section 8.2.¶
diff --git a/caw/deployment-impact/draft-ietf-tls-esni.txt b/caw/deployment-impact/draft-ietf-tls-esni.txt
index 0303396a..705ed469 100644
--- a/caw/deployment-impact/draft-ietf-tls-esni.txt
+++ b/caw/deployment-impact/draft-ietf-tls-esni.txt
@@ -1262,10 +1262,10 @@ Table of Contents
discussed in Section 8.1.
Beyond coordination difficulties, ECH deployments may also induce
- challenges for use cases of information that ECH is designed to
- encrypt. In particular, use cases which depend on this unencrypted
- information may no longer work as desired. This is elaborated upon
- in Section 8.2.
+ challenges for use cases of information that ECH protects. In
+ particular, use cases which depend on this unencrypted information
+ may no longer work as desired. This is elaborated upon in
+ Section 8.2.
8.1. Compatibility Issues