From 721c5fdd80c2b1f84964930ba9fc8590c8c896c7 Mon Sep 17 00:00:00 2001
From: hyugogirubato <65763543+hyugogirubato@users.noreply.github.com>
Date: Tue, 28 Apr 2026 21:12:08 +0200
Subject: [PATCH] fix keydive mitm doc

---
 docs/advanced/CHALLENGE.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/advanced/CHALLENGE.md b/docs/advanced/CHALLENGE.md
index 6599ef0..8b97bc9 100644
--- a/docs/advanced/CHALLENGE.md
+++ b/docs/advanced/CHALLENGE.md
@@ -17,7 +17,7 @@ To extract unencrypted challenges using KeyDive and HTTP Toolkit, you can follow
 #### 3. Configure KeyDive
 
 - Ensure KeyDive is set up to run on your Android device. This involves:
-    - Installing KeyDive on your device via Magisk or another suitable method.
+    - Installing KeyDive on your device via pip or another suitable method.
     - Running KeyDive with the necessary configurations to intercept DRM-related requests.
 
 #### 4. Intercept Traffic with HTTP Toolkit
@@ -42,7 +42,7 @@ To extract unencrypted challenges using KeyDive and HTTP Toolkit, you can follow
     - Open HTTP Toolkit and ensure interception is enabled for your device's network traffic.
 
 2. **Run KeyDive:**
-    - Execute KeyDive on your Android device, ensuring it intercepts DRM-related requests.
+    - Execute KeyDive on your devive, ensuring it intercepts DRM-related requests.
 
 3. **Access DRM Content:**
     - Access DRM-protected content on your device that triggers DRM challenge requests.