From 370e27b91957c3f1ff253fef6f17d7029e1a1fe9 Mon Sep 17 00:00:00 2001 From: Chris Roberts Date: Wed, 10 May 2017 10:32:04 -0700 Subject: [PATCH] Update documentation for WSL --- website/source/docs/other/wsl.html.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/website/source/docs/other/wsl.html.md b/website/source/docs/other/wsl.html.md index 0e5e3d46d..6e3d88ee9 100644 --- a/website/source/docs/other/wsl.html.md +++ b/website/source/docs/other/wsl.html.md @@ -79,9 +79,9 @@ to user ID mismatches). Vagrant supports enabling user access to provide seamless behavior and control between Vagrant on Windows and Vagrant on WSL. By setting the `VAGRANT_WSL_ACCESS_WINDOWS_USER` environment variable, Vagrant will -allow access to Vagrant managed machines in that user's home path, as -well as share the `VAGRANT_HOME` directory. Below is a demonstration -of the behavior: +allow access to Vagrant managed machines in that user's home path in +Windows (`C:\Users\vagrant` for example), as well as share the `VAGRANT_HOME` +directory. Below is a demonstration of the behavior: ``` C:\Users\vagrant> bash @@ -108,9 +108,9 @@ are unsure of how this may affect your system, do not enable this feature. ## Using Docker -The docker daemon cannot be run in side the Windows Subsystem for Linux. However, +The docker daemon cannot be run inside the Windows Subsystem for Linux. However, the daemon _can_ be run on Windows and accessed by Vagrant while running in the -WSL. Once docker is installed and running on windows, export the following +WSL. Once docker is installed and running on Windows, export the following environment variable to give Vagrant access: ```