diff --git a/docs/platforms/android/session-replay/index.mdx b/docs/platforms/android/session-replay/index.mdx
index 422b5a554293cb..76df8d6421dd57 100644
--- a/docs/platforms/android/session-replay/index.mdx
+++ b/docs/platforms/android/session-replay/index.mdx
@@ -69,8 +69,8 @@ SentryAndroid.init(context) { options ->
```
```XML {filename:AndroidManifest.xml}
-
-
+
+
```
## Verify
@@ -113,6 +113,11 @@ options.experimental.sessionReplay.maskAllImages = false
// options.experimental.sessionReplay.redactAllImages = false
```
+```XML {filename:AndroidManifest.xml}
+
+
+```
+
## Error Linking
Errors that happen while a replay is running will be linked to the replay, making it possible to jump between related issues and replays. However, it's **possible** that in some cases the error count reported on the **Replays Details** page won't match the actual errors that have been captured. That's because errors can be lost, and while this is uncommon, there are a few reasons why it could happen:
diff --git a/docs/platforms/android/session-replay/privacy/index.mdx b/docs/platforms/android/session-replay/privacy/index.mdx
index 77bd56d53199de..350d972a74dfc9 100644
--- a/docs/platforms/android/session-replay/privacy/index.mdx
+++ b/docs/platforms/android/session-replay/privacy/index.mdx
@@ -24,6 +24,11 @@ options.experimental.sessionReplay.maskAllImages = false
// options.experimental.sessionReplay.redactAllImages = false
```
+```XML {filename:AndroidManifest.xml}
+
+
+```
+
|Session Replay Unmasked | Session Replay Masked |
|:-----------------------------:|:---------------------------------------: |
| | |