From 31f851a1577b82aaff6519d43ebad0043ab4afde Mon Sep 17 00:00:00 2001
From: takageRoshi <36808555+takageRoshi@users.noreply.github.com>
Date: Fri, 23 Nov 2018 09:53:38 -0700
Subject: updated readme

removed this :
  "It appears that VirtualBox does not yet work on Windows 10."
---
 README.md | 2 --
 1 file changed, 2 deletions(-)

(limited to 'README.md')

diff --git a/README.md b/README.md
index b1c6b60..3943a52 100644
--- a/README.md
+++ b/README.md
@@ -148,8 +148,6 @@ If you only want to build using the command line, you might want to run your Vag
 
 If prefer, you can install the gcc-arm toolchain on your local machine, or you might already have it.  You can find all you need [here](http://gnuarmeclipse.livius.net/).
 
-It appears that VirtualBox does not yet work on Windows 10.
-
 If your connection drops out while updating the Vagrant box, you can get stuck, unable to `vagrant up`.  To resolve, you need to delete the temp file - `~/vagrant.d/tmp`.
 
 # Firmware development tips
-- 
cgit v1.2.1