public repo edits

Author: ktoliver

articles/virtual-machines/extensions/features-windows.md

@@ -248,12 +248,9 @@ Moving the **command to execute** property to the **protected** configuration se
 }
 ```
 
-On an Azure IaaS VM using extensions, you might notice certificates with subject = **_"Windows Azure CRP Certificate Generator"_** in the certificates console.
-On a Classic RDFE VM, these certificates will have Subject Name = **_"Windows Azure Service Management for Extensions"_**.
-
-These certificates are there to secure the communication between the VM and its host, during the transfer of protected settings (password, etc…) used by extensions. They are built by the Azure Fabric Controller, and passed to the VM Agent. If you stop/start the VM every day, a new certificate might be created by the Fabric Controller and will be stored in the Computer's Personal certificates store. These certificates can be deleted, the VM Agent will recreate one if needed.
-
+On an Azure IaaS VM that uses extensions, in the certificates console, you might see certificates that have the subject **_Windows Azure CRP Certificate Generator_**. On a Classic RDFE VM, these certificates have the subject name **_Windows Azure Service Management for Extensions_**.
 
+These certificates secure the communication between the VM and its host during the transfer of protected settings (password, other credentials) used by extensions. The certificates are built by the Azure fabric controller and passed to the VM Agent. If you stop and start the VM every day, a new certificate might be created by the fabric controller. The certificate is stored in the computer's Personal certificates store. These certificates can be deleted. The VM Agent re-creates certificates if needed.
 
 ### How do agents and extensions get updated?