Merge pull request #108834 from arpitjain099/master

Fix english typos and grammar in documentation #4398

Author: Jak-MS

CODE_OF_CONDUCT.md

@@ -1,2 +1,2 @@
 This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
-For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments.
+For more information, see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments.

README.md

@@ -4,23 +4,23 @@ Welcome to the open-source [documentation](/azure) of [Microsoft Azure](https://
 
 ## Getting Started
 
-Contributing to open source is more than just providing updates, it's also about letting us know when there is an issue. Read our [Contributing guidance](CONTRIBUTING.md) to find out more.
+Contributing to open source is more than just providing updates. It's also about letting us know when there is an issue. Read our [Contributing guidance](CONTRIBUTING.md) to find out more.
 
 ### Prerequisites
 
-You've decided to contribute, that's great! To contribute to the documentation, you need a few tools.
+You've decided to contribute. That's great! To contribute to the documentation, you need a few tools.
 
 #### GitHub
 
 Contributing to the documentation requires a GitHub account. If you don't have an account, follow the instructions for [GitHub account setup](https://learn.microsoft.com/contribute/get-started-setup-github) from our contributor guide.
 
 #### Tools
 
-To install necessary tools, follow the instructions for [Install content authoring tools](https://learn.microsoft.com/contribute/get-started-setup-tools) from our contributor guide.
+To install the necessary tools, follow the instructions for [Install content authoring tools](https://learn.microsoft.com/contribute/get-started-setup-tools) from our contributor guide.
 
 ## License
 
-Please refer to [LICENSE](LICENSE), [LICENSE-CODE](LICENSE-CODE) and [ThirdPartyNotices](ThirdPartyNotices.md) for all Licensing information.
+Please refer to [LICENSE](LICENSE), [LICENSE-CODE](LICENSE-CODE), and [ThirdPartyNotices](ThirdPartyNotices.md) for all Licensing information.
 
 ## Code of Conduct
 

SECURITY.md

@@ -12,13 +12,13 @@ If you believe you have found a security vulnerability in any Microsoft-owned re
 
 Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report).
 
-If you prefer to submit without logging in, send email to [[email protected]](mailto:[email protected]).  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).
+If you prefer to submit without logging in, email [[email protected]](mailto:[email protected]). 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 for some reason you do not, please follow up via email 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:
 
-  * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
+  * Type of issue (e.g., buffer overflow, SQL injection, cross-site scripting, etc.)
   * Full paths of source file(s) related to the manifestation of the issue
   * The location of the affected source code (tag/branch/commit or direct URL)
   * Any special configuration required to reproduce the 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.
 
-If you are reporting for a bug bounty, 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.
+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

@@ -1,7 +1,7 @@
 ## Legal Notices
 Microsoft and any contributors grant you a license to the Microsoft documentation and other content
 in this repository under the [Creative Commons Attribution 4.0 International Public License](https://creativecommons.org/licenses/by/4.0/legalcode),
-see the [LICENSE](LICENSE) file, and grant you a license to any code in the repository under the [MIT License](https://opensource.org/licenses/MIT), see the
+see the [LICENSE](LICENSE) file, and grant you a license to any code in the repository under the [MIT License](https://opensource.org/licenses/MIT). See the
 [LICENSE-CODE](LICENSE-CODE) file.
 
 Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation
@@ -11,5 +11,5 @@ Microsoft's general trademark guidelines can be found at http://go.microsoft.com
 
 Privacy information can be found at https://privacy.microsoft.com/en-us/
 
-Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents,
-or trademarks, whether by implication, estoppel or otherwise.
+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 - Learn how to do this and that using customer words. This info is displayed on the search page inline 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
@@ -15,7 +15,7 @@ ms.date: 04/10/2018
 ## Section here H2 
 Paragraph here. 
 **This phrase is bold**
-*This phrase is italics*
+*This phrase is in italics*
 
 This is a [hyperlink to an article](template-concepts.md)
 
@@ -49,7 +49,7 @@ This is a numbered list:
 
 5. Fifth item
 
-## This list is bulleted list:
+## This list is a bulleted list:
 - Item 1
 - Item 2
 - Item 3

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

@@ -1,6 +1,6 @@
 ---
 title: Verb action for Azure Machine Learning in 59 chars or less. Include the name Azure Machine Learning. Test title here https://moz.com/learn/seo/title-tag  (EXAMPLE - Deploying web services in Python with Azure Machine Learning)
-description: Learn how to do this and that using customer words in Azure Machine Learning. This string describes the article in 115 to 145 characters. Use SEO kind of action verbs here. This info is displayed on the search page inline with the article date stamp. If your intro para describes your article's intent, you can use it here edited for length.
+description: Learn how to do this and that using customer words in Azure Machine Learning. This string describes the article in 115 to 145 characters. Use SEO kind of action verbs here. 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.
 services: machine-learning
 ms.service: machine-learning
 ms.subservice: core
@@ -10,28 +10,28 @@ 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 article, 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)
 
 
-1st paragraph	provides the primary intent of the article in 1 or 2 short sentences. 
+1st paragraph provides the primary intent of the article in 1 or 2 short sentences. 
 
 ## Prerequisites
-To step through this how-to guide, you need:
+To step through this how-to guide, you need the following:
 - [A machine learning account](template-howto.md)
 
 ## Section here H2 
 Paragraph here. 
 **This phrase is bold.**
-*This phrase is italics.*
+*This phrase is in italics.*
 
 This is a [hyperlink to an article](./template-concepts.md)
 
 This is an image:
 
 ![This is an image description](media/overview-what-is-azure-ml/aml-concepts.png)
-Note that images need to be stored in the media folder with a subdirectory matching the name of the article and then the filename.
+Note that images need to be stored in the media folder with a subdirectory matching the article's name and then the filename.
 
 ## Section here H2
 This table has headings:
@@ -59,7 +59,7 @@ This is a numbered list:
 
 5. Fifth item
 
-## This list is bulleted list:
+## This list is a bulleted list:
 - Item 1
 - Item 2
 - Item 3

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
@@ -28,9 +28,9 @@ ms.author: Your MSFT alias or your full email address;semicolon separates two or
 
 [Opening paragraph]
 
-* *Briefly describe the specific issue(s) that this article will help troubleshoot, and the common root cause(s).*
-* *The opening paragraph is a good place to use different keywords from those in the title, but make sure to not make it very wordy. The sentences should flow well and be easy to understand.*
-* *Exceptions (optional) - List the relevant scenarios that are not covered in this article. For example, ” Linux/OSS scenarios aren't covered in this article”.*
+* *Briefly describe the specific issue(s) this article will help troubleshoot and the common root cause(s).*
+* *The opening paragraph is a good place to use different keywords from those in the title, but make sure not to make it very wordy. The sentences should flow well and be easy to understand.*
+* *Exceptions (optional) - List the relevant scenarios that are not covered in this article. For example," Linux/OSS scenarios aren't covered in this article".*
 
 These {errors}|{Issues} occur because {a very general reason}.
 
@@ -42,9 +42,9 @@ These {errors}|{Issues} occur because {a very general reason}.
 * *Password validation failed.*
 * *Failed to authorize access to the specified subscription.*
 
-*These errors occur because you don’t have permission to access the data source.*
+*These errors occur because you don't have permission to access the data source.*
 
-*If it is an article on the billing topic, include the following note (the note below is slightly different than the one at the bottom of this article):*
+*If it is an article on the billing topic, include the following note (the note below is slightly different from the one at the bottom of this article):*
 
 > [!NOTE]
 > If you need more help at any point in this article, please [contact support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade) to get your issue resolved quickly.
@@ -56,14 +56,14 @@ These {errors}|{Issues} occur because {a very general reason}.
 
 ## Troubleshooting guidance (optional)
 * *Use this section when the guidance applies across the board.*
-* *Don’t go into details. Keep it high level to serve as a guidance.*
+* * Don't go into details. Keep it high level to serve as a guide.*
 
-*Here is an example of a troubleshooting guidance.*
+*Here is an example of troubleshooting guidance.*
 
-*In general, as long as the error does not indicate "the requested VM size is not supported", you can always retry at a later time, as enough resource may have been freed up in the cluster to accommodate your request. If the problem is the requested VM size is not supported, try a different VM size; otherwise, the only option is to remove the pinning constraint.*
+*In general, if the error does not indicate "the requested VM size is not supported," you can always retry later, as enough resources may have been freed up in the cluster to accommodate your request. If the problem is that the requested VM size is not supported, try a different VM size; otherwise, the only option is to remove the pinning constraint.*
 
 ## Troubleshooting steps
-*List the solutions in the order of usability and simplicity, meaning the simplest, the most effective and useful solution should go first.*
+*List the solutions in the order of usability and simplicity, meaning the simplest, most effective, and most useful solution should go first.*
 
 *Select one of the versions that apply to your situation.*
 
@@ -72,9 +72,9 @@ These {errors}|{Issues} occur because {a very general reason}.
 | <p><h3>[Issue 1] \ |[Error 1]</h3><h4>Cause</h4>[Cause details]</p><p><h4>Solution 1</h4><em>(the simplest and most effective)</em></p><ol><li>[Step 1]</li><li>[Step 2]</li></ol><p><h4>Solution 2</h4><em>(the less simple or effective)</em></p><ol><li>[Step 1]</li><li>[Step 2]</li></ol><p><h3>[Issue 2] \ |[Error 2]</h3><h4>Cause</h4>[Cause details]</p><p><h4>Solution 1</h4><em>(the simplest and most effective)</em></p><ol><li>[Step 1]</li><li>[Step 2]</li></ol><p><h4>Solution 2</h4><em>(the simplest and most effective)</em></p><ol><li>[Step 1]</li><li>[Step 2]</li></ol><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /> |
 
 ## Next steps
-*Include this section if there are 1 -3 concrete, highly relevant next steps the user should take. Delete if there are no next steps. This is not a place for a list of links. If you include links to next steps, make sure to include text to explain why the next steps are relevant/ important.*
+*Include this section if there are 1 -3 concrete, highly relevant next steps the user should take. Delete if there are no next steps. This is not a place for a list of links. If you include links to the next steps, include text to explain why the next steps are relevant/ important.*
 
-*If it is an article on the billing topic, include the following note (the note below is slightly different than the one at the beginning of this article):*
+*If it is an article on the billing topic, include the following note (the note below is slightly different from the one at the beginning of this article):*
 
 > [!NOTE]
 > If you still have further questions, please [contact support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade) to get your issue resolved quickly.