diff --git a/content/client-server-api/modules/end_to_end_encryption.md b/content/client-server-api/modules/end_to_end_encryption.md
index fec2cd01..56d7e75b 100644
--- a/content/client-server-api/modules/end_to_end_encryption.md
+++ b/content/client-server-api/modules/end_to_end_encryption.md
@@ -1488,12 +1488,8 @@ disabling [server-side backups of room keys](#server-side-key-backups). The data
 is stored in the [`m.key_backup`](#mkey_backup) global
 [account data](#client-config).
 
-####### Events
-
 {{% event event="m.key_backup" %}}
 
-####### Client behaviour on sign-in
-
 When a user signs in to a client which supports encryption and key backup:
 
 * If this event type exists in account data and contains the specified property
@@ -1508,16 +1504,12 @@ When a user signs in to a client which supports encryption and key backup:
   clients MUST ignore the existing value and MAY decide whether or not to
   perform key backup, possibly based on user input.
 
-####### Client behaviour on setting change
-
 If the user turns on key backups, clients MUST set this event type in account
 data, to `"enabled": true`.
 
 If the user turns off key backups, clients MUST set this event type in account
 data, to `"enabled": false`.
 
-####### Not actively monitoring this setting
-
 Clients are not required to monitor the `m.key_backup` account data actively.
 Clients MAY monitor the setting but should be aware that changing this setting
 without user interaction based on choices made in a different client (or a