From e04d63ab55fa2ab2c890e4b7e3c68d70e6d51a67 Mon Sep 17 00:00:00 2001
From: krakenrf <78108016+krakenrf@users.noreply.github.com>
Date: Sat, 8 Oct 2022 20:47:15 +1300
Subject: Updated 10. VirtualBox, Docker Images and Install Scripts (markdown)

---
 10.-VirtualBox,-Docker-Images-and-Install-Scripts.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/10.-VirtualBox,-Docker-Images-and-Install-Scripts.md b/10.-VirtualBox,-Docker-Images-and-Install-Scripts.md
index 2d6863d..d56ca9e 100644
--- a/10.-VirtualBox,-Docker-Images-and-Install-Scripts.md
+++ b/10.-VirtualBox,-Docker-Images-and-Install-Scripts.md
@@ -18,7 +18,7 @@ We recommend allocating 8GB of RAM and 4 CPU cores to the system. We have tested
 sudo adduser $USER vboxusers
 ```
 
-**Hyper-V Note**: If you are seeing problems with the VirtualBox image not being stable, and errors in the logs like `[Input/Output Error [Errno 5]`, then this is probably due to a bug between VirtualBox and Windows Hyper-V. To solve this disable Hyper-V, Virtual Machine Platform and Windows Hypervisor Platform in "Turn Windows Features On or Off"
+**Hyper-V Note**: If you are seeing problems with the VirtualBox image not being stable, and errors in the logs like `[Input/Output Error [Errno 5]`, then this is probably due to a bug between VirtualBox and Windows Hyper-V. To solve this disable Hyper-V, Virtual Machine Platform and Windows Hypervisor Platform in "Turn Windows Features On or Off". If you turn off Hyper-V you may also need to disable `Enable Nested Paging` in the Virtual Box settings under System->Acceleration.
 
 ## Docker
 
-- 
cgit v1.2.3