From 1497b8de8d382a8214251e5ce76b82ce5d8c9ed2 Mon Sep 17 00:00:00 2001 From: Jordon Phillips Date: Wed, 26 Feb 2025 12:39:17 +0100 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Kevin Stich --- docs/source-2.0/aws/amazon-eventstream.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/source-2.0/aws/amazon-eventstream.rst b/docs/source-2.0/aws/amazon-eventstream.rst index 8450e72ee55..dcb8ad190a4 100644 --- a/docs/source-2.0/aws/amazon-eventstream.rst +++ b/docs/source-2.0/aws/amazon-eventstream.rst @@ -47,7 +47,7 @@ Message Format ============== The wire format is structured as a sequence of messages. Messages consist of two -sections: the prelude and the data. The prelude section contains a 4-byte +sections: the prelude and the data. The prelude section contains a four-byte unsigned integer representing the total length of the message and a four-byte unsigned integer representing the total length of the message's headers. The data section consists of the :ref:`headers ` @@ -95,10 +95,10 @@ name MUST only appear once in a message. On the wire, each header begins with a one-byte unsigned integer that indicates the number of UTF-8 encoded bytes used by the header's name. Header names MUST -be at least one byte long. This length prefix if followed by the UTF-8 header +be at least one byte long. This length prefix is followed by the UTF-8 header name. -The name of the header is followed by a one-byte unsigned integer representing +The name of the header is followed by a one-byte unsigned integer indicating the header's data type. The set of types is fixed and not open to extension. Implementations SHOULD bind header types to the corresponding types in their programming language. The following table shows the available types and their