Fixed the Acrolinx score

Author: Padmalathas

articles/cyclecloud/how-to/create-custom-image.md

@@ -7,7 +7,7 @@ ms.author: adjohnso
 ---
 # Custom Images in a CycleCloud Cluster
 
-An Azure CycleCloud installation uses recommended OS images for clusters by default, but the use of Azure Marketplace images, Gallery images (in preview) or custom images in nodes and nodearrays is also supported. Custom images are useful for pre-installed applications in a cluster, or to fulfill business or security requirements.
+An Azure CycleCloud installation uses recommended OS images for clusters by default, but the use of Azure Marketplace images, Gallery images (in preview) or custom images in nodes and nodearrays is also supported. Custom images are useful for preinstalled applications in a cluster, or to fulfill business or security requirements.
 
 ## Specify a Custom Image via the Cluster UI
 
@@ -16,7 +16,7 @@ Custom and marketplace images are supported in the cluster UI. Instead of select
 ![Custom Images](~/articles/cyclecloud/images/custom-image.png)
 
 > [!NOTE]
-> This is only supported in CycleCloud versions >7.7.0
+> Customer Image is supported only in CycleCloud versions later than 7.7.0.
 
 ## Use a Custom Image in a CycleCloud Template
 
@@ -41,11 +41,11 @@ You can also specify a Marketplace or Gallery image by using the URN:
 ```
 
 > [!NOTE]
-> CycleCloud versions prior to 7.7.0 [require a different notation](#custom-image-notation-prior-7-7-0).
+> CycleCloud versions earlier than 7.7.0 [require a different notation](#custom-image-notation-prior-7-7-0).
 
 ### Use an Azure Marketplace Image with a Pricing Plan
 
-You can use a Marketplace image with an associated pricing plan but the image must be enabled for programmatic use. To do this, locate the Marketplace image you want to use. Click **Want to deploy programmatically**, **Get Started ->**, and enter any required information and save it.
+You can use a Marketplace image with an associated pricing plan but the image must be enabled for programmatic use. To complete this process, locate the desired image in the Marketplace, click **Want to deploy programmatically**, then select **Get Started ->**, fill in the required information, and save your changes.
 
 ::: moniker range=">=cyclecloud-8"
 To enable CycleCloud to automatically accept license terms on your behalf, enable the "Accept marketplace terms on my behalf" option on your subscription in the web interface:
@@ -67,7 +67,7 @@ az vm image accept-terms --publisher PUBLISHER --offer OFFER --plan SKU
 
 ### Use a Shared Image Gallery image with a Pricing Plan
 
-CycleCloud 8.0.2 and up support custom images created from images with a pricing plan. This requires using a custom template:
+Starting with CycleCloud version 8.0.2, custom images derived from those with a pricing plan are supported. This functionality requires the use of a custom template:
 
 ``` ini
 [[node custom_image]]
@@ -78,23 +78,23 @@ CycleCloud 8.0.2 and up support custom images created from images with a pricing
  ImagePlan.Name = NAME (sometimes called SKU)
 ```
 
-If the Shared Image Gallery has the purchase-plan metadata on it, it is used automatically and you do not need to specify the plan details.
+If the Shared Image Gallery has the purchase-plan metadata on it, it's used automatically and you don't need to specify the plan details.
 
 ## Create a Custom Image
 
 Custom Azure Images can be created by following [this tutorial.](/azure/virtual-machines/image-version-vm-cli#create-an-image-definition)
 
 > [!NOTE]
-> Please use generalized images since specialized images have not been through the process to remove machine specific information and accounts, and specialized images do not contain osProfile which CycleCloud requires.
+> Generalized images have been recommended, as specialized images haven't undergone the process to remove machine-specific information and accounts, and they lack the osProfile required by CycleCloud.
 
 <a name="custom-image-notation-prior-7-7-0"></a>
-## Custom Images on prior CycleCloud versions (<7.7.0)
+## Custom Images on CycleCloud versions earlier than 7.7.0
 
-Custom and marketplace images are supported in CycleCloud versions prior to 7.7.0 but they use a different notation. To use a custom image in a CycleCloud template prior to version 7.7.0, the `ImageId` attribute is used to specify the custom Azure image. This ID can be found in the Azure portal as the Resource ID for the image, and generally takes the form:
+Custom and marketplace images are supported in CycleCloud versions earlier than 7.7.0 but they use a different notation. To use a custom image in a CycleCloud template earlier than version 7.7.0, the `ImageId` attribute is used to specify the custom Azure image. This ID can be found in the Azure portal as the Resource ID for the image, and generally takes the form:
 
 `/subscriptions/$SUBSCRIPTION-ID/resourceGroups/$RESOURCEGROUPNAME/providers/Microsoft.Compute/images/$CustomImageName`
 
-Marketplace images prior to version 7.7.0 need to be specified using their Publisher/Offer/Sku/Version explicitly. They also need to specify `JetpackPlatform` so the correct jetpack packages is installed. Acceptable values for `JetpackPlatform` are: `centos-6`,`centos-7`, `ubuntu-14.04`, `ubuntu-16.04`, and `windows`. This should match the operating system of the Azure Marketplace image. Additionally, `InstallJetpack` must be set to true.
+For CycleCloud versions earlier than 7.7.0, Marketplace images must be specified explicitly using their Publisher, Offer, SKU, and Version. Also, the `JetpackPlatform` attribute must be defined to ensure the correct Jetpack packages are installed. Accepted values for `JetpackPlatform` include `centos-6`,`centos-7`, `ubuntu-14.04`, `ubuntu-16.04`, and `windows`, and this should align with the operating system of the Azure Marketplace image. The `InstallJetpack` must also be set to true.
 
 ``` ini
 [[node custom]]