diff --git a/blog/2025-02-14-TSforge/index.md b/blog/2025-02-14-TSforge/index.md
index 04e74c3..03d36c0 100644
--- a/blog/2025-02-14-TSforge/index.md
+++ b/blog/2025-02-14-TSforge/index.md
@@ -39,7 +39,7 @@ Recognizing this, asdcorp decided to investigate how CID validation worked inter
 
 import ReactPlayer from 'react-player'
 
-<ReactPlayer controls width='100%' height='auto' url='/cidtrick.mp4' />
+<ReactPlayer controls width='100%' height='auto' src='/cidtrick.mp4' />
 
 As shown in the video, patching the CID validation code in `sppobjs.dll` allowed us to use a CID made of all zeroes for activation. Crucially though, this activation remained even after clearing the patch by restarting sppsvc. To us, this suggested something very important: **whatever data SPP saves to remember that it's activated is never validated after being written**.
 
diff --git a/docs/genuine-installation-media.md b/docs/genuine-installation-media.md
index bcb2f58..0f46cae 100644
--- a/docs/genuine-installation-media.md
+++ b/docs/genuine-installation-media.md
@@ -131,7 +131,7 @@ Microsoft doesn't allow you to download ISO file directly if browser's useragent
 
 import ReactPlayer from 'react-player'
 
-<ReactPlayer controls width='100%' height='auto' url='/how_to_verify_files.mp4' />
+<ReactPlayer controls width='100%' height='auto' src='/how_to_verify_files.mp4' />
 
 ---