Merge branch 'master' of github.com:johnsta/visualstudio-docs-pr into johnsta

Author: ghogen

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-03.md

@@ -19,7 +19,7 @@ If you have [.NET Core](https://www.microsoft.com/net) installed, you can quickl
 dotnet new mvc --name webfrontend
 ```
 
-Alternatively, **download sample code from GitHub** by navigating to https://github.com/johnsta/vsce-samples and select **Clone or Download** to download the GitHub repository to your local environment. The code for this guide is in `vsce-samples/dotnetcore/getting-started/webfrontend`.
+Alternatively, **download sample code from GitHub** by navigating to https://github.com/Azure/vsce and select **Clone or Download** to download the GitHub repository to your local environment. The code for this guide is in `vsce/samples/dotnetcore/getting-started/webfrontend`.
 
 [!INCLUDE[](common/vsce-init.md)]
 

connected-environment/get-started-netcore-05.md

@@ -18,7 +18,7 @@ In this section we're going to create a second service, `mywebapi`, and have `we
 ![](media/multi-container.png)
 
 ## Download sample code for *mywebapi*
-For the sake of time, let's download sample code from a GitHub repository. Go to https://github.com/johnsta/vsce-samples and select **Clone or Download** to download the GitHub repository. The code for this section is in `vsce-samples/dotnetcore/getting-started/mywebapi`.
+For the sake of time, let's download sample code from a GitHub repository. Go to https://github.com/Azure/vsce and select **Clone or Download** to download the GitHub repository. The code for this section is in `vsce/samples/dotnetcore/getting-started/mywebapi`.
 
 
 ## Run *mywebapi*

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

@@ -40,7 +40,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/get-started-netcore-visualstudio-05.md

@@ -19,7 +19,7 @@ In this section we're going to create a second service, `mywebapi`, and have `we
 ![](media/multi-container.png)
 
 ## Download sample code for *mywebapi*
-For the sake of time, let's download sample code from a GitHub repository. Go to https://github.com/johnsta/vsce-samples and select **Clone or Download** to download the GitHub repository. The code for this section is in `vsce-samples/dotnetcore/getting-started/mywebapi`.
+For the sake of time, let's download sample code from a GitHub repository. Go to https://github.com/Azure/vsce and select **Clone or Download** to download the GitHub repository. The code for this section is in `vsce/samples/dotnetcore/getting-started/mywebapi`.
 
 ## Run *mywebapi*
 1. Open the project `mywebapi` in a *separate Visual Studio window*.

connected-environment/get-started-nodejs-03.md

@@ -14,7 +14,7 @@ manager: "ghogen"
 Previous step: [Create a Kubernetes development environment in Azure](get-started-nodejs-02.md)
 
 ## Create a Node.js Web App
-Download code from GitHub by navigating to https://github.com/johnsta/vsce-samples and select **Clone or Download** to download the GitHub repository to your local environment. The code for this guide is in `vsce-samples/nodejs/getting-started/webfrontend`.
+Download code from GitHub by navigating to https://github.com/Azure/vsce and select **Clone or Download** to download the GitHub repository to your local environment. The code for this guide is in `vsce/samples/nodejs/getting-started/webfrontend`.
 
 [!INCLUDE[](common/vsce-init.md)]
 
@@ -41,13 +41,13 @@ If you open the web app on a mobile device, you will notice that the UI does not
 
 To fix this, we'll add a `viewport` meta tag:
 1. Open the file `./public/index.html`
-1. Add a `viewport` meta tag in the existing `header` tag:
+1. Add a `viewport` meta tag in the existing `head` element:
 
 ```html
-<header>
+<head>
     <!-- Add this line -->
     <meta name="viewport" content="width=device-width, initial-scale=1">
-</header>
+</head>
 ```
 
 1. Save the file.

connected-environment/get-started-nodejs-05.md

@@ -18,7 +18,7 @@ In this section we're going to create a second service, `mywebapi`, and have `we
 ![](media/multi-container.png)
 
 ## Open sample code for *mywebapi*
-You should already have the sample code for `mywebapi` for this guide under a folder named `vsce-samples` (if not, go to https://github.com/johnsta/vsce-samples and select **Clone or Download** to download the GitHub repository.) The code for this section is in `vsce-samples/nodejs/getting-started/mywebapi`.
+You should already have the sample code for `mywebapi` for this guide under a folder named `vsce/samples` (if not, go to https://github.com/Azure/vsce and select **Clone or Download** to download the GitHub repository.) The code for this section is in `vsce/samples/nodejs/getting-started/mywebapi`.
 
 ## Run *mywebapi*
 1. Open the folder `mywebapi` in a *separate VS Code window*.

connected-environment/how-to/share-dev-environment.md

@@ -3,7 +3,7 @@
 With Connected Environment, you can share your development environment with others on your team. Each developer can work in their own space without fear of breaking others. Also, working together in one environment can enable you to test code end-to-end without having to create mocks or simulate dependencies. See the [Learn about team development](../get-started-nodejs-06.md) guide for more information.
 
 To set up an environment for multiple developers:
-1. [Create a Connected Environment in Azure](../get-started.md). You'll need to have Owner or Contributor access to an Azure subscription.
+1. [Create a Connected Environment in Azure](../get-started.md). You'll need to have Owner or Contributor access to the selected Azure subscription.
 1. Configure the environment's **resource group** to [grant Contributor access](https://docs.microsoft.com/en-us/azure/active-directory/role-based-access-control-configure) for each team member. You can check an environment's resource group by running this command: `vsce env list`
 1. Ask team members to **select the environment** in order to develop in it.
      * **Command line or VS Code**: To see existing Connected Environments you have access to: `vsce env list`. To select an environment: `vsce env select`.

connected-environment/how-to/use-kubectl-with-vsce.md

@@ -0,0 +1,11 @@
+# Use `kubectl` with a Connected Environment
+
+You can access the Kubernetes cluster within a Connected Environment, and use existing Kubernetes tools like `kubectl`.
+
+Running `vsce env create` or `vsce env select` will automatically add a `kubectl` configuration context for you, so kubectl should already be connected to your VSCE Kubernetes cluster. Examples:
+- Confirm the current context: `kubectl config current-context`
+- List all available contexts: `kubectl config get-contexts`. A kubernetes cluster created by VSCE will be named something like "vsce-<guid>".
+- Change context: `kubectl config use-context <context-name>`
+- View the Kubernetes dashboard: run `kubectl proxy`, then open your browser to the address that this command emits (append `/ui` to the URL to navigate to the Kubernetes dashboard).
+- List the running services in the default VSCE space named *mainline*: `kubectl get services --namespace=mainline`
+

connected-environment/troubleshooting.md

@@ -22,7 +22,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 () {...}`