Fix broken image links

docs/containers/app-service.md

@@ -84,7 +84,7 @@ In the previous section, the image is pushed to a remote container registry. Now
 
     ![Deployment complete output](images/app-service/output-appservice-deployment.png)
 
-5. To browse the deployed website, you can use Ctrl+Click to open the URL in the Output panel. The new App Service also appears in the Azure view in Visual Studio Code under the App Service section, where you can right-click the website and select Browse Website.
+5. To browse the deployed website, you can use `kbstyle(Ctrl+click)` to open the URL in the Output panel. The new App Service also appears in the Azure view in Visual Studio Code under the App Service section, where you can right-click the website and select Browse Website.
 
     ![Web Application](images/app-service/webapp-homepage.png)
 

docs/containers/choosing-dev-environment.md

@@ -11,7 +11,7 @@ MetaDescription: Guidance on choosing remote or local environments for developin
 
 You can choose whether to develop a container-based service in the **local environment**, or in a **remote environment**. The local environment is the operating system of your developer workstation; using the local environment means you build and run your service container(s) using Docker installed on your workstation.
 
-[A remote development environment](https://code.visualstudio.com/docs/remote/remote-overview) is different from your developer workstation. It can be a remote machine accessible via SSH, a virtual machine running on your developer workstation, or a development container. A remote environment can have advantages over the local environment, the main one being **the ability to use the same operating system during development, and when your service is running in production**. To use a remote environment, you need to ensure that `docker` command (Docker CLI) [is available and functional within that environment](#enabling-docker-cli-inside-a-development-environment).
+[A remote development environment](/docs/remote/remote-overview.md) is different from your developer workstation. It can be a remote machine accessible via SSH, a virtual machine running on your developer workstation, or a development container. A remote environment can have advantages over the local environment, the main one being **the ability to use the same operating system during development, and when your service is running in production**. To use a remote environment, you need to ensure that `docker` command (Docker CLI) [is available and functional within that environment](#enabling-docker-cli-inside-a-development-environment).
 
 The second important choice is whether to debug your service running as a ordinary process, or **debug your service running in a container**.
 
@@ -21,7 +21,7 @@ The second important choice is whether to debug your service running as a ordina
    - using the same OS for development and inside the service container, nor
    - installing necessary tools and dependencies on top of your local environment.
 
-1. Consider [development container](https://code.visualstudio.com/docs/remote/containers) first if you need a remote environment.
+1. Consider [development container](/docs/remote/containers.md) first if you need a remote environment.
     - On Windows, [Windows Subsystem for Linux (WSL)](#windows-subsystem-for-linux) is worth considering as an alternative.
 
 1. Debugging your service running in a container is possible, but brings additional complexity. Use normal debugging by default, and debugging in container when you need it.

docs/containers/debug-common.md

@@ -94,7 +94,7 @@ More information about debugging Node.js applications within Docker containers c
 
 ### `node` Object Properties
 
-> These properties are the same as those described in the [VS Code documentation](https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_launch-configuration-attributes) for attaching a debugger to Node.js applications. All properties passed in the `node` object will be passed on to the Node.js debug adaptor, even if not specifically listed below.
+> These properties are the same as those described in the [VS Code documentation](/docs/nodejs/nodejs-debugging.md#launch-configuration-attributes) for attaching a debugger to Node.js applications. All properties passed in the `node` object will be passed on to the Node.js debug adaptor, even if not specifically listed below.
 
 | Property | Description | Default |
 | --- | --- | --- |

docs/containers/overview.md

@@ -33,7 +33,7 @@ In addition, you can use the Problems panel to view common errors for `Dockerfil
 
 ## Generating Docker files
 
-You can add Docker files to your workspace by opening the Command Palette (`kb(workbench.action.showCommands)` key) and using `Docker: Add Docker Files to Workspace` command. The command will generate `Dockerfile` and `.dockerignore` files and add them to your workspace. The command will also query you if you want the Docker Compose files added as well; this is optional.
+You can add Docker files to your workspace by opening the Command Palette (`kb(workbench.action.showCommands)` key) and using **Docker: Add Docker Files to Workspace** command. The command will generate `Dockerfile` and `.dockerignore` files and add them to your workspace. The command will also query you if you want the Docker Compose files added as well; this is optional.
 
 The extension recognizes workspaces that use most popular development languages (C#, Node.js, Python, Ruby, Go and Java) and customizes generated Docker files accordingly.
 
@@ -55,7 +55,7 @@ Many of the most common Docker commands are built right into the Command Palette
 
 ![Docker commands](images/overview/command-palette.png)
 
-You can run Docker commands to manage [images](https://docs.docker.com/engine/reference/commandline/image/), [networks](https://docs.docker.com/engine/reference/commandline/network/), [volumes](https://docs.docker.com/engine/reference/commandline/volume/), [image registries](https://docs.docker.com/engine/reference/commandline/push/) and [Docker Compose](https://docs.docker.com/compose/reference/overview/). In addition, the `Docker: Prune System` command will remove stopped containers, dangling images, and unused networks and volumes.
+You can run Docker commands to manage [images](https://docs.docker.com/engine/reference/commandline/image/), [networks](https://docs.docker.com/engine/reference/commandline/network/), [volumes](https://docs.docker.com/engine/reference/commandline/volume/), [image registries](https://docs.docker.com/engine/reference/commandline/push/) and [Docker Compose](https://docs.docker.com/compose/reference/overview/). In addition, the **Docker: Prune System** command will remove stopped containers, dangling images, and unused networks and volumes.
 
 ## Using image registries
 
@@ -83,15 +83,15 @@ Visual Studio Code's experience for authoring `docker-compose.yml` is also very
 2. Define a new service called `web:`
 3. On the second line, bring up IntelliSense by pressing `kb(editor.action.triggerSuggest)` to see a list of all valid compose directives.
 
- ![Docker Compose IntelliSense](images/docker/dockercomposeintellisense.png)
+ ![Docker Compose IntelliSense](images/overview/dockercomposeintellisense.png)
 
 4. For the `image` directive, you can press `kb(editor.action.triggerSuggest)` again and VS Code will query the Docker Hub index for public images.
 
- ![Docker Compose image suggestions](images/docker/dockercomposeimageintellisense.png)
+ ![Docker Compose image suggestions](images/overview/dockercomposeimageintellisense.png)
 
 VS Code will first show a list of popular images along with metadata such as the number of stars and description. If you continue typing, VS Code will query the Docker Hub index for matching images, including searching public profiles. For example, searching for `Microsoft` will show you all the public Microsoft images.
 
- ![Docker Compose Microsoft image suggestions](images/docker/dockercomposesearch.png)
+ ![Docker Compose Microsoft image suggestions](images/overview/dockercomposesearch.png)
 
 ## Next steps
 

docs/containers/quickstart-aspnet-core.md

@@ -33,7 +33,7 @@ In this guide you will learn how to:
 ## Add Docker files to the project
 
 1. Open the project folder in VS Code
-1. Open Command Palette (`kb(workbench.action.showCommands)`) and use `Docker: Add Docker Files to Workspace...` command:
+1. Open Command Palette (`kb(workbench.action.showCommands)`) and use **Docker: Add Docker Files to Workspace...** command:
 
    ![Add Dockerfile to a .NET project](images/quickstarts/aspnetcore-add-dotnet.png)
 

docs/containers/quickstart-node.md

@@ -33,7 +33,7 @@ In this guide you will learn how to:
 ## Add Docker file to the project
 
 1. Open the project folder in VS Code.
-1. Open the Command Palette (`kb(workbench.action.showCommands)`) and use `Docker: Add Docker Files to Workspace...` command:
+1. Open the Command Palette (`kb(workbench.action.showCommands)`) and use **Docker: Add Docker Files to Workspace...** command:
 
    ![Add Dockerfile to a Node.js project](images/quickstarts/node-add-node.png)
 
@@ -60,7 +60,7 @@ The extension will create `Dockerfile` and `.dockerignore` files. If you elected
 
    ![Application page in browser](images/quickstarts/node-run-browser.png)
 
-1. When done testing, type `Ctrl+C` in the terminal.
+1. When done testing, type `kbstyle(Ctrl+C)` in the terminal.
 
 ## Build the service image