Minor fix How to WaPosh and rework How to Custom Create

Author: KBDAzure

DevCenter/Shared/Chunks/powershell.md

@@ -54,7 +54,7 @@ The following tasks are supported:
 
 <h2> <a id="GetStarted"></a>Get started using Windows Azure PowerShell</h2>
 
-The recommended way to install the Windows Azure PowerShell cmdlets is via the [Microsoft Web Platform Installer][wpi-installer]. After installing and launching the Web Platform Installer, select **Windows Azure PowerShell** and follow the prompts to install the cmdlets. The Web Platform Installer will install all dependencies for the Windows Azure PowerShell cmdlets. Note that you can also select **Windows Azure SDK for Node.js - July 2012** or **Windows Azure SDK for PHP - July 2012** as these SDKs will include the Windows Azure PowerShell cmdlets.
+The recommended way to install the Windows Azure PowerShell cmdlets is via the [Microsoft Web Platform Installer][wpi-installer]. After installing and launching the Web Platform Installer, select **Windows Azure PowerShell** and follow the prompts to install the cmdlets. The Web Platform Installer will install all dependencies for the Windows Azure PowerShell cmdlets.
 
 ### Getting started with Windows PowerShell
 

ITPro/Shared/Chunks/howto-custom-create-vm.md

@@ -2,64 +2,50 @@
 
 #How to Create a Custom Virtual Machine
 
-You can create a custom virtual machine by providing advanced options, such as size, connected resources, DNS name, and network connection. You must use this option if you want to connect virtual machines or if you want to use a custom image to create the machine. 
+Creating a custom virtual machine allows you to choose options that aren't available if you use the **Quick Create** method. These options include connecting to a virtual network, to an existing cloud service, and to an availability set.
 
