Apply suggestions from code review

Co-authored-by: Kevin Stich <kevin@kstich.com>

Author: JordonPhillips

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 <amazon-eventstream-headers-format>`
@@ -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