Apply suggestions from code review

SECURITY.md

@@ -14,7 +14,7 @@ Instead, please report them to the Microsoft Security Response Center (MSRC) at
 
 If you prefer to submit without logging in, email [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey).
 
-You should receive a response within 24 hours. If you still need to, please email us to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). 
+You should receive a response within 24 hours. If you do not, you can email us to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). 
 
 Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
 
@@ -28,7 +28,7 @@ Please include the requested information listed below (as much as you can provid
 
 This information will help us triage your report more quickly.
 
-More complete reports can contribute to a higher bounty award if you are reporting for a bug bounty. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs.
+If you are reporting for a bug bounty, providing more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs.
 
 ## Preferred Languages
 

ThirdPartyNotices.md

@@ -5,11 +5,11 @@ see the [LICENSE](LICENSE) file, and grant you a license to any code in the repo
 [LICENSE-CODE](LICENSE-CODE) file.
 
 Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation
-Microsoft may be either trademarks or registered trademarks in the United States and/or other countries.
+may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries.
 The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks.
 Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.
 
 Privacy information can be found at https://privacy.microsoft.com/en-us/
 
-Microsoft and any contributors reserve all other's rights, whether under their respective copyrights, patents,
+Microsoft and any contributors reserve all other rights, whether under their respective copyrights, patents,
 or trademarks, whether by implication, estoppel, or otherwise.

markdown templates/aml-templates/template-concepts.md

@@ -1,6 +1,6 @@
 ---
 title: CONCEPT SUCH AS Web Services in Azure Machine Learning in 59 chars or less. Include the name Azure Machine Learning. Test title here https://moz.com/learn/seo/title-tag 
-description: This string describes the article in 115 to 145 characters. Use SEO kind of action verbs here. Such as - Learning how to do this and that using customer words. This info is displayed on the search page in line with the article date stamp. If your intro para describes your article's intent, you can use it here, edited for length.
+description: This string describes the article in 115 to 145 characters. Use SEO kind of action verbs here. For example, Learning how to do this and that using customer words. This info is displayed on the search page in line with the article date stamp. If your intro paragraph describes your article's intent, you can use it here, edited for length.
 services: machine-learning
 ms.service: machine-learning
 ms.subservice: core

markdown templates/aml-templates/template-howto.md

@@ -10,7 +10,7 @@ ms.author: your-msft-alias
 author: your-github-account-name
 ms.date: 04/10/2018
 ---
-# This H1 is the title of the article. It appears in search, appears at the top of the article, and has the second greatest impact on search, 100 chars or less.
+# This H1 is the title of the article. It appears in search, appears at the top of the article, and has the second greatest impact on search. 100 chars or less.
 
 Guidance [here](https://review.learn.microsoft.com/help/contribute/contribute-how-to-write-seo-basics?branch=main)
 

markdown templates/markdown-template-for-support-articles-troubleshoot.md

@@ -5,7 +5,7 @@ services: service-name
 documentationcenter: dev-center-name
 author: GitHub-alias-of-only-one-author
 manager: manager-alias
-editor:"
+editor: editor-alias
 tags: top-support-issue
 
 ms.service: required

markdown templates/virtual-machines-ps-template-compare-sm-arm-task.md

@@ -11,7 +11,7 @@ Pay attention to spacing and indents. They affect formatting.
 <!--replace this with Properties and Tags sections. These are required sections. See "article-metadata.md" under your repo's "contributor-guide" folder. Attributes in each section can be placed on separate lines to make them easier to read and check-->
 
 # Use Azure PowerShell to [task]
-This article shows you how to [task] using commands from the Azure and the Azure Resource Manager modules. This is intended to help you learn the new commands and migrate existing scripts to the new commands.
+This article shows you how to [task] by using commands from the Azure and the Azure Resource Manager modules. This is intended to help you learn the new commands and migrate existing scripts to the new commands.
 
 ## Prerequisite: Install a Recent Version of Azure PowerShell
 If you haven't done so already, install at least the [version number] version of Azure PowerShell on your local computer. Using an earlier version will have different Azure Resource Manager cmdlets described in this article. For details, see:
@@ -32,13 +32,13 @@ Then, use the following syntax to add a reference to the image in your article:
 ![](./media/name-of-file-without-extension/image-name-no-spaces.png)
 -->
 
-<!--if a command string uses variables, define the variables first using the following construction. Sometimes, the variable is straightforward and doesn't need much explanation. But parameters such as location and size can benefit from brief description or listing of all accepted values:--> 
+<!--if a command string uses variables, define the variables first using the following construction. In some cases, the variable is straightforward and doesn't need much explanation. But parameters such as location and size can benefit from brief explanation or listing of all accepted values:--> 
 
 These command examples use the following variables:
 
 $FriendlyName"\<Describe value>"
 
-<!-- if it makes more sense to present this in a table, use this. Otherwise, delete. The table will render once it's in GitHub or published to Sandbox.-->
+<!-- if it makes more sense to present this in a table, use this. Otherwise, delete. The table will render after it's in GitHub or published to Sandbox.-->
 
 | Service Management | Resource Manager |
 | --- | --- |