From 07a412cb7805482ba182280186c78480baae0d98 Mon Sep 17 00:00:00 2001 From: Blake-Madden Date: Tue, 19 Dec 2023 05:45:46 -0500 Subject: [PATCH] Fix a few typos --- WSL/file-permissions.md | 2 +- WSL/intune.md | 2 +- WSL/networking.md | 2 +- WSL/troubleshooting.md | 4 ++-- WSL/tutorials/wsl-database.md | 4 ++-- WSL/wsl-config.md | 2 +- WSL/wsl2-mount-disk.md | 4 ++-- 7 files changed, 10 insertions(+), 10 deletions(-) diff --git a/WSL/file-permissions.md b/WSL/file-permissions.md index 0a039851..99a2fe92 100644 --- a/WSL/file-permissions.md +++ b/WSL/file-permissions.md @@ -41,7 +41,7 @@ The result depends on if the file already has existing metadata. ##### DrvFS file does not have metadata (default) -If the file has no metadata associated with it then we translate the effective permissions of the Windows user to read/write/execute bits and set them to the this as the same value for user, group, and other. For example, if your Windows user account has read and execute access but not write access to the file then this will be shown as `r-x` for user, group and other. If the file has the 'Read Only' attribute set in Windows then we do not grant write access in Linux. +If the file has no metadata associated with it then we translate the effective permissions of the Windows user to read/write/execute bits and set them to this as the same value for user, group, and other. For example, if your Windows user account has read and execute access but not write access to the file then this will be shown as `r-x` for user, group and other. If the file has the 'Read Only' attribute set in Windows then we do not grant write access in Linux. ##### The file has metadata diff --git a/WSL/intune.md b/WSL/intune.md index 6e79a78f..6bd0e550 100644 --- a/WSL/intune.md +++ b/WSL/intune.md @@ -26,7 +26,7 @@ To maximize security in an enterprise environment, we recommend that you specify | Allow custom networking configuration | Disabled | When set to disabled, this policy disables custom networking configuration via .wslconfig (wsl2.networkingmode). This policy only applies to Store WSL. | | Allow user setting firewall configuration | Disabled | When set to disabled, this policy disables firewall configuration via .wslconfig (wsl2.firewall). This policy only applies to Store WSL. | | Allow nested virtualization | Disabled | When set to disabled, this policy disables nested virtualization configuration via .wslconfig (wsl2.nestedVirtualization). This policy only applies to Store WSL. | -| Allow kernel debugging | Disabled | When set to disabled, this policy disables kernel kernel debugging configuration via .wslconfig (wsl2.kernelDebugPort). This policy only applies to Store WSL. | +| Allow kernel debugging | Disabled | When set to disabled, this policy disables kernel debugging configuration via .wslconfig (wsl2.kernelDebugPort). This policy only applies to Store WSL. | ## Control access to WSL diff --git a/WSL/networking.md b/WSL/networking.md index 98242571..37517c72 100644 --- a/WSL/networking.md +++ b/WSL/networking.md @@ -91,7 +91,7 @@ This new mode addresses networking issues seen with using a NAT (Network Address ## DNS Tunneling -Setting [`dnsTunneling=true` under `[wsl2]` in the `.wslconfig` file](./wsl-config.md#configuration-setting-for-wslconfig) has WSL use a virtulization feature to answer DNS requests from within WSL, instead of requesting them over a networking packet. This feature is aimed to improve compatibility with VPNs, and other complex networking set ups. +Setting [`dnsTunneling=true` under `[wsl2]` in the `.wslconfig` file](./wsl-config.md#configuration-setting-for-wslconfig) has WSL use a virtualization feature to answer DNS requests from within WSL, instead of requesting them over a networking packet. This feature is aimed to improve compatibility with VPNs, and other complex networking set ups. ## Auto Proxy diff --git a/WSL/troubleshooting.md b/WSL/troubleshooting.md index f5279b1f..d68f864c 100644 --- a/WSL/troubleshooting.md +++ b/WSL/troubleshooting.md @@ -20,7 +20,7 @@ The [WSL product repo issues](https://github.com/Microsoft/wsl/issues) enables y You can also: - **File a documentation issue** using the [WSL docs repo](https://github.com/MicrosoftDocs/wsl/issues). To contribute to the WSL docs, see the [Microsoft Docs contributor guide](/contribute). -- **File a Windows Terminal** issue using the the [Windows Terminal product repo](https://github.com/microsoft/terminal/issues) if your problem is related more to the Windows Terminal, Windows Console, or the command-line UI. +- **File a Windows Terminal** issue using the [Windows Terminal product repo](https://github.com/microsoft/terminal/issues) if your problem is related more to the Windows Terminal, Windows Console, or the command-line UI. ## Installation issues @@ -139,7 +139,7 @@ If there are no Win32 paths in your $PATH, interop isn't going to find the .exe. You can verify it by running `echo $PATH` in Linux. It's expected that you will see a Win32 path (for example, /mnt/c/Windows) in the output. If you can't see any Windows paths then most likely your PATH is being overwritten by your Linux shell. -Here is a an example that /etc/profile on Debian contributed to the problem: +Here is an example that /etc/profile on Debian contributed to the problem: ```Bash if [ "`id -u`" -eq 0 ]; then diff --git a/WSL/tutorials/wsl-database.md b/WSL/tutorials/wsl-database.md index f3ac2fb0..7c3984da 100644 --- a/WSL/tutorials/wsl-database.md +++ b/WSL/tutorials/wsl-database.md @@ -35,7 +35,7 @@ Some [popular choices](https://insights.stackoverflow.com/survey/2021#section-mo **MongoDB** is an open-source NoSQL document database designed to work with JSON and store schema-free data. It is horizontally scalable, which means multiple smaller machines will do the work for you. It's good for flexibility and unstructured data, and caching real-time analytics. -**Redis** is is an open-source NoSQL in-memory data structure store. It uses key-value pairs for storage instead of documents. +**Redis** is an open-source NoSQL in-memory data structure store. It uses key-value pairs for storage instead of documents. ## Install MySQL @@ -54,7 +54,7 @@ Example using the Ubuntu distribution: For more about working with MySQL databases, see the [MySQL docs](https://dev.mysql.com/doc/mysql-getting-started/en/). -To work with with MySQL databases in VS Code, try the [MySQL extension](https://marketplace.visualstudio.com/items?itemName=cweijan.vscode-mysql-client2). +To work with MySQL databases in VS Code, try the [MySQL extension](https://marketplace.visualstudio.com/items?itemName=cweijan.vscode-mysql-client2). You may also want to run the included security script. This changes some of the less secure default options for things like remote root logins and sample users. This script also includes steps to change password for MySQL root user. To run the security script: diff --git a/WSL/wsl-config.md b/WSL/wsl-config.md index 6885a374..03f5264c 100644 --- a/WSL/wsl-config.md +++ b/WSL/wsl-config.md @@ -28,7 +28,7 @@ You must wait until the subsystem running your Linux distribution completely sto If you launch a distribution (e.g. Ubuntu), modify the configuration file, close the distribution, and then re-launch it, you might assume that your configuration changes have immediately gone into effect. This is not currently the case as the subsystem could still be running. You must wait for the subsystem to stop before relaunching in order to give enough time for your changes to be picked up. You can check to see whether your Linux distribution (shell) is still running after closing it by using PowerShell with the command: `wsl --list --running`. If no distributions are running, you will receive the response: "There are no running distributions." You can now restart the distribution to see your configuration updates applied. -The command `wsl --shutdown` is a fast path to restarting WSL 2 distributions, but it will shut down all running distributions, so use wisely. You can also use `wsl --terminate ` to terminate a a specific distribution that's running instantly. +The command `wsl --shutdown` is a fast path to restarting WSL 2 distributions, but it will shut down all running distributions, so use wisely. You can also use `wsl --terminate ` to terminate a specific distribution that's running instantly. ## wsl.conf diff --git a/WSL/wsl2-mount-disk.md b/WSL/wsl2-mount-disk.md index 5cea9c12..08fde4f5 100644 --- a/WSL/wsl2-mount-disk.md +++ b/WSL/wsl2-mount-disk.md @@ -23,7 +23,7 @@ You will need to be on Windows 11 Build 22000 or later, or be running the Micros External drives formatted for Windows typically use the NTFS file system formatting. External drives formatted for Linux typically use the Ext4 file system formatting. -If you have mounted a NTFS-formatted drive on your Windows file system, you can access that drive from your Linux distribution using WSL by creating a mounted directory (`sudo mkdir /mnt/d`, replacing 'd' with whatever drive letter you'd like to use) and then using the `drvfs` file system interop plugin, with the command: +If you have mounted an NTFS-formatted drive on your Windows file system, you can access that drive from your Linux distribution using WSL by creating a mounted directory (`sudo mkdir /mnt/d`, replacing 'd' with whatever drive letter you'd like to use) and then using the `drvfs` file system interop plugin, with the command: ```bash sudo mount -t drvfs D: /mnt/d @@ -212,7 +212,7 @@ This will make the block device available inside WSL 2 so it can be mounted manu > [!NOTE] > This option is only available with [WSL from the Microsoft Store](https://devblogs.microsoft.com/commandline/a-preview-of-wsl-in-the-microsoft-store-is-now-available/) -By default the mountpoint name is generated based on the physical disk or VHD name. This can be overriden with `--name`. Example: +By default the mountpoint name is generated based on the physical disk or VHD name. This can be overridden with `--name`. Example: ```powershell wsl --mount --name myDisk