From 73eec3386dc843761e37bfff6420e173cff891e8 Mon Sep 17 00:00:00 2001
From: Tejas <47889755+tejas15802@users.noreply.github.com>
Date: Tue, 5 Jul 2022 19:48:49 +0530
Subject: [PATCH] Reference to memory dump removed

---
 doc/source/Windows.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/source/Windows.rst b/doc/source/Windows.rst
index 2f8d58a04..a9e712fc9 100644
--- a/doc/source/Windows.rst
+++ b/doc/source/Windows.rst
@@ -40,7 +40,7 @@ Example
 Example 1
 ~~~~~~~~~
 
-In this example we will be using memory dump from PragyanCTF'22. The dump is available `here <https://drive.google.com/file/d/1VPIdqIDFkOi3zGET2g00s1y-OeWOUqyi/view?usp=sharing>`_.
+In this example we will be using memory dump from PragyanCTF'22. 
 We will limit the discussion to memory forensics with volatility3 and not extend to other parts of the challenges. 
 
 In windows memory forensics using volatility3, most of the times we do not require creating a ISF file.