Fixed more typos in examples; clarified that each resource only receives one copy of the message (forked or wrapped)
Messages of type chat that are addressed to the bare JID (localpart@domain) MUST be copied by the receiving server to all of the resources for that user that have non-negative presence priority and have not filtered messages through some other means. The process of making copies is known as "forking."
+Messages of type chat that are addressed to the bare JID (localpart@domain) MUST be delivered according to RFC 6121 ยง 8.5.2, and MUST be copied by the receiving server to all of the resources for that user that are carbons-enabled. The process of making copies is known as "forking."