diff options
| author |  Eric Anderson <ejona@google.com> | 2015-11-16 15:34:12 -0800 |
|---|---|---|
| committer | Eric Anderson <ejona@google.com> | 2015-11-16 15:34:12 -0800 |
| commit | 94aa0fd393a4f3a49b7ca66eddd44a4c3a449241 (patch) | |
| tree | 402d38131e03c4fb99825e70aef0754a6be7a300 | |
| parent | 118c0a0eec5cedfb4d610483c3e26dacf71bcd4a (diff) | |
Improve grammar/language for clarity
| -rw-r--r-- | doc/PROTOCOL-HTTP2.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/PROTOCOL-HTTP2.md b/doc/PROTOCOL-HTTP2.md index 4c93362350..7a26724c85 100644 --- a/doc/PROTOCOL-HTTP2.md +++ b/doc/PROTOCOL-HTTP2.md @@ -66,9 +66,9 @@ 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 -due to receiving an invalid **ASCII-Value** but value valid 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 +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 application is permitted to echo the value back as metadata. For example, if the metadata is provided to the application as a list in a request, the application should not trigger an error by providing that same list as the metadata in the |