Format fixes, typo

Author: Chuxel

docs/remote/containers.md

@@ -599,7 +599,7 @@ See the following examples dev containers for additional information:
 * Alpine Linux or Windows container images are not yet supported. Most images come with a Debian or Ubuntu based flavor you can use instead. (Typically Alpine variations end in `-alpine`).
 * All roots/folders in a multi-root workspace will be opened in the same container, regardless of whether there are configuration files at lower levels.
 * The unofficial Ubuntu Docker **snap** package for Linux is **not** supported. Follow the [official Docker install instructions for your distribution](https://docs.docker.com/install/#supported-platforms).
-* When installing an extension pack in a container, extensions may install locally instead of inside the container. Click the **Install** button for each extension in the Local section of the extension panel to work around the issue. See [vscode-remote-release #11](https://github.com/Microsoft/vscode-remote-release/issues/11) for details.
+* When installing an extension pack in a container, extensions may install locally instead of inside the container. Click the **Install** button for each extension in the Local section of the extension panel to work around the issue. See [Microsoft/vscode-remote-release#11](https://github.com/Microsoft/vscode-remote-release/issues/11) for details.
 * If you clone a Git repository using SSH and your SSH key has a passphrase, VS Code's pull and sync features may hang when running remotely. Either use a SSH key without a passphrase, clone using HTTPS, or run `git push` from the command line to work around the issue.
 * Local proxy settings are not reused inside the container, which can prevent extensions from working unless the appropriate proxy information is configured (for example global `HTTP_PROXY` or `HTTPS_PROXY` environment variables with the appropriate proxy information).
 

docs/remote/ssh.md

@@ -169,7 +169,7 @@ VS Code's local user settings are also reused when you are connected to an SSH h
 - Linux hosts must have Bash (`/bin/bash`), `tar`, and either `curl` or `wget` installed.
 - PuTTY is not supported on Windows.
 - You cannot drag files out of the File Explorer to your local filesystem to copy them.
-- When installing an extension pack when connected to a SSH host, extensions may install locally instead of inside on the host. Click the **Install** button for each extension in the Local section of the extension panel to work around the issue. See [vscode-remote-release #11](https://github.com/Microsoft/vscode-remote-release/issues/11) for details.
+- When installing an extension pack when connected to a SSH host, extensions may install locally instead of inside on the host. Click the **Install** button for each extension in the Local section of the extension panel to work around the issue. See [Microsoft/vscode-remote-release#11](https://github.com/Microsoft/vscode-remote-release/issues/11) for details.
 - If you clone a Git repository using SSH and your SSH key has a passphrase, VS Code's pull and sync features may hang when running remotely. Either use a SSH key without a passphrase, clone using HTTPS, or run `git push` from the command line to work around the issue.
 - Local proxy settings are not reused on the remote host, which can prevent extensions from working unless the appropriate proxy information is configured on the remote host (for example global `HTTP_PROXY` or `HTTPS_PROXY` environment variables with the appropriate proxy information).
 - See [here for a list of active issues](https://aka.ms/vscode-remote/ssh/issues) related to SSH.
@@ -186,7 +186,7 @@ The Docker extension is configured to run as a local "UI" extension by default.
 
 ### Extension limitations
 
-Many extensions will work on remote SSH hosts modification. However, in some cases, certain features may require changes. If you run into an extension issue, there is [a summary of common problems and solutions](/docs/remote/troubleshooting.md#extension-tips) that you can mention to the extension author when reporting the issue.
+Many extensions will work on remote SSH hosts without modification. However, in some cases, certain features may require changes. If you run into an extension issue, there is [a summary of common problems and solutions](/docs/remote/troubleshooting.md#extension-tips) that you can mention to the extension author when reporting the issue.
 
 ## Common questions
 

docs/remote/wsl.md

@@ -114,24 +114,24 @@ See [here for a list of active issues](https://aka.ms/vscode-remote/wsl/issues)
 
 | Issue | Existing issues |
 |---|---|
-Non-empty folders in the open workspace can't be renamed | https://github.com/Microsoft/WSL/issues/3395, https://github.com/Microsoft/WSL/issues/1956
-| When installing an extension pack in WSL, extensions may install locally instead of in WSL. Click the **Install** button for each extension in the Local section of the extension panel to work around the issue. | [vscode-remote-release #11](https://github.com/Microsoft/vscode-remote-release/issues/11) |
+Non-empty folders in the open workspace can't be renamed | [Microsoft/WSL#3395](https://github.com/Microsoft/WSL/issues/3395), [Microsoft/WSL#1956](https://github.com/Microsoft/WSL/issues/1956)
+| When installing an extension pack in WSL, extensions may install locally instead of in WSL. Click the **Install** button for each extension in the Local section of the extension panel to work around the issue. | [Microsoft/vscode-remote-release#11](https://github.com/Microsoft/vscode-remote-release/issues/11) |
 
 In addition, local proxy settings are not reused by VS Code running in WSL, which can prevent extensions from working without adding a global `HTTP_PROXY` and `HTTPS_PROXY` environment variable with the appropriate proxy information.
 
 ### Golang in WSL
 
 | Issue | Existing issues |
 |---|---|
-Delve debugger doesn't work under WSL | https://github.com/go-delve/delve/issues/810 https://github.com/Microsoft/vscode-go/issues/926 |
+Delve debugger doesn't work under WSL | [go-delve/delve#810](https://github.com/go-delve/delve/issues/810),  [Microsoft/vscode-go#926](https://github.com/Microsoft/vscode-go/issues/926) |
 
 ### Node.js in WSL
 
 | Issue | Existing issues |
 |---|---|
-NodeJS Error: spawn EACCES (different variants of this error) | https://github.com/Microsoft/WSL/issues/3886 |
-Webpack HMR not working | https://github.com/Microsoft/WSL/issues/2709 |
-Firebase via node unusably slow only on WSL | https://github.com/Microsoft/WSL/issues/2657 |
+NodeJS Error: spawn EACCES (different variants of this error) | [Microsoft/WSL#3886](https://github.com/Microsoft/WSL/issues/3886) |
+Webpack HMR not working | [Microsoft/WSL#2709](https://github.com/Microsoft/WSL/issues/2709) |
+Firebase via node unusably slow only on WSL | [Microsoft/WSL#2657](https://github.com/Microsoft/WSL/issues/2657) |
 
 ### Git limitations