Cleaned up grammar

Author: v-miegge

articles/virtual-machines/extensions/considerations-using-vm-extensions-python-3.md

@@ -4,7 +4,7 @@ description: Learn about using VM extensions in Python 3-enabled Linux systems
 services: virtual-machines-windows
 documentationcenter: ''
 author: v-miegge
-ms.author: 
+ms.author: jparrel
 manager: dcscontentpm
 editor: ''
 tags: top-support-issue,azure-resource-manager
@@ -21,7 +21,7 @@ ms.assetid: 3cd520fd-eaf7-4ef9-b4d3-4827057e5028
 
 ## Summary
 
-Some Linux distributions have transitioned to Python 3.x and removed the legacy `/usr/bin/python` entry point for Python. This impacts the out-of-the-box, automated deployment of certain virtual machine (VM) extensions which exhibit the following conditions:
+Some Linux distributions have transitioned to Python 3.x and removed the legacy `/usr/bin/python` entry point for Python. The Python 3.x transition impacts the out-of-the-box, automated deployment of certain virtual machine (VM) extensions that exhibit the following conditions:
 
 - Working on Python 3.x support in their road map
 - Using the legacy /usr/bin/python entry point
@@ -37,13 +37,13 @@ Azure Virtual Machines customers running the Linux operating system can deploy e
 
 Each extension has their own road map and release cadence, and can be offered by Microsoft or certain third-party partners.
 
-Customers can deploy an extension via the REST API, with the `azure-cli` or through the Azure Portal, which extends the VM model to reference the extension.
+Customers can deploy an extension via the REST API, with the `azure-cli` or through the Azure portal, which extends the VM model to reference the extension.
 
 Extensions are packaged for deployment through the Azure Linux Agent. Upon extending the VM model with the extension, the Azure Linux Agent fetches the extension package. In this package, extensions ship a JSON manifest with specific commands for lifecycle operations, and the Azure Linux Agent executes those commands for each operation.
 
-However, extensions might be written in any language that can execute in Linux, such as Python or shell scripts, and contain arbitrary logic. That means that some extensions use a legacy /usr/bin/python entry point. Since the extensions are packaged, and the Azure Linux Agent does not handle each extension’s specific logic, certain extensions might fail to deploy when those pre-requisites aren’t met. This is the case in the conditions described previously in the Summary.
+However, extensions might be written in any language that can execute in Linux, such as Python or shell scripts, and contain arbitrary logic. Some extensions, therefore, use a legacy /usr/bin/python entry point. Since the extensions are packaged, and the Azure Linux Agent doesn't handle each extension’s specific logic, certain extensions might fail to deploy when those pre-requisites aren’t met. This failure is described previously in the Summary.
 
-Failed deployments might take several minutes to time out and send both error messages and failure conditions in the Azure Portal, automated scripts, and other interfaces.
+Failed deployments might take several minutes to time out and send both error messages and failure conditions in the Azure portal, automated scripts, and other interfaces.
 
 ## Resolution
 
@@ -58,7 +58,7 @@ Customers might want to consider the following general recommendations before de
 
 1. Engage Azure Support in case additional troubleshooting or debugging support is needed when deploying extensions in the known-affected scenarios described in the Summary
 
-> [!Note]:
+> [!Note]
 > For Python 2.7, above, Microsoft encourages customers to adopt Python 3.x in their systems unless their workload requires Python 2.x support. Examples could include legacy administration scripts, or extensions such as Azure Disk Encryption and Azure Monitor.
 
 Before installing Python 2.x in production, customers should consider the question of long-term support of Python 2.x, particularly their ability to receive security updates.