Auth rules: PDU content definitions cross-refs (#1050)

* Auth rules: PDU content definitions cross-refs

* Changelog

* Apparently v6 & v7 auth rules aren't in fragments

changelogs/room_versions/newsfragments/1050.clarification

@@ -0,0 +1 @@
+Add cross-references to PDU content definitions from the authorisation rules.

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

@@ -4,11 +4,11 @@ toc_hide: true
 
 The types of state events that affect authorization are:
 
--   `m.room.create`
--   `m.room.member`
--   `m.room.join_rules`
--   `m.room.power_levels`
--   `m.room.third_party_invite`
+-   [`m.room.create`](/client-server-api#mroomcreate)
+-   [`m.room.member`](/client-server-api#mroommember)
+-   [`m.room.join_rules`](/client-server-api#mroom)
+-   [`m.room.power_levels`](/client-server-api#mroompower_levels)
+-   [`m.room.third_party_invite`](/client-server-api#mroomthird_party_invite)
 
 {{% boxes/note %}}
 Power levels are inferred from defaults when not explicitly supplied.

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

@@ -11,11 +11,11 @@ however.
 
 The types of state events that affect authorization are:
 
--   `m.room.create`
--   `m.room.member`
--   `m.room.join_rules`
--   `m.room.power_levels`
--   `m.room.third_party_invite`
+-   [`m.room.create`](/client-server-api#mroomcreate)
+-   [`m.room.member`](/client-server-api#mroommember)
+-   [`m.room.join_rules`](/client-server-api#mroom)
+-   [`m.room.power_levels`](/client-server-api#mroompower_levels)
+-   [`m.room.third_party_invite`](/client-server-api#mroomthird_party_invite)
 
 {{% boxes/note %}}
 Power levels are inferred from defaults when not explicitly supplied.

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

@@ -12,11 +12,11 @@ of receipt, they are authorized at a later stage: see the
 
 The types of state events that affect authorization are:
 
--   `m.room.create`
--   `m.room.member`
--   `m.room.join_rules`
--   `m.room.power_levels`
--   `m.room.third_party_invite`
+-   [`m.room.create`](/client-server-api#mroomcreate)
+-   [`m.room.member`](/client-server-api#mroommember)
+-   [`m.room.join_rules`](/client-server-api#mroom)
+-   [`m.room.power_levels`](/client-server-api#mroompower_levels)
+-   [`m.room.third_party_invite`](/client-server-api#mroomthird_party_invite)
 
 {{% boxes/note %}}
 Power levels are inferred from defaults when not explicitly supplied.

content/rooms/v6.md

@@ -59,11 +59,11 @@ Events must be signed by the server denoted by the `sender` key.
 
 The types of state events that affect authorization are:
 
--   `m.room.create`
--   `m.room.member`
--   `m.room.join_rules`
--   `m.room.power_levels`
--   `m.room.third_party_invite`
+-   [`m.room.create`](/client-server-api#mroomcreate)
+-   [`m.room.member`](/client-server-api#mroommember)
+-   [`m.room.join_rules`](/client-server-api#mroom)
+-   [`m.room.power_levels`](/client-server-api#mroompower_levels)
+-   [`m.room.third_party_invite`](/client-server-api#mroomthird_party_invite)
 
 {{% boxes/note %}}
 Power levels are inferred from defaults when not explicitly supplied.

content/rooms/v7.md

@@ -45,11 +45,11 @@ of receipt, they are authorized at a later stage: see the
 
 The types of state events that affect authorization are:
 
--   `m.room.create`
--   `m.room.member`
--   `m.room.join_rules`
--   `m.room.power_levels`
--   `m.room.third_party_invite`
+-   [`m.room.create`](/client-server-api#mroomcreate)
+-   [`m.room.member`](/client-server-api#mroommember)
+-   [`m.room.join_rules`](/client-server-api#mroom)
+-   [`m.room.power_levels`](/client-server-api#mroompower_levels)
+-   [`m.room.third_party_invite`](/client-server-api#mroomthird_party_invite)
 
 {{% boxes/note %}}
 Power levels are inferred from defaults when not explicitly supplied.