From c7f2c4e5e38fab771cb8875f3810f33738558012 Mon Sep 17 00:00:00 2001
From: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
Date: Fri, 4 Oct 2024 11:00:32 -0700
Subject: [PATCH] fix

---
 contents/blog/mobile-session-replay.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/contents/blog/mobile-session-replay.md b/contents/blog/mobile-session-replay.md
index ce76babd8d4d..b556f0cc42df 100644
--- a/contents/blog/mobile-session-replay.md
+++ b/contents/blog/mobile-session-replay.md
@@ -120,7 +120,7 @@ There are more challenges to solve, specifically around [SwiftUI](https://github
 
 We solved the testing problem in 3 key ways:
 
-1. **Building testing tools:** <TeamMember name="Paul D'Ambra" /> and <TeamMember name="Manoel Aranda Neto"> wanted to keep the rrweb schema for mobile replay to ensure the fewest changes possible to our API and player. To do this, they wrote a [validation and testing tool](https://github.com/PostHog/mobile-replay-data-transformer) to rapidly test the transformations before deploying it in our main app.
+1. **Building testing tools:** <TeamMember name="Paul D'Ambra" /> and <TeamMember name="Manoel Aranda Neto"/> wanted to keep the rrweb schema for mobile replay to ensure the fewest changes possible to our API and player. To do this, they wrote a [validation and testing tool](https://github.com/PostHog/mobile-replay-data-transformer) to rapidly test the transformations before deploying it in our main app.
 
 2. **Using open source apps:** The team found a [list of open source apps](https://github.com/pcqpcq/open-source-android-apps) they could test with. This helped find issues, support more edge cases, and build test coverage.