Links to Helm documentation

Author: John Stallo

connected-environment/common/vsce-init.md

@@ -11,7 +11,7 @@ vsce init --public
 
 The Connected Environment CLI's ```init``` command generates Docker and Kubernetes assets with default settings:
 * `./Dockerfile` describes the app's container image, and how the source code is built and runs within the container.
-* A **Helm chart** under `./charts/webfrontend` describes how to deploy the container to Kubernetes.
+* A [Helm chart](https://docs.helm.sh) under `./charts/webfrontend` describes how to deploy the container to Kubernetes.
 
 For now it isn't necessary to understand the full content of these files. It's worth pointing out, however, that **the same Kubernetes and Docker configuration-as-code assets can be used from development through to production, thus providing better consistency across different environments.**
 

connected-environment/get-started-netcore-visualstudio-03.md

@@ -29,7 +29,7 @@ Until the development environment is successfully created you cannot debug your
 ## Look at the files added to project
 While we wait for the development environment to be created, let’s look at the files that have been added to your project when you chose to use a development environment.
 
-First, you can see a folder named `charts` has been added and within this a Helm chart for your application has been scaffolded. These files are used to deploy your application into the development environment.
+First, you can see a folder named `charts` has been added and within this a [Helm chart](https://docs.helm.sh) for your application has been scaffolded. These files are used to deploy your application into the development environment.
 
 You will see a file named `Dockerfile` has been added. This file has information needed to package your application in the standard Docker format. A `HeaderPropagation.cs` file is also created, we will discuss this file later in the walkthrough. 
 

connected-environment/troubleshooting.md

@@ -11,7 +11,7 @@ You may see this error when trying to access your service. For example, when you
 1. If the container is in the process of being built/deployed, you can wait 2-3 seconds and try accessing the service again. 
 1. Check your port configuration. The specified port numbers should be **identical** in all the assets below:
     * **Dockerfile:** Specified by the `EXPOSE` instruction.
-    * **Helm Chart:** Specified by the `externalPort` and `internalPort` values for a service (often located in a `values.yml` file),
+    * **[Helm chart](https://docs.helm.sh):** Specified by the `externalPort` and `internalPort` values for a service (often located in a `values.yml` file),
     * Any ports being opened up in application code, for example in Node.js: `var server = app.listen(80, function () {...}`