Remote release notes edit pass

remote-release-notes/v1_53.md

@@ -4,7 +4,7 @@
 
 ### Extension management in the remote CLI
 
-The `code` command in integrated terminals of remote windows now supports
+The `code` command in the Integrated Terminal of remote windows now supports:
 
 - `code --install-extension idOrPathToVSIX` in combination with `--force`
 - `code --uninstall-extension idOrPathToVSIX` in combination with `--force`
@@ -22,11 +22,11 @@ This month, we improved this by adding the ability to restore the UI state of re
 
 ### Smart update of machine settings
 
-Machine scoped settings are written into remote settings file when updated through `vscode.workspace.getConfiguration().update()` API.
+Machine scoped settings are written into a remote settings file when updated through `vscode.workspace.getConfiguration().update()` API.
 
 ### Connection compression
 
-The communication between VS Code and the remote machine is now compressed, using a WebSocket extension called `permessage-deflate`. The compression helps a lot especially with weak network connections.
+The communication between VS Code and the remote machine is now compressed, using a WebSocket extension called `permessage-deflate`. The compression is especially helpful for weak network connections.
 
 Here is the data usage when opening a workbench and typing character-for-character the following in an empty TypeScript file:
 
@@ -45,11 +45,11 @@ window.addEventListener('load', function() {
 
 Previously, after a short duration of failing to communicate with the remote, a modal dialog would interrupt the user's coding session. We have increased this duration and opted for a subtler indication beforehand.
 
-![Brief Disconnect State](images/1_53/reconnecting.png)
+![Brief disconnect state](images/1_53/reconnecting.png)
 
 ### Port attributes
 
-Attributes can now be configured for ports in settings. These attributes let you control the label that shows in the Ports view, the action that occurs when the port is auto-forwarded, and whether that that port should always prompt for elevation if the local port is privileged (currently no Remote extension support this last one).
+Attributes can now be configured for ports in settings. These attributes let you control the label that shows in the Ports view, the action that occurs when the port is auto-forwarded, and whether that that port should always prompt for elevation if the local port is privileged (currently no Remote extensions support this last one).
 
 * The port number can be a number or a range (ex. `3000` or `30000-40000`).
 * `label`: A label for the port in the "Ports" view.
@@ -58,17 +58,17 @@ Attributes can now be configured for ports in settings. These attributes let you
   * `silent`: The port will be auto-forwarded, but no notification will be shown
   * `openBrowser`: Immediately opens the browser when the port is auto-forwarded
   * `ignore`: The port will not be auto-forwarded
-* `elevateIfNeeded`: If the remote extension you are using supports elevating for privileged ports (i.e., ports below 1024 on Linux or MacOS), then setting this to `true` will cause the elevation prompt to immediately show when a local privileged port is used for forwarding. **Note:** At the time of this release, no remote extensions support elevating for privileged ports.
+* `elevateIfNeeded`: If the remote extension you are using supports elevating for privileged ports (for example, ports below 1024 on Linux or macOS), then setting this to `true` will cause the elevation prompt to immediately show when a local privileged port is used for forwarding. **Note:** At the time of this release, remote extensions do not support elevating for privileged ports.
 
 ![Setting port attributes](images/1_53/ports-attributes.gif)
 
 ### Privileged port forwarding
 
-On Linux and MacOS, privileged ports (ports < 1024) could not be detected previously. Now, privileged ports will be detected if a url (ex. http://localhost:80) is printed to the debug console or terminal output and will be auto forwarded.
+Previously, privileged ports (ports < 1024) could not be detected on Linux and macOS. Now, privileged ports will be detected if a url (ex. http://localhost:80) is printed to the Debug Console or Terminal Output and will be auto forwarded.
 
 ### More port details
 
-The process ID of the process associated with the forwarded port is now shown in the Ports view. You can also see additional details about the forwarded port's CLI when the Ports view is wide.
+The process ID of the process associated with the forwarded port is now shown in the Ports view. You can also see more details about the forwarded port's CLI when the Ports view is wide.
 
 ![Ports view with more info](images/1_53/ports-view-more-info.png)
 
@@ -80,7 +80,7 @@ The hover text for links in the terminal now hints that the port is forwarded wh
 
 ## Containers (version 0.158.x)
 
-### Support SSH connection with password entry
+### Support for SSH connection with password entry
 
 If you connect to Docker using SSH, we now support prompting for a password (and passphrase) when required.
 
@@ -89,10 +89,10 @@ If you connect to Docker using SSH, we now support prompting for a password (and
 ### Install extensions from a WSL shell
 
 The `code` CLI in the WSL shell now also supports
-`--list-extensions`, `--uninstall-extension` and `--uninstall-extension`. You can use them to list, remove or add extensions installed on the WSL side. This works for extensions from the Marketplace as well as from VSIXes.
+`--list-extensions`, `--uninstall-extension`, and `--uninstall-extension`. You can use them to list, remove, or add extensions installed on the WSL side. This works for extensions from the Marketplace and from VSIXes.
 
-Again, the command is restricted to extensions on the WSL side. To install an extension locally, use `code.cmd` from the Windows side or the extensions view.
+Again, the command is restricted to extensions on the WSL side. To install an extension locally, use `code.cmd` from the Windows side or the Extensions view.
 
 ### Shortcuts to install WSL and WSL distros
 
-The Remote - WSL extension now guides users how to install WSL and WSL distros when not yet present. It uses the new simplified [`wsl --install`](https://docs.microsoft.com/en-us/windows/wsl/install-win10#simplified-installation-for-windows-insiders) feature available in Windows Preview builds.
+The [Remote - WSL extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-wsl) now guides users how to install WSL and WSL distros when not yet present. It uses the new simplified [`wsl --install`](https://docs.microsoft.com/en-us/windows/wsl/install-win10#simplified-installation-for-windows-insiders) feature available in Windows Preview builds.