From 8ce97741877cc205f7ced333f617ea9cc79f65d2 Mon Sep 17 00:00:00 2001
From: lixin18 <68135097+lixin963@users.noreply.github.com>
Date: Fri, 15 Dec 2023 01:11:31 -0800
Subject: [PATCH] [Doc] Update PROTOCOL-HTTP2.md (#34907)

more strict  --> stricter

<!--

If you know who should review your pull request, please assign it to that
person, otherwise the pull request would get assigned randomly.

If your pull request is for a specific language, please add the appropriate
lang label.

-->

Closes #34907

COPYBARA_INTEGRATE_REVIEW=https://github.com/grpc/grpc/pull/34907 from lixin963:patch-1 9081eb445ed3ee54d55270a7a8b1241193d31dbd
PiperOrigin-RevId: 591176601
---
 doc/PROTOCOL-HTTP2.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/PROTOCOL-HTTP2.md b/doc/PROTOCOL-HTTP2.md
index 40ec2c10331b4..e5d9696575a99 100644
--- a/doc/PROTOCOL-HTTP2.md
+++ b/doc/PROTOCOL-HTTP2.md
@@ -75,7 +75,7 @@ Base64-encoded values.
 
 **ASCII-Value** should not have leading or trailing whitespace. If it contains
 leading or trailing whitespace, it may be stripped. The **ASCII-Value**
-character range defined is more strict than HTTP. Implementations must not error
+character range defined is stricter than HTTP. Implementations must not error
 due to receiving an invalid **ASCII-Value** that's a valid **field-value** in
 HTTP, but the precise behavior is not strictly defined: they may throw the value
 away or accept the value. If accepted, care must be taken to make sure that the