Inline "[New in this version]" in auth rules

This makes it much easier to see exactly what is new, and what is existing.

content/rooms/fragments/v3-auth-rules.md

@@ -2,7 +2,7 @@
 toc_hide: true
 ---
 
-{{% added-in this=true %}} In room versions 1 and 2, events need a
+{{< added-in this=true >}} In room versions 1 and 2, events need a
 signature from the domain of the `event_id` in order to be considered
 valid. This room version does not include an `event_id` over federation
 in the same respect, so does not need a signature from that server.

content/rooms/v3.md

@@ -89,7 +89,7 @@ The complete structure of a event in a v3 room is shown below.
 
 ### Authorization rules
 
-{{% added-in this=true %}} `m.room.redaction` events are no longer
+{{< added-in this=true >}} `m.room.redaction` events are no longer
 explicitly part of the auth rules. They are still subject to the
 minimum power level rules, but should always fall into "11. Otherwise,
 allow". Instead of being authorized at the time of receipt, they are
@@ -97,7 +97,7 @@ authorized at a later stage: see the [Handling Redactions](#handling-redactions)
 section below for more information.
 
 <!-- set withVersioning=true so we get all the "new in this version" stuff -->
-{{% rver-fragment name="v3-auth-rules" withVersioning=true %}}
+{{< rver-fragment name="v3-auth-rules" withVersioning=true >}}
 
 ## Unchanged from v2
 

content/rooms/v7.md

@@ -32,7 +32,7 @@ as do the versions v6 is based upon.
 
 ### Authorization rules
 
-{{% added-in this=true %}} For checks performed upon `m.room.member` events, a
+{{< added-in this=true >}} For checks performed upon `m.room.member` events, a
 new point for `membership=knock` is added.
 
 Events must be signed by the server denoted by the `sender` property.

content/rooms/v8.md

@@ -83,11 +83,11 @@ room without invite. Otherwise, the room version inherits all properties of
 
 ### Authorization rules
 
-{{% added-in this=true %}} For checks performed upon `m.room.member` events, new
+{{< added-in this=true >}} For checks performed upon `m.room.member` events, new
 points for handling `content.join_authorised_via_users_server` are added (Rule 4.2
 and 4.3.5).
 
-{{% rver-fragment name="v8-auth-rules" %}}
+{{< rver-fragment name="v8-auth-rules" withVersioning=true >}}
 
 ### Redactions
 

content/rooms/v9.md

@@ -62,7 +62,7 @@ completeness.
 
 ### Authorization rules
 
-{{% rver-fragment name="v8-auth-rules" %}}
+{{< rver-fragment name="v8-auth-rules" >}}
 
 ### State resolution