diff --git a/crates/matrix-sdk-crypto/src/lib.rs b/crates/matrix-sdk-crypto/src/lib.rs
index 4621a7c9a37..0f0b109e9af 100644
--- a/crates/matrix-sdk-crypto/src/lib.rs
+++ b/crates/matrix-sdk-crypto/src/lib.rs
@@ -414,9 +414,9 @@ pub enum RoomEventDecryptionResult {
 /// To enable decryption the following three steps are needed:
 ///
 /// 1. [The cryptographic identity of your device needs to be published to the
-/// homeserver](#uploading-identity-and-one-time-keys).
+///    homeserver](#uploading-identity-and-one-time-keys).
 /// 2. [Decryption keys coming in from other devices need to be processed and
-/// stored](#receiving-room-keys-and-related-changes).
+///    stored](#receiving-room-keys-and-related-changes).
 /// 3. [Individual messages need to be decrypted](#decrypting-room-events).
 ///
 /// The simplified flowchart
@@ -582,13 +582,13 @@ pub enum RoomEventDecryptionResult {
 /// The method performs two tasks:
 ///
 /// 1. It processes and, if necessary, decrypts each [to-device] event that was
-/// pushed into it, and returns the decrypted events. The original events are
-/// replaced with their decrypted versions.
+///    pushed into it, and returns the decrypted events. The original events are
+///    replaced with their decrypted versions.
 ///
 /// 2. It produces internal state changes that may trigger the creation of new
-/// outgoing requests. For example, if the server informs the client that its
-/// one-time prekeys have been depleted, the OlmMachine will create an outgoing
-/// request to replenish them.
+///    outgoing requests. For example, if the server informs the client that its
+///    one-time prekeys have been depleted, the OlmMachine will create an
+///    outgoing request to replenish them.
 ///
 /// Our updated sync method now looks like this:
 ///
@@ -702,15 +702,15 @@ pub enum RoomEventDecryptionResult {
 /// outlined bellow:
 ///
 /// 1. [Cryptographic devices of other users need to be
-/// discovered](#tracking-users)
+///    discovered](#tracking-users)
 ///
 /// 2. [Secure channels between the devices need to be
-/// established](#establishing-end-to-end-encrypted-channels)
+///    established](#establishing-end-to-end-encrypted-channels)
 ///
 /// 3. [A room key needs to be exchanged with the group](#exchanging-room-keys)
 ///
 /// 4. [Individual messages need to be encrypted using the room
-/// key](#encrypting-room-events)
+///    key](#encrypting-room-events)
 ///
 /// The process for enabling encryption in a two-device scenario is also
 /// depicted in the following sequence diagram: