remote release notes edit pass

release-notes/v1_50.md

@@ -383,7 +383,7 @@ We've updated the documentation to help you [create a development container](htt
 
 ## Extensions
 
-We're excited to share the work of our partner teams, whose extensions help make VS Code even better.
+Our partner teams at Microsoft release extensions that help make VS Code even better.
 
 ### Microsoft C++ extension
 

remote-release-notes/v1_50.md

@@ -10,34 +10,31 @@ Detecting ports for automatic forwarding was added in 1.49, but now there is a n
 
 It is now possible to install/enable extensions when VS Code is connected to a remote. If an extension is not executing (i.e. its code is not executing), it can also be uninstalled/disabled without reloading VS Code.
 
-## SSH
-
-
 ## Containers
 
-### Improved Log Access and Rendering
+### Improved log access and rendering
 
-When you open a folder locally after opening it in a container failed, the new command `Remote-Containers: Show Previous Log` opens the log from the failed attempt to open in a container.
+When you open a folder locally after attempting to open it in a container failed, the new command **Remote-Containers: Show Previous Log** opens the log from the failed attempt to open in a container.
 
-The command `Remote-Containers Developer: Show All Logs...` now shows one file per startup (instead of one file per VS Code session potentially spanning several startups) making it easier to navigate:
+The command **Remote-Containers Developer: Show All Logs...** now shows one file per startup (instead of one file per VS Code session, potentially spanning several startups) making it easier to navigate:
 
 ![Remote-Containers Developer: Show All Logs...](images/1_50/containers-show-all-logs.png)
 
-The current log shown in the DevContainer terminal with the `Remote-Containers: Show Log` command now comes with coloring:
+The current log shown in the DevContainer terminal with the **Remote-Containers: Show Log** command now comes with coloring:
 
 ![Log Coloring](images/1_50/containers-log-coloring.png)
 
-### DevContainer Development Actions in Remote-Explorer
+### DevContainer development actions in Remote-Explorer
 
 The Remote-Explorer viewlet's Details section now comes with the `Open Container Configuration File` and `Rebuild Container` actions which previously were only available in the command palette:
 
 ![Details Section](images/1_50/containers-details-section.png)
 
-### Clone Repository in Container Volume: better recovery support
+### Clone repository in container volume: better recovery support
 
-When opening a repository in a container volume using `Clone Repository in Container Volume` fails, then we now show the creation log of the container together with the `devcontainer.json` in the recovery container. This is now the same experience as when `Open Folder in Container` fails.
+When opening a repository in a container volume using `Clone Repository in Container Volume` fails, we now show the creation log of the container together with the `devcontainer.json` in the recovery container. This is now the same experience as when `Open Folder in Container` fails.
 
-### Notable Fixes
+### Notable fixes
 
 - [3648](https://github.com/microsoft/vscode-remote-release/issues/3648): `Pass "remoteEnv" variables to "postCreate/Start/AttachCommand"s and dotfiles script.`