-Before you create a virtual machine, you should decide how it will be used. If you have a need for only one virtual machine in your application, you choose to create a stand-alone virtual machine. If you need multiple virtual machines in the same cloud service that can communicate with each other and act as a load-balanced application, connect the new virtual machine to an existing virtual machine.
+Each virtual machine is associated with a cloud service, either by itself or with other virtual machines in the same cloud service. A common reason for placing more than one virtual machine in the same cloud service is to provide load balancing for the application. If your application needs only one virtual machine, or you're creating the first virtual machine, you will create the cloud service when you create the virtual machine. Otherwise, you will add the new virtual machine to an existing cloud service.
 
 **Important**: If you want your virtual machine to use a virtual network so you can connect to it directly by hostname or set up cross-premises connections, make sure you specify the virtual network when you create the virtual machine. A virtual machine can be configured to join a virtual network only when you create the virtual machine. For more information about virtual networks, see [Windows Azure Virtual Network Overview](http://go.microsoft.com/fwlink/p/?LinkID=294063).
 
 1. Sign in to the [Windows Azure Management Portal](http://manage.windowsazure.com).
 
 2. On the command bar, click **New**.
 
-	![Create a new virtual machine][Create a new virtual machine]
+3. Click **Compute**, click **Virtual Machine**, and then click **From Gallery**.
 
-3. Click **Virtual Machine**, and then click **From Gallery**.
-
-	![Create a new custom virtual machine][Create a new custom virtual machine]
-
-	The **Select the virtual machine operating system** dialog box appears.  
-
-	
 4. From **Platform Images**, select a platform image that you want to use, and then click the arrow to continue.
-
-	**Note**: These instructions describe the selection of a Windows Server image, but the instructions also apply to Linux images.
-
-	The **Virtual machine configuration** dialog box appears.
-
 
-5. In **Virtual Machine Name**, type the name that you want to use for the virtual machine.
-
-6. In **New User Name**, type a name for the administrative account that you want to use to manage the server. 
+5.  If multiple versions of the image are available, in **Version Release Date**, pick the version you want to use.
 
-7. In **New Password**, type a strong password to use for the administrative account on the virtual machine. In **Confirm Password**, retype the same password.
+6. In **Virtual Machine Name**, type the name that you want to use for the virtual machine.
 
-8. In **Size**, select the size that you want to use for the virtual machine. The size that you select depends on the number of cores that are needed for your application.
+7. In **Size**, select the size that you want to use for the virtual machine. The size that you select depends on the number of cores that are needed for your application.
 
-9. Click the arrow to continue.
+8. In **New User Name**, type a name for the administrative account that you want to use to manage the server. 
 
-	The **Virtual machine mode** dialog box appears.
-	
-10. Choose whether this virtual machine will be a stand-alone virtual machine, or connected to other virtual machines in the same cloud service to balance the load of traffic to the application. For more information about connecting virtual machines, see [How to connect virtual machines in a cloud service](http://www.windowsazure.com/en-us/manage/windows/how-to-guides/connect-to-a-cloud-service/).
+9. In **New Password**, type a strong password to use for the administrative account on the virtual machine. In **Confirm Password**, retype the same password.
 
-11. If it will be a stand-alone virtual machine, in **DNS Name**, type a name for the cloud service that is created for the machine. The entry can contain from 3 through 24 lowercase letters and numbers.
+10. Click the arrow to continue.
 
-12. In **Storage Account**, select an existing storage account for the VHD file, or use an automatically generated storage account. Only one storage account per region is automatically created. All other virtual machines that you create with this setting are located in this storage account. You are limited to 20 storage accounts.
-
-13. In **Region/Affinity Group/Virtual Network**, select region, affinity group, or virtual network that you want to use for the virtual machine. For more information about affinity groups, see [About Affinity Groups for Virtual Network][].
+11. In **Cloud Service**, do one of the following:
+	
+- If this is the first or only virtual machine in the cloud service, select **Create a New Cloud Service**. Then, in **Cloud Service DNS Name**, type a name that uses between 3 and 24 lowercase letters and numbers. This name becomes part of the URI that is used to contact the virtual machine through the cloud service.
+- If this virtual machine is being added to a cloud service, select it in the list.
 
-14. Click the arrow to continue.
+	**Note**: For more information about placing virtual machines in the same cloud service, see [How to connect virtual machines in a cloud service](http://www.windowsazure.com/en-us/manage/windows/how-to-guides/connect-to-a-cloud-service/).
 
-	The **Virtual machine options** dialog box appears.
+12. In **Region/Affinity Group/Virtual Network**, select region, affinity group, or virtual network that you want to use for the virtual machine. For more information about affinity groups, see [About Affinity Groups for Virtual Network][].
 
+13. In **Storage Account**, select an existing storage account for the VHD file, or use an automatically generated storage account. Only one storage account per region is automatically created. All other virtual machines that you create with this setting are located in this storage account. You are limited to 20 storage accounts.
 
-15. (Optional) In **Availability Set**, select **Create availability set**. When a virtual machine is a member of an availability set, it is deployed to different fault domains than other virtual machines in the set. Multiple virtual machines in an availability set help ensure that your application is available during network failures, local disk hardware failures, and any planned downtime.
+14. If you want the virtual machine to belong to an availability set, In **Availability Set**, select **Create availability set** or add it to an existing availability set. 
 
-	If you are creating an availability set, type a the name for the availability set.
+	**Note**: Virtual machine that are members of an availability set are deployed to different fault domains. Placing multiple virtual machines in an availability set helps ensure that your application is available during network failures, local disk hardware failures, and any planned downtime.
 
-16. (Optional) If you want the virtual machine to use a virtual network, choose the virtual network subnet. For more information about virtual networks, see [Windows Azure Virtual Network Overview](http://go.microsoft.com/fwlink/p/?LinkID=294063).
+15.  Under Endpoints, review the new endpoints that will be created to allow connections to the virtual machine, such through Remote Desktop or a Secure Shell (SSH) client. You also can add endpoints now, or create them later. For instructions on creating them later, see [How to Set Up Communication with a Virtual Machine](http://www.windowsazure.com/en-us/manage/linux/how-to-guides/setup-endpoints/). 
 
-17. Click the arrow to create the virtual machine.
+16. Click the arrow to create the virtual machine.
 
 	![Custom virtual machine creation successful][Custom virtual machine creation successful]