From 8a4f4eba3eaff2992ada258a4436cad3405042f0 Mon Sep 17 00:00:00 2001 From: Matthias Ahouansou Date: Tue, 28 May 2024 18:03:11 +0100 Subject: [PATCH] Correct formatting --- content/rooms/fragments/v8-auth-rules.md | 4 ++-- content/rooms/v10.md | 4 ++-- content/rooms/v11.md | 4 ++-- content/rooms/v3.md | 2 +- content/rooms/v6.md | 4 ++-- content/rooms/v7.md | 4 ++-- 6 files changed, 11 insertions(+), 11 deletions(-) diff --git a/content/rooms/fragments/v8-auth-rules.md b/content/rooms/fragments/v8-auth-rules.md index 7ca3d56a..2b42f839 100644 --- a/content/rooms/fragments/v8-auth-rules.md +++ b/content/rooms/fragments/v8-auth-rules.md @@ -19,8 +19,8 @@ the default power level for users in the room. `m.room.redaction` events are subject to auth rules in the same way as any other event. In practice, that means they will normally be allowed by the auth rules, unless the `m.room.power_levels` event sets a power level requirement for `m.room.redaction` -events via the `events` or `events_default` properties. In particular, the /redact -level/ is **not** considered by the auth rules. +events via the `events` or `events_default` properties. In particular, the _redact +level_ is **not** considered by the auth rules. The ability to send a redaction event does not mean that the redaction itself should be performed. Receiving servers must perform additional checks, as described in diff --git a/content/rooms/v10.md b/content/rooms/v10.md index 0fa203ad..3a08c0b9 100644 --- a/content/rooms/v10.md +++ b/content/rooms/v10.md @@ -94,8 +94,8 @@ the default power level for users in the room. `m.room.redaction` events are subject to auth rules in the same way as any other event. In practice, that means they will normally be allowed by the auth rules, unless the `m.room.power_levels` event sets a power level requirement for `m.room.redaction` -events via the `events` or `events_default` properties. In particular, the /redact -level/ is **not** considered by the auth rules. +events via the `events` or `events_default` properties. In particular, the _redact +level_ is **not** considered by the auth rules. The ability to send a redaction event does not mean that the redaction itself should be performed. Receiving servers must perform additional checks, as described in diff --git a/content/rooms/v11.md b/content/rooms/v11.md index a4905da2..d105e575 100644 --- a/content/rooms/v11.md +++ b/content/rooms/v11.md @@ -101,8 +101,8 @@ the default power level for users in the room. `m.room.redaction` events are subject to auth rules in the same way as any other event. In practice, that means they will normally be allowed by the auth rules, unless the `m.room.power_levels` event sets a power level requirement for `m.room.redaction` -events via the `events` or `events_default` properties. In particular, the /redact -level/ is **not** considered by the auth rules. +events via the `events` or `events_default` properties. In particular, the _redact +level_ is **not** considered by the auth rules. The ability to send a redaction event does not mean that the redaction itself should be performed. Receiving servers must perform additional checks, as described in diff --git a/content/rooms/v3.md b/content/rooms/v3.md index 90b84677..5e560d33 100644 --- a/content/rooms/v3.md +++ b/content/rooms/v3.md @@ -94,7 +94,7 @@ The complete structure of a event in a v3 room is shown below. the same way as any other event. In practice, that means they will normally be allowed by the auth rules, unless the `m.room.power_levels` event sets a power level requirement for `m.room.redaction`events via the `events` or `events_default` properties. In -particular, the /redact level/ is **not** considered by the auth rules. +particular, the _redact level_ is **not** considered by the auth rules. The ability to send a redaction event does not mean that the redaction itself should be performed. Receiving servers must perform additional checks, as described in diff --git a/content/rooms/v6.md b/content/rooms/v6.md index a27b06f6..2cc968fb 100644 --- a/content/rooms/v6.md +++ b/content/rooms/v6.md @@ -69,8 +69,8 @@ the default power level for users in the room. `m.room.redaction` events are subject to auth rules in the same way as any other event. In practice, that means they will normally be allowed by the auth rules, unless the `m.room.power_levels` event sets a power level requirement for `m.room.redaction` -events via the `events` or `events_default` properties. In particular, the /redact -level/ is **not** considered by the auth rules. +events via the `events` or `events_default` properties. In particular, the _redact +level_ is **not** considered by the auth rules. The ability to send a redaction event does not mean that the redaction itself should be performed. Receiving servers must perform additional checks, as described in diff --git a/content/rooms/v7.md b/content/rooms/v7.md index 07525e27..ed4d0055 100644 --- a/content/rooms/v7.md +++ b/content/rooms/v7.md @@ -55,8 +55,8 @@ the default power level for users in the room. `m.room.redaction` events are subject to auth rules in the same way as any other event. In practice, that means they will normally be allowed by the auth rules, unless the `m.room.power_levels` event sets a power level requirement for `m.room.redaction` -events via the `events` or `events_default` properties. In particular, the /redact -level/ is **not** considered by the auth rules. +events via the `events` or `events_default` properties. In particular, the _redact +level_ is **not** considered by the auth rules. The ability to send a redaction event does not mean that the redaction itself should be performed. Receiving servers must perform additional checks, as described in