diff --git a/event-schemas/schema/v1/m.room.message.feedback b/event-schemas/schema/v1/m.room.message.feedback
index 1bbfc1ba..2eaed999 100644
--- a/event-schemas/schema/v1/m.room.message.feedback
+++ b/event-schemas/schema/v1/m.room.message.feedback
@@ -1,7 +1,7 @@
 {
     "type": "object",
     "title": "MessageFeedback",
-    "description": "Feedback events are events sent to acknowledge a message in some way. There are two supported acknowledgements: ``delivered`` (sent when the event has been received) and ``read`` (sent when the event has been observed by the end-user). The ``target_event_id`` should reference the ``m.room.message`` event being acknowledged. N.B. not implemented in Synapse, and superceded in v2 CS API by the ``relates_to`` event field.",
+    "description": "**NB: Usage of this event is discouraged in favour of the** `receipts module`_. **Most clients will not recognise this event.** Feedback events are events sent to acknowledge a message in some way. There are two supported acknowledgements: ``delivered`` (sent when the event has been received) and ``read`` (sent when the event has been observed by the end-user). The ``target_event_id`` should reference the ``m.room.message`` event being acknowledged.",
     "allOf": [{
         "$ref": "core-event-schema/room_event.json"
     }],
diff --git a/specification/modules/instant_messaging.rst b/specification/modules/instant_messaging.rst
index 619226df..7934b80a 100644
--- a/specification/modules/instant_messaging.rst
+++ b/specification/modules/instant_messaging.rst
@@ -4,15 +4,37 @@ Instant Messaging
 .. _module:im:
 
 This module adds support for sending human-readable messages to a room. It also
-adds human-readable information to the room itself such as a room name and topic.
+adds support for associating human-readable information with the room itself
+such as a room name and topic.
 
 Events
 ------
 
 {{m_room_message_event}}
 
+
+.. admonition:: Rationale
+
+  Not all clients can display all message types. The most commonly supported
+  message type is raw text. As a result, we chose to have a textual fallback
+  display method represented by the ``body`` key. This means that even if the
+  client cannot display a particular ``msgtype``, they can still display
+  *something*, even if it is just plain text.
+
 {{m_room_message_feedback_event}}
 
+Usage of this event is discouraged for several reasons:
+ - The number of feedback events will grow very quickly with the number of users
+   in the room. This event provides no way to "batch" feedback, unlike the
+   `receipts module`_.
+ - Pairing feedback to messages gets complicated when paginating as feedback
+   arrives before the message it is acknowledging.
+ - There are no guarantees that the client has seen the event ID being
+   acknowledged.
+
+
+.. _`receipts module`: `module:receipts`_
+
 {{m_room_name_event}}
 
 {{m_room_topic_event}}
@@ -20,13 +42,10 @@ Events
 m.room.message msgtypes
 ~~~~~~~~~~~~~~~~~~~~~~~
 
-.. TODO-spec
-   How a client should handle unknown message types.
-
-
 Each `m.room.message`_ MUST have a ``msgtype`` key which identifies the type
 of message being sent. Each type has their own required and optional keys, as
-outlined below.
+outlined below. If a client cannot display the given ``msgtype`` then it MUST
+display the fallback plain text ``body`` key instead.
 
 {{msgtype_events}}
 
@@ -34,9 +53,37 @@ outlined below.
 Client behaviour
 ----------------
 
+Events which have attachments (e.g. ``m.image``, ``m.file``) are advised to be
+uploaded using the `content repository module`_ where available. The
+resulting ``mxc://`` URI can then be used in the ``url`` key. The
+attachment SHOULD be uploaded *prior* to sending the event in order to stop a
+race condition where the recipient receives a link to a non-existent attachment.
+
+.. _`content repository module`: `module:content`_
+
+Recommendations when sending messages
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+- Advise using idempotent PUTs to send messages (and why)
+- Retries (exp backoff, giveup eventually allowing manual retry)
+- Queueing (bucket per room)
+
+Implementing local echo
+~~~~~~~~~~~~~~~~~~~~~~~
+- Local echo (document bug with races) - sending state. Pairing returned event ID.
+
+Displaying membership information with messages
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- Member name linking (incl. pagination aka historical display names)
+
 Server behaviour
 ----------------
 
+- SHOULD enforce the body/msgtype keys are present (can 400 them)
+
 Security considerations
 -----------------------
 
+- Not encrypted, link to E2E module.
+- XSS: Should sanitise ALL KEYS before injecting as unsafe HTML (name/topic/body/etc)
+