Update spelling + aspell

.spellcheck.yml

@@ -5,6 +5,8 @@ matrix:
   expect_match: false   # false -> supress errors if no markdown files were edited
   aspell:
     lang: en
+    mode: none
+    add-filter: url
   dictionary:
     wordlists:
     - .wordlist.txt

.wordlist.txt

@@ -20,4 +20,8 @@ gossipsub
 libp2p
 pubsub
 subnets
-ZXCV
+ZXCV
+BCP
+Bradner
+encodings
+implementers

informational/chatdefs.md

@@ -3,7 +3,7 @@ title: CHAT-DEFINITIONS
 name: Shared definitions for Chat Protocols
 category: Informational
 tags: definitions, terminology, reference
-editor: Jazzz
+editor: 
 contributors:
 ---
 
@@ -47,25 +47,25 @@ Terms are organized into the following categories for clarity and ease of refere
 
 ### Message Types
 
-**Payload**: The encoded bytes as produced by a chat protocol. The term `message` is avoided due to conlicts with other layers.
+**Payload**: The encoded bytes as produced by a chat protocol. The term `message` is avoided due to conflicts with other layers.
 
-**Frame**: A datastructure which is required to implement a chat protocol. Frames are used to disambiguate the objects defined by chat protocols from transport 'messages' and application `content`. 
+**Frame**: A data structure which is required to implement a chat protocol. Frames are used to disambiguate the objects defined by chat protocols from transport 'messages' and application `content`. 
 
 **Content**: The data that is intended for end-users or applications. Chat protocols transmit and route content between clients. 
 
-**ContentType**: The structured format of content. These datastructures represent specific encodings of Text, Image, Audio data. 
+**ContentType**: The structured format of content. These data structures represent specific encodings of Text, Image, Audio data. 
 
 **Delivery Acknowledgement**: A notification from a receiving client to sender that their message was successfully received. While similar to a read-receipt delivery acknowledgements differ in that the acknowledgement originates based on the client, where read-receipts are fired when they are displayed to a user.
 
-**Invite**: An protocol message from one client to another to estblish a communication channel. Invites notify a client that somone wants to communicate with them, and provides the required information to do so.
+**Invite**: An protocol message from one client to another to establish a communication channel. Invites notify a client that someone wants to communicate with them, and provides the required information to do so.
 
 
 ### Transports
 
-**Out-of-Band**: The transfer of information using a channel separate from the defined protocol channel. Data sent Out-of-Band is transmitted using an undefined mechanism. This is used when protocols requires information to be shared with another entity, but it does not describe how that should occur. The responsibility to define how this occurs is on implementors or other protocols in the suite. 
+**Out-of-Band**: The transfer of information using a channel separate from the defined protocol channel. Data sent Out-of-Band is transmitted using an undefined mechanism. This is used when protocols requires information to be shared with another entity, but it does not describe how that should occur. The responsibility to define how this occurs is the implementer or other protocols in the suite. 
 
 
-### TBD
+### Software Entities
 
 **Client**: Software that implements a chat protocol. It is responsible for establishing and maintaining communication with the underlying network, performing protocol operations (e.g., encryption, key management, frame generation), and exposing an interface for higher-level software. A Client serves as the technical component that provides messaging capabilities to Applications.