Original text:
view. Switch from using a map to using an array at the message level. <del> While this change means that it is no longer possible to new named parameters to the top level message, it also means that there is not a need to define how older implementations are defined to behave when new fields are present.  Most of the reasons that a new field would need to be defined are adequately addressed by defining a new parameter instead. </del>  Signed messages separate the concept of protected and unprotected attributes that are for the content and the signature. structures are used for the plain text and for the different key management techniques. <del> One of the by products of using the same technique for encrypting and </del>  encoding both the content and the keys using the various key management techniques, is a requirement that all of the key management techniques use an Authenticated Encryption (AE) algorithm. and place in the protected field of the Enc_structure and the COSE_Encrypt structure. <del> Copy the add field from the COSE_Encrypt structure to the </del>  Enc_Structure. Encode the Enc_structure using a CBOR Canonical encoding CBOR- Canonical to get the AAD value. <del> Encrypt the plain text and place it in the ciphertext field.  The AAD value is passed in as part of the encryption process. </del>  For recipient of the message, recursively perform the encryption algorithm for that recipient using the encryption key as the plain 4.3. <del> Verify that the protected field is empty. </del>  <del> Verify that the aad field is empty. </del>  <del> Encrypt the plain text and place in the ciphertext field. </del>  5.

Reviewer comments:
The majority of changes prior to the examples section are to address typos or what I saw as inconsistencies. I will admit I wasn't as diligent as I should have been on those, but I need to take another pass on the document. The examples were reformatted to minimize side scrolling -- and likely fit within the TXT representation.

Revised text:
view. Switch from using a map to using an array at the message level.  <ins> While this change means that it is no longer possible to add new named parameters to the top level message, it also means that there is not a need to define how older implementations are defined to behave when new fields are present.  Most of the reasons that a new field would need to be defined are adequately addressed by defining a new parameter instead. </ins> Signed messages separate the concept of protected and unprotected attributes that are for the content and the signature. structures are used for the plain text and for the different key management techniques.  <ins> One of the byproducts of using the same technique for encrypting and </ins> encoding both the content and the keys using the various key management techniques, is a requirement that all of the key management techniques use an Authenticated Encryption (AE) algorithm. and place in the protected field of the Enc_structure and the COSE_Encrypt structure.  <ins> Copy the 'aad' field from the COSE_Encrypt structure to the </ins> Enc_Structure. Encode the Enc_structure using a CBOR Canonical encoding CBOR- Canonical to get the AAD value.  <ins> Encrypt the plain text and place it in the 'ciphertext' field. The AAD value is passed in as part of the encryption process. </ins> For recipient of the message, recursively perform the encryption algorithm for that recipient using the encryption key as the plain 4.3.  <ins> Verify that the 'protected' field is empty. </ins>  <ins> Verify that the 'aad' field is empty. </ins>  <ins> Encrypt the plain text and place in the 'ciphertext' field. </ins> 5.