use markdown image links

remote-release-notes/v1_44.md

@@ -14,17 +14,17 @@ These containers use isolated, local [Docker volumes](https://docs.docker.com/st
 - the **Remote-Containers: Open Repository in Container** command and entering the corresponding Pull Request, e.g. `https://github.com/microsoft/vscode-npm-scripts/pull/111`
 - in the [GitHub Pull Request Extension](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) you can select the PR and use the command **Checkout Pull Request in Dev Container**.
 
-<img src="images/1_44/checkout-pr.png" alt="Checkout Pull Request" style="width:400px;"/>
+![Checkout Pull Request](images/1_44/checkout-pr.png)
 
 When opening a Pull Request into a dev container then the GitHub Pull Request extension is automatically installed into the container and the Pull Request is checked out, ready for you to review. You can switch to the PR description from the status line:
 
-<img src="images/1_44/checkout-pr-status.png" alt="Checkout Pull Request Status Bar" style="width:600px;"/>
+![Checkout Pull Request Status Bar](images/1_44/checkout-pr-status.png)
 
 When the repository does not yet contain a dev container configuration you will be prompted to select one and it will be added.
 
 There is support to quickly create a unique volume for a PR review. You will be prompted to remove the unique volume when removing the container from the Remote Explorer.
 
-<img src="images/1_44/checkout-unique.png" alt="Use a Unique Volume" style="width:600px;"/>
+![Use a Unique Volume](images/1_44/checkout-unique.png)
 
 In addition to entering the GitHub URLs for Pull Requests you can also enter the URLs for branches and commits. In this case the corresponding branch or commit will be checked out when creating the container.