Review comments.

content/rooms/v11.md

@@ -9,17 +9,6 @@ rules.
 
 ## Client considerations
 
-Clients should no longer depend on the `creator` property in the `content` of
-[`m.room.create`](/client-server-api#mroomcreate) events.  In all room versions,
-clients can rely on `sender` instead to determine a room creator.
-
-Clients should note that the format of [`m.room.redaction`](/client-server-api#mroomredaction)
-events has been modified and look for the `redacts` key under `content` instead
-of a top-level event property.
-
-Clients should note that the `third_party_invite` key of [`m.room.member`](/client-server-api#mroommember)
-events is no longer redacted, *but* will only contain the `signed` key after redaction.
-
 ### Redactions
 
 {{% added-in this=true %}} The top-level `origin`, `membership`, and `prev_state` properties
@@ -33,6 +22,19 @@ The full redaction algorithm follows.
 
 {{% rver-fragment name="v11-redactions" withVersioning="true" %}}
 
+### Event format
+
+Clients should no longer depend on the `creator` property in the `content` of
+[`m.room.create`](/client-server-api#mroomcreate) events.  In all room versions,
+clients can rely on `sender` instead to determine a room creator.
+
+The format of [`m.room.redaction`](/client-server-api#mroomredaction)
+events has been modified. Client should look for the `redacts` key under `content`
+instead of a top-level event property.
+
+The `third_party_invite` key of [`m.room.member`](/client-server-api#mroommember)
+events is no longer redacted, *but* will only contain the `signed` key after redaction.
+
 ## Server implementation components
 
 {{% boxes/warning %}}