Merge pull request #57913 from sethmanheim/wk11-13

Freshness reviews and updates

Author: Ja-Dunn

articles/azure-stack/user/azure-stack-create-vm-template.md

@@ -1,6 +1,6 @@
 ---
 title: In this tutorial, you create an Azure Stack VM using a template | Microsoft Docs
-description: Describes how to use the ASDK to create a VM using a predfined template and a GitHub custom template.
+description: Describes how to use the ASDK to create a VM using a predefined template and a GitHub custom template.
 services: azure-stack
 documentationcenter: ''
 author: sethmanheim
@@ -14,41 +14,41 @@ pms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: tutorial
 ms.custom: mvc
-ms.date: 09/12/2018
+ms.date: 11/13/2018
 ms.author: sethm
 ms.reviewer: 
 ---
 
 # Tutorial: create a VM using a community template
+
 As an Azure Stack operator or user, you can create a VM using [custom GitHub quickstart templates](https://github.com/Azure/AzureStack-QuickStart-Templates) rather than deploying one manually from the Azure Stack marketplace.
 
 In this tutorial, you learn how to:
 
 > [!div class="checklist"]
-> * Learn about Azure Stack quickstart templates 
+> * Use Azure Stack quickstart templates 
 > * Create a VM using a custom GitHub template
 > * Start minikube and install an application
 
-## Learn about Azure Stack quickstart templates
-Azure Stack quickstart templates are stored in the [public AzureStack QuickStart Templates repository](https://github.com/Azure/AzureStack-QuickStart-Templates) on GitHub. This repository contains Azure Resource Manager deployment templates that have been tested with the Microsoft Azure Stack Development Kit (ASDK). You can use them to make it easier for you to evaluate Azure Stack and use the ASDK environment. 
+## Azure Stack quickstart templates
 
-Over time many GitHub users have contributed to the repository, resulting in a huge collection of more than 400 deployment templates. This repository is a great starting point to get a better understanding of how you can deploy various kinds of environments to Azure Stack. 
-
->[!IMPORTANT]
-> Some of these templates are created by members of the community and not by Microsoft. Each template is licensed under a license agreement by its owner, not Microsoft. Microsoft is not responsible for these templates and does not screen for security, compatibility, or performance. Community templates are not supported under any Microsoft support program or service, and are made available "AS IS" without warranty of any kind.
+Azure Stack quickstart templates are stored in the [public Azure Stack QuickStart templates repository](https://github.com/Azure/AzureStack-QuickStart-Templates) on GitHub. This repository contains Azure Resource Manager deployment templates that have been tested with the Microsoft Azure Stack Development Kit (ASDK). You can use them to make it easier for you to evaluate Azure Stack and use the ASDK environment. 
 
-If you want to contribute your Azure Resource Manager templates to GitHub, you should make your contribution to the [azure-quickstart-templates repository](https://github.com/Azure/AzureStack-QuickStart-Templates).
+Over time many GitHub users have contributed to the repository, resulting in a collection of more than 400 deployment templates. This repository is a great starting point to get a better understanding of how you can deploy various kinds of environments to Azure Stack. 
 
-To learn more about the GitHub repository, and how to contribute to it, see the [readme file](https://github.com/Azure/AzureStack-QuickStart-Templates/blob/master/README.md). 
+>[!IMPORTANT]
+> Some of these templates are created by members of the community and not by Microsoft. Each template is licensed under a license agreement by its owner, not Microsoft. Microsoft is not responsible for these templates and does not screen for security, compatibility, or performance. Community templates are not supported under any Microsoft support program or service, and are made available "AS IS," without warranty of any kind.
 
+If you want to contribute your Azure Resource Manager templates to GitHub, make your contribution to the [AzureStack-QuickStart-Templates](https://github.com/Azure/AzureStack-QuickStart-Templates) repository. To learn more about this repository and how to contribute to it, see the [readme file](https://github.com/Azure/AzureStack-QuickStart-Templates/blob/master/README.md). 
 
 ## Create a VM using a custom GitHub template
+
 In this example tutorial, the [101-vm-linux-minikube](https://github.com/Azure/AzureStack-QuickStart-Templates/tree/master/101-vm-linux-minikube) Azure Stack quickstart template is used to deploy an Ubuntu 16.04 virtual machine on Azure Stack running Minikube to manage a Kubernetes cluster.
 
 Minikube is a tool that makes it easy to run Kubernetes locally. Minikube runs a single-node Kubernetes cluster inside a VM, enabling you to try out Kubernetes or develop with it day-to-day. It supports a simple, one-node Kubernetes cluster running on a Linux VM. Minikube is the fastest and most straightforward way to get a fully functional Kubernetes cluster running. It enables developers to develop and test their Kubernetes-based application deployments on their local machines. Architecturally, the Minikube VM runs both Master and Agent Node Components locally:
 
 - Master Node components such as API Server, Scheduler, and [etcd Server](https://coreos.com/etcd/) are run in a single Linux process called LocalKube.
-- Agent Node components are run inside docker containers exactly as they would run on a normal Agent Node. From an application deployment standpoint, there is no difference when the application is deployed on a Minikube or regular Kubernetes cluster.
+- Agent Node components are run inside docker containers exactly as they would run on a normal Agent Node. From an application deployment standpoint, there is no difference between when the application is deployed on a Minikube, or in a regular Kubernetes cluster.
 
 This template installs the following components:
 
@@ -60,33 +60,33 @@ This template installs the following components:
 - xRDP
 
 > [!IMPORTANT]
-> The Ubuntu VM image (Ubuntu Server 16.04 LTS in this example) must already have been added to the Azure Stack marketplace before beginning these steps.
+> The Ubuntu VM image (Ubuntu Server 16.04 LTS in this example) must already have been added to the Azure Stack marketplace before performing these steps.
 
-1.	Click **+ Create a resource** > **Custom** > **Template deployment**.
+1.	Select **+ Create a resource**, then **Custom**, then **Template deployment**.
 
     ![](media/azure-stack-create-vm-template/1.PNG) 
 
-2. Click **Edit template**.
+2. Select **Edit template**.
 
     ![](media/azure-stack-create-vm-template/2.PNG) 
 
-3.	Click **Quickstart template**.
+3.	Select **Quickstart template**.
 
     ![](media/azure-stack-create-vm-template/3.PNG)
 
 4. Select **101-vm-linux-minikube** from the available templates using the **Select a template** dropdown list, and then click **OK**.	
 
     ![](media/azure-stack-create-vm-template/4.PNG)
 
-5. If you want to make modifications to the template JSON you can do so, if not, or when complete, click **Save** to close the edit template dialog.
+5. If you want to make modifications to the template JSON you can do so. If not, or when complete, select **Save** to close the **Edit template** dialog.
 
     ![](media/azure-stack-create-vm-template/5.PNG) 
 
-6.	Click on **Parameters**, fill in or modify the available fields as necessary, and then click **OK**. Choose the subscription to use, create or choose an existing resource group name, and then click **Create** to initiate the template deployment.
+6.	Select **Parameters**, fill in or modify the available fields as necessary, and then click **OK**. Choose the subscription to use, create or choose an existing resource group name, and then select **Create** to initiate the template deployment.
 
     ![](media/azure-stack-create-vm-template/6.PNG)
 
-7. Choose the subscription to use, create or choose an existing resource group name, and then click **Create** to initiate the template deployment.
+7. Choose the subscription to use, create or choose an existing resource group name, and then select **Create** to initiate the template deployment.
 
     ![](media/azure-stack-create-vm-template/7.PNG)
 
@@ -97,18 +97,19 @@ This template installs the following components:
     >[!NOTE]
     > The VM will be running when the deployment completes. 
 
-## Start minikube and install an application
-Now that the Linux VM has been successfully created, you can sign in to start minikube and install an application. 
+## Start Minikube and install an application
+
+Now that the Linux VM has been successfully created, you can sign in to start Minikube and install an application. 
 
-1. After the deployment completes, click **Connect** to view the Public IP address that will be used to connect to the Linux VM. 
+1. After the deployment completes, select **Connect** to view the public IP address that will be used to connect to the Linux VM. 
 
     ![](media/azure-stack-create-vm-template/9.PNG)
 
-2. From an elevated command prompt, run **mstsc.exe** to open Remote Desktop Connection and connect to the Linux VM's public IP address discovered in the previous step. When prompted to sign in to xRDP, use the credentials you specified when creating the VM.
+2. From an elevated command prompt, run **mstsc.exe** to open Remote Desktop Connection and connect to the Linux VM public IP address discovered in the previous step. When prompted to sign in to xRDP, use the credentials you specified when creating the VM.
 
     ![](media/azure-stack-create-vm-template/10.PNG)
 
-3. Open Terminal Emulator and enter following commands to start minikube:
+3. Open Terminal Emulator and enter following commands to start Minikube:
 
     ```shell
     sudo minikube start --vm-driver=none
@@ -118,11 +119,11 @@ Now that the Linux VM has been successfully created, you can sign in to start mi
 
     ![](media/azure-stack-create-vm-template/11.PNG)
 
-4. Open the web browser and visit the Kubernetes dashboard address. Congratulations, you now have a fully working Kubernetes installation using minikube!
+4. Open the web browser and visit the Kubernetes dashboard address. Congratulations, you now have a fully working Kubernetes installation using Minikube!
 
     ![](media/azure-stack-create-vm-template/12.PNG)
 
-5. If you would like to deploy a sample application, visit the official documentation page of kubernetes, skip the "Create Minikube Cluster" section as you have already created one above. Simply jump to the section "Create your Node.js application" at https://kubernetes.io/docs/tutorials/stateless-application/hello-minikube/.
+5. To deploy a sample application, visit the official documentation page of Kubernetes, and skip the "Create Minikube Cluster" section as you have already created one above. Jump to the section "Create your Node.js application" at https://kubernetes.io/docs/tutorials/stateless-application/hello-minikube/.
 
 ## Next steps
 

articles/azure-stack/user/azure-stack-subscribe-services.md

@@ -14,17 +14,17 @@ pms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: tutorial
 ms.custom: mvc
-ms.date: 09/05/2018
+ms.date: 11/13/2018
 ms.author: sethm
 ms.reviewer: 
 ---
 
 # Tutorial: create and test a subscription
-This tutorial shows you how to create a subscription containing an offer and then test it. 
-For the test, you will sign in to the Azure Stack user portal as a cloud administrator, subscribe to the offer, and then create a virtual machine.
+
+This tutorial shows you how to create a subscription containing an offer and then test it. For the test, you sign in to the Azure Stack user portal as a cloud administrator, subscribe to the offer, and then create a virtual machine.
 
 > [!TIP]
-> For more a more advanced evaluation experience, you can [create a subscription for a particular user](https://docs.microsoft.com/azure/azure-stack/azure-stack-subscribe-plan-provision-vm#create-a-subscription-as-a-cloud-operator) and then login as that user in the user portal. 
+> For more a more advanced evaluation experience, you can [create a subscription for a particular user](../azure-stack-subscribe-plan-provision-vm.md#create-a-subscription-as-a-cloud-operator) and then sign in as that user in the user portal. 
 
 This tutorial shows you how to subscribe to an Azure Stack offer.
 
@@ -35,48 +35,49 @@ What you will learn:
 > * Test the offer
 
 ## Subscribe to an offer
-To subscribe to an offer as a user, you need to login to the Azure Stack user portal to discover the services that have been offered by the Azure Stack operator.
 
-1. Sign in to the user portal and click **Get a Subscription**.
+To subscribe to an offer as a user, you sign in to the Azure Stack user portal to discover the services that have been offered by the Azure Stack operator.
+
+1. Sign in to the user portal and select **Get a Subscription**.
 
    ![Get a subscription](media/azure-stack-subscribe-services/get-subscription.png)
 
-2. In the **Display Name** field, type a name for your subscription. Then, click **Offer** to select one of the available offers in the **Choose an offer** section and then click **Create**.
+2. In the **Display Name** field, type a name for your subscription. Then select **Offer** to choose one of the available offers in the **Choose an offer** section. Then select **Create**.
 
    ![Create an offer](media/azure-stack-subscribe-services/create-subscription.png)
 
    > [!TIP]
    > You must now refresh the user portal to start using your subscription.
 
-3. To view the subscription you created, click **All services**.  Then, under the **GENERAL** category select **Subscriptions**, and then select your new subscription. After you subscribe to an offer, refresh the portal to see if new services have been included as part of the new subscription. In this example, **Virtual machines** has been added.
+3. To view the subscription you created, select **All services**. Then, under the **GENERAL** category select **Subscriptions**, and then select your new subscription. After you subscribe to an offer, refresh the portal to see if new services have been included as part of the new subscription. In this example, **Virtual machines** has been added.
 
    ![View subscription](media/azure-stack-subscribe-services/view-subscription.png)
 
-
 ## Test the offer
-While logged in to the user portal, you can test the offer by provisioning a virtual machine using the new subscription capabilities. 
+
+While signed in to the user portal, you can test the offer by provisioning a virtual machine using the new subscription capabilities. 
 
 > [!NOTE]
 > This test requires that a Windows Server 2016 Datacenter VM has first been added to the Azure Stack marketplace. 
 
 1. Sign in to the user portal.
 
-2. In the user portal, click **Virtual Machines** > **Add** > **Windows Server 2016 Datacenter**, and then click **Create**.
+2. In the user portal, select **Virtual Machines**, then **Add**, then **Windows Server 2016 Datacenter**, and then click **Create**.
 
-3. In the **Basics** section, type a **Name**, **User name**, and **Password**, choose a **Subscription**, create a **Resource group** (or select an existing one), and then click **OK**.
+3. In the **Basics** section, type a **Name**, **User name**, and **Password**, choose a **Subscription**, create a **Resource group** (or select an existing one), and then select **OK**.
 
-4. In the **Choose a size** section, click **A1 Standard**, and then click **Select**.  
+4. In the **Choose a size** section, select **A1 Standard**, and then click **Select**.  
 
-5. In the Settings blade, accept the defaults and click **OK**.
+5. In the **Settings** blade, accept the defaults and select **OK**.
 
 6. In the **Summary** section, click **OK** to create the virtual machine.  
 
-7. To see your new virtual machine, click **Virtual machines**, then search for the new virtual machine, and click its name.
+7. To see your new virtual machine, select **Virtual machines**, then search for the new virtual machine, and click its name.
 
     ![All resources](media/azure-stack-subscribe-services/view-vm.png)
 
 > [!NOTE]
-> The virtual machine deployment will take a few minutes to complete.
+> The virtual machine deployment takes a few minutes to complete.
 
 
 ## Next steps