Incorporate PRs and add metadata label (#921)

* Add install button

* Add links for more info on using VirtualBox

* Update about.md (#813)

* Update user-suport.md (#814)

* Update user-suport.md

* Update user-support.md

* Grammar and specificity correction

Co-authored-by: Matt Wojciakowski <[email protected]>

* Use correct capitalization of VMware (#818)

* Update wsl-config.md: Fix `memory` default (#820)

This commit reflect change in default memory consumption introduced in `20175` build

https://docs.microsoft.com/windows/wsl/release-notes#build-20175

* Fix a typo (#900)

Fix a typo.

* add code quotes around wsl --mount (#906)

* Update troubleshooting.md (#907)

Add a missing link to the github repo

* Removed dead link in the build-custom-distro.md file (#917)

The removed link ("Command-line UserVoice portal") leads to a 404 page that says: "This UserVoice instance is no longer available."

* Add OKR metadata label

* Change to secure link

* fix link

Co-authored-by: Himanshu maurya <[email protected]>
Co-authored-by: Michael Geary <[email protected]>
Co-authored-by: Alexander Georgievskiy <[email protected]>
Co-authored-by: Aleksandar Nikolić <[email protected]>
Co-authored-by: John Zabroski <[email protected]>
Co-authored-by: soolo <[email protected]>
Co-authored-by: Darian Benam <[email protected]>

Author: 8 people

WSL/about.md

@@ -20,7 +20,7 @@ You can:
     * Tools: vim, emacs, tmux
     * Languages: [NodeJS](https://docs.microsoft.com/windows/nodejs/setup-on-wsl2), Javascript, [Python](https://docs.microsoft.com/windows/python/web-frameworks), Ruby, C/C++, C# & F#, Rust, Go, etc.
     * Services: SSHD, [MySQL](./tutorials/wsl-database.md), Apache, lighttpd, [MongoDB](./tutorials/wsl-database.md), [PostgreSQL](./tutorials/wsl-database.md).
-* Install additional software using own GNU/Linux distribution package manager.
+* Install additional software using your own GNU/Linux distribution package manager.
 * Invoke Windows applications using a Unix-like command-line shell.
 * Invoke GNU/Linux applications on Windows.
 
@@ -67,6 +67,6 @@ Individual Linux distributions can be run with either the WSL 1 or WSL 2 archite
 
 * [Reference WSL commands](./reference.md)
 
-* [Build a custom distributions](./build-custom-distro.md)
+* [Build custom distributions](./build-custom-distro.md)
 
 * [Read the WSL Release Notes](./release-notes.md)

WSL/build-custom-distro.md

@@ -41,4 +41,3 @@ Follow the instructions on the [Distro Launcher GitHub repo](https://github.com/
 
 - [Distro Launcher GitHub repo](https://github.com/Microsoft/WSL-DistroLauncher)
 - [GitHub issue tracker for WSL](https://github.com/Microsoft/BashOnWindows/issues)
-- [Command-line UserVoice portal](https://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo/category/161892-bash)

WSL/compare-versions.md

@@ -5,6 +5,7 @@ keywords: BashOnWindows, bash, wsl, windows, windowssubsystem, gnu, linux, ubunt
 ms.date: 09/15/2020
 ms.topic: conceptual
 ms.localizationpriority: high
+ms.custom: contperfq1
 ---
 
 # Comparing WSL 1 and WSL 2
@@ -26,7 +27,7 @@ Feature | WSL 1 | WSL 2
  Integration between Windows and Linux| ✅|✅
  Fast boot times| ✅ | ✅
  Small resource foot print| ✅ |✅
- Runs with current versions of VMWare and VirtualBox| ✅ | ✅
+ Runs with current versions of VMware and VirtualBox| ✅ | ✅
  Managed VM| ❌ | ✅
  Full Linux Kernel| ❌ |✅
  Full system call compatibility| ❌ | ✅
@@ -48,7 +49,7 @@ You can access your Linux root file system with Windows apps and tools like File
 WSL 2 is only available in Windows 10, Version 1903, Build 18362 or higher. Check your Windows version by selecting the **Windows logo key + R**, type **winver**, select **OK**. (Or enter the `ver` command in Windows Command Prompt). You may need to [update to the latest Windows version](ms-settings:windowsupdate). For builds lower than 18362, WSL is not supported at all.
 
 > [!NOTE]
-> WSL 2 will work with [VMWare 15.5.5+](https://blogs.vmware.com/workstation/2020/05/vmware-workstation-now-supports-hyper-v-mode.html) and [VirtualBox 6+](https://www.virtualbox.org/wiki/Changelog-6.0).
+> WSL 2 will work with [VMware 15.5.5+](https://blogs.vmware.com/workstation/2020/05/vmware-workstation-now-supports-hyper-v-mode.html) and [VirtualBox 6+](https://www.virtualbox.org/wiki/Changelog-6.0). Learn more in our [WSL 2 FAQs.](./wsl2-faq.md#will-i-be-able-to-run-wsl-2-and-other-3rd-party-virtualization-tools-such-as-vmware-or-virtualbox)
 
 ## Whats new in WSL 2
 

WSL/release-notes.md

@@ -13,7 +13,7 @@ ms.localizationpriority: high
 ## Build 20211
 For general Windows information on build 20211 visit the [Windows blog](https://blogs.windows.com/windows-insider/2020/09/10/announcing-windows-10-insider-preview-build-20211/).
 
-* Introduce wsl.exe --mount for mounting physical or virtual disks. For more information see [Access Linux filesystems in Windows and WSL 2](https://devblogs.microsoft.com/commandline/access-linux-filesystems-in-windows-and-wsl-2/).
+* Introduce `wsl.exe --mount` for mounting physical or virtual disks. For more information see [Access Linux filesystems in Windows and WSL 2](https://devblogs.microsoft.com/commandline/access-linux-filesystems-in-windows-and-wsl-2/).
 * Fix crash in LxssManager service when checking if the VM is idle. [GH 5768]
 * Support for compressed VHD files. [GH 4103]
 * Ensure that Linux user mode libs installed to c:\windows\system32\lxss\lib are preserved across OS upgrade. [GH 5848]

WSL/troubleshooting.md

@@ -9,7 +9,7 @@ ms.localizationpriority: high
 
 # Troubleshooting Windows Subsystem for Linux
 
-For support with issues related to WSL, please see our GitHub repo:
+For support with issues related to WSL, please see our GitHub repo: https://github.com/Microsoft/wsl/issues
 
 ## Search for any existing issues related to your problem
 
@@ -40,7 +40,7 @@ Lastly, if your issue is related to the Windows Terminal, Windows Console, or th
 
 This is likely because your machine has not yet taken the backport for WSL 2. The simplest way to resolve this is by going to Windows Settings and clicking 'Check for Updates' to install the latest updates on your system. You can view the full instructions on taking the backport [here](https://devblogs.microsoft.com/commandline/wsl-2-support-is-coming-to-windows-10-versions-1903-and-1909/#how-do-i-get-it). 
 
-If you hit 'Check for Updates' and still do not receive the update you can install KB KB4566116 manually by [following this link](http://www.catalog.update.microsoft.com/Search.aspx?q=KB4566116).  
+If you hit 'Check for Updates' and still do not receive the update you can install KB KB4566116 manually by [following this link](https://www.catalog.update.microsoft.com/Search.aspx?q=KB4566116).  
 
 ### Error: 0x1bc when `wsl --set-default-version 2`
 This may happen when 'Display Language' or 'System Locale' setting is not English.

WSL/tutorials/wsl-containers.md

@@ -122,7 +122,7 @@ Let's use Docker to create a development container for an existing app project.
 
     ![VS Code run debug configuration](../media/vscode-run-config.png)
 
-10. From inside VS Code, select **Run** > **Start debugging** (or just press the **F5** key). This will open a terminal inside VS Code and you should see a result saying something like: "Starting development server at http://127.0.0.1:8000/ Quit the server with CONTROL-C." Hold down the Control key and select the address displayed to open your app in your default web browser and see your project running inside of it's container.
+10. From inside VS Code, select **Run** > **Start debugging** (or just press the **F5** key). This will open a terminal inside VS Code and you should see a result saying something like: "Starting development server at http://127.0.0.1:8000/ Quit the server with CONTROL-C." Hold down the Control key and select the address displayed to open your app in your default web browser and see your project running inside of its container.
 
     ![VS Code running a docker container](../media/vscode-running-in-container.png)
 
@@ -157,4 +157,4 @@ For more help with general troubleshooting issues in WSL, see the [Troubleshooti
 - [VS Code Blog: Guidelines for choosing a development environment](https://code.visualstudio.com/docs/containers/choosing-dev-environment#_guidelines-for-choosing-a-development-environment)
 - [VS Code Blog: Using Docker in WSL 2](https://code.visualstudio.com/blogs/2020/03/02/docker-in-wsl2)
 - [VS Code Blog: Using Remote Containers in WSL 2](https://code.visualstudio.com/blogs/2020/07/01/containers-wsl)
-- [Hanselminutes Podcast: Making Docker lovely for Developers with Simon Ferquel](https://hanselminutes.com/736/making-docker-lovely-for-developers-with-simon-ferquel)
+- [Hanselminutes Podcast: Making Docker lovely for Developers with Simon Ferquel](https://hanselminutes.com/736/making-docker-lovely-for-developers-with-simon-ferquel)

WSL/user-support.md

@@ -11,9 +11,9 @@ ms.localizationpriority: high
 
 Once you have [enabled WSL and installed a Linux distribution from the Microsoft Store](./install-win10.md), the first step you will be asked to complete when opening your newly installed Linux distribution is to create an account, including a **User Name** and **Password**.
 
-- This **User Name** and **Password** is specific to your Linux distribution and has no bearing on your Windows user name.
+- This **User Name** and **Password** is specific to each separate Linux distribution that you install and has no bearing on your Windows user name.
 
-- Once you create this **User Name** and **Password**, the account will be your default user for the distribution and automatically sign-in on launch.
+- Once you create a **User Name** and **Password**, the account will be your default user for the distribution and automatically sign-in on launch.
 
 - This account will be considered the Linux administrator, with the ability to run `sudo` (Super User Do) administrative commands.
 
@@ -29,7 +29,7 @@ Most distributions ship with an empty or minimal package catalog. We strongly re
 sudo apt update && sudo apt upgrade
 ```
 
-Windows does not automatically update or upgrade your Linux distribution(s). This is a task that the most Linux users prefer to control themselves.
+Windows does not automatically update or upgrade your Linux distribution(s). This is a task that most Linux users prefer to control themselves.
 
 ## Reset your Linux password
 

WSL/wsl-config.md

@@ -340,7 +340,7 @@ These settings affect the VM that powers any WSL 2 distribution.
 | key | value | default | notes|
 |:----|:----|:----|:----|
 | kernel | string | The Microsoft built kernel provided inbox | An absolute Windows path to a custom Linux kernel. |
-| memory | size | 80% of your total memory on Windows * | How much memory to assign to the WSL 2 VM. |
+| memory | size | 50% of total memory on Windows or 8GB, whichever is less; on builds before 20175: 80% of your total memory on Windows | How much memory to assign to the WSL 2 VM. |
 | processors | number | The same number of processors on Windows | How many processors to assign to the WSL 2 VM. |
 | localhostForwarding | boolean | `true` | Boolean specifying if ports bound to wildcard or localhost in the WSL 2 VM should be connectable from the host via localhost:port. |
 | kernelCommandLine | string | Blank | Additional kernel command line arguments. |

WSL/wsl2-faq.md

@@ -25,13 +25,13 @@ We currently have no plans to deprecate WSL 1. You can run WSL 1 and WSL 2 distr
 
 ## Will I be able to run WSL 2 and other 3rd party virtualization tools such as VMware, or VirtualBox?
 
-Some 3rd party applications cannot work when Hyper-V is in use, which means they will not be able to run when WSL 2 is enabled, such as VMware and VirtualBox. However, recently both VirtualBox and VMware have released versions that support Hyper-V and WSL2! You can learn more about [VirtualBox's changes here][1] and [VMware's changes here][4].
+Some 3rd party applications cannot work when Hyper-V is in use, which means they will not be able to run when WSL 2 is enabled, such as VMware and VirtualBox. However, recently both VirtualBox and VMware have released versions that support Hyper-V and WSL2. Learn more about [VirtualBox's changes here][1] and [VMware's changes here][4]. For troubleshooting issues, take a look at the [VirtualBox issue discussions in the WSL repo on GitHub](https://github.com/MicrosoftDocs/WSL/issues?q=is%3Aissue+virtualbox+sort%3Acomments-desc).
 
 We are consistently working on solutions to support third-party integration of Hyper-V. For example, we expose a set of APIs called [Hypervisor Platform][2] that third-party virtualization providers can use to make their software compatible with Hyper-V. This lets applications use the Hyper-V architecture for their emulation such as [the Google Android Emulator][3], and VirtualBox 6 and above which are both now compatible with Hyper-V.
 
 ## Can I access the GPU in WSL 2? Are there plans to increase hardware support?
 
-We have released support for accessing the GPU inside of WSL 2 distros! This means you can now use WSL for machine learning, artificial intelligence, and data science scenarios more easily when big data sets are involved. You can find a tutorial to [get started with GPU support here](./tutorials/gpu-compute). As of right now WSL 2 does not include serial support, or USB device support. We are investigating the best way to add these features.
+We have released support for accessing the GPU inside of WSL 2 distros! This means you can now use WSL for machine learning, artificial intelligence, and data science scenarios more easily when big data sets are involved. Check out the [get started with GPU support](./tutorials/gpu-compute.md) tutorial. As of right now WSL 2 does not include serial support, or USB device support. We are investigating the best way to add these features.
 
 ## Will WSL 2 be able to use networking applications?