Merge pull request #227464 from shantanugg/docs-editor/azure-vm-plan-technical-config-1676484891

DOCS REQUEST 5687- Amanda's update request.

Author: denrea

articles/marketplace/azure-vm-plan-technical-configuration.md

@@ -73,11 +73,11 @@ Here is a list of properties that can be selected for your VM. Enable the proper
 
     - Virtual machines deployed with these images don't allow customers to access it using Remote Desktop or SSH. Learn more about [locked VM images](./azure-vm-certification-faq.yml#locked-down-or-ssh-disabled-offer). Images that are published with either SSH disabled (for Linux) or RDP disabled (for Windows) are treated as Locked down VMs. There are special business scenarios to restrict access to users. During validation checks, Locked down VMs might not allow execution of certain certification commands.
 
-    - Image does not support sampleuser while deploying.
+    - Image doesn't support sampleuser while deploying.
     - Image has limited access.
-    - Image does not comply with the Certification Test Tool.
+    - Image doesn't comply with the Certification Test Tool.
     - Image requires setup during initial login which causes automation to not connect to the virtual machine.
-    - Image does not support port 22.
+    - Image doesn't support port 22.
 
 - **Requires custom ARM template for deployment**: Enable this property if the images in this plan can only be deployed using a custom ARM template. In general, all the images that are published under a VM offer will follow standard ARM template for deployment. However, there are scenarios that might require customization while deploying VMs (for example, multiple NIC(s) to be configured).
 Below are examples (non-exhaustive) that might require custom templates for deploying the VM:
@@ -92,21 +92,23 @@ Below are examples (non-exhaustive) that might require custom templates for depl
 
 Generations of a virtual machine defines the virtual hardware it uses. Based on your customer’s needs, you can publish a Generation 1 VM, Generation 2 VM, or both. To learn more about the differences between Generation 1 and Generation 2 capabilities, see [Support for generation 2 VMs on Azure](../virtual-machines/generation-2.md).
 
-When creating a new plan, select an Image type from the drop-down menu. You can choose either X64 Gen 1 or X64 Gen 2. To add another image type to a plan, select **+Add image type**. You will need to provide a SKU ID for each new image type that is added.
+When creating a new plan, select an Image type from the drop-down menu. You can choose either X64 Gen 1 or X64 Gen 2. To add another image type to a plan, select **+Add image type**. You'll need to provide a SKU ID for each new image type that is added.
 
 > [!NOTE]
 > A published generation requires at least one image version to remain available for customers. To remove the entire plan (along with all its generations and images), select **Deprecate plan** on the **Plan Overview** page. Learn more about [deprecating plans](./deprecate-vm.md).
 >
 
 ## VM images
 
-To add a new image version, click **+Add VM image**. This will open a panel in which you will then need to specify an image version number. From there, you can provide your image(s) via either the Azure Compute Gallery and/or using a shared access signature (SAS) URI.
+To add a new image version, click **+Add VM image**. This will open a panel in which you'll then need to specify an image version number. From there, you can provide your image(s) via either the Azure Compute Gallery and/or using a shared access signature (SAS) URI.
+
+> [!IMPORTANT]
+> You can now provide more than one VM image per image type within a given submission. By adding multiple images at a time, you won't need to publish each image sequentially as part of separate submissions.   
 
 Keep in mind the following when publishing VM images:
 
-1.	Provide only one new VM image per image type in a given submission.
-2.	After an image has been published, you can't edit it, but you can deprecate it. Deprecating a version prevents both new and existing users from deploying a new instance of the deprecated version. Learn more about [deprecating VM images](./deprecate-vm.md).
-3.	You can add up to 16 data disks for each VM image provided. Regardless of which operating system you use, add only the minimum number of data disks that the solution requires. During deployment, customers can’t remove disks that are part of an image, but they can always add disks during or after deployment.
+1.	After an image has been published, you can't edit it, but you can deprecate it. Deprecating a version prevents both new and existing users from deploying a new instance of the deprecated version. Learn more about [deprecating VM images](./deprecate-vm.md).
+1.	You can add up to 16 data disks for each VM image provided. Regardless of which operating system you use, add only the minimum number of data disks that the solution requires. During deployment, customers can’t remove disks that are part of an image, but they can always add disks during or after deployment.
 
 > [!NOTE]
 > If you provide your images using the SAS URI method and you are adding data disks, you also need to provide them in the form of a SAS URI. Data disks are also VHD shared access signature URIs that are stored in your Azure storage accounts. If you are using a gallery image, the data disks are captured as part of your image in Azure Compute Gallery.
@@ -126,3 +128,4 @@ For VM offers with more than one plan, you can change the order that your plans
 
 - [Learn more about how to reorder plans](azure-vm-plan-reorder-plans.md)
 - [Resell through CSPs](azure-vm-resell-csp.md)
+