diff --git a/support/documentation/content/en/technical/slow_mode.md b/support/documentation/content/en/technical/slow_mode.md
index 73ceeec192..a606bafc34 100644
--- a/support/documentation/content/en/technical/slow_mode.md
+++ b/support/documentation/content/en/technical/slow_mode.md
@@ -186,3 +186,31 @@ Moreover, each time a user sends a text message, the client SHOULD prevent the u
 To avoid some frustrating behaviour, in case there is some lag on the server for example, the client SHOULD prevent sending new messages for a slightly longer duration, than the slow mode duration (for example by adding 100 or 200ms). Indeed, if the first message is processed with some delay by the server, it could consider that the duration is not passed yet when receiving the next one.
 
 If the `muc#roomconfig_slow_mode_duration` field is present in room configuration form (as described in "4.1 Activating Slow Mode in the MUC Room configuration"), the client SHOULD add an input field when the room's owner modifies the room configuration. This field SHOULD only accept positive integer as value (0 included, which means the feature is disabled).
+
+## Appendices
+
+### Appendix A: Document information
+
+TO BE DONE
+
+### Appendix B: Author Information
+
+John Livingston
+
+Website: https://www.john-livingston.fr
+
+### Appendix C: Legal Notices
+
+TO BE DONE
+
+### Appendix D: Relation to XMPP
+
+The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 6120) and XMPP IM (RFC 6121) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.
+
+### Appendix E: Discussion Venue
+
+TO BE DONE
+
+### Appendix F: Requirements Conformance
+
+The following requirements keywords as used in this document are to be interpreted as described in [RFC 2119](https://www.ietf.org/rfc/rfc2119.txt): "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".