From 8914c33963b775dee58d4052357df5f6ddeab401 Mon Sep 17 00:00:00 2001
From: xerox <xerox@hacks.ltd>
Date: Sun, 19 Apr 2020 09:35:55 +0000
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index d03af62..2950c2e 100644
--- a/README.md
+++ b/README.md
@@ -13,7 +13,7 @@ Before I begin, those who helped me create this project shall be credited.
 Given map/unmap (read/write) of physical memory, one can now systematically map unsigned code into ones kernel.
 Many drivers expose this primitive and now can all be exploited by simply coding a few functions.
 
-## What drivers support physical read/write?
+### What drivers support physical read/write?
 
 Any driver exposing MmMapIoSpace/MmUnmapIoSpace or ZwMapViewOfSection/ZwUnmapViewOfSection can be exploited. This means bios flashing utils, fan speed utils
 (like MSI Afterburner), or general windows system utilities that expose physical read/write.