From 734fa7bbbb96ba413826f33b5586a6c3d8f6ba05 Mon Sep 17 00:00:00 2001 From: Jon Forrest Date: Thu, 13 Oct 2016 14:46:43 -0700 Subject: [PATCH] Update common-issues.html.md --- website/source/docs/virtualbox/common-issues.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/virtualbox/common-issues.html.md b/website/source/docs/virtualbox/common-issues.html.md index 6b0778943..30af68cb2 100644 --- a/website/source/docs/virtualbox/common-issues.html.md +++ b/website/source/docs/virtualbox/common-issues.html.md @@ -16,7 +16,7 @@ as well as solutions for those issues. If Vagrant commands are hanging on Windows because they're communicating to VirtualBox, this may be caused by a permissions issue with VirtualBox. -This is easy to fix. Start VirtualBox as a normal user or as an +This is easy to fix. Starting VirtualBox as a normal user or as an administrator will prevent you from using it in the opposite way. Please keep in mind that when Vagrant interacts with VirtualBox, it will interact with it with the same access level as the console running Vagrant.