More files

Author: arpitjain099

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
 

ThirdPartyNotices.md

@@ -1,15 +1,15 @@
 ## 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
-may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries.
+Microsoft may be either trademarks or registered trademarks 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 others rights, whether under their respective copyrights, patents,
-or trademarks, whether by implication, estoppel or otherwise.
+Microsoft and any contributors reserve all other's rights, whether under their respective copyrights, patents,
+or trademarks, whether by implication, estoppel, or otherwise.

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:"
 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.

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

@@ -1,20 +1,20 @@
-<!--save a copy of this file to your local repo. It's important that you follow the naming conventions by starting with the service name, and use lowercase only for the file name. See "file-names-and-locations.md" under the "contributor-guide" folder in your repo.
+<!--save a copy of this file to your local repo. It's important that you follow the naming conventions by starting with the service name and using lowercase only for the file name. See "file-names-and-locations.md" under your repo's "contributor-guide" folder.
 
-Info to help you use the template are enclosed in the Markdown comments using the caret, hyphen, dash syntax. Delete these from your file.
+Info to help you use the template is enclosed in the Markdown comments using the caret, hyphen, and dash syntax. Delete these from your file.
 
-Text not wrapped in comment syntax is intended to be used as is, or with updates enclosed in [  ]. Add the info and delete the bracket. 
+Text not wrapped in comment syntax is intended to be used as is or with updates enclosed in [  ]. Add the info and delete the bracket. 
 
 Pay attention to spacing and indents. They affect formatting. 
 
 --> 
 
-<!--replace this with Properties and Tags sections. These are required sections. See "article-metadata.md" in under the "contributor-guide" folder in your repo. Attributes in each section can be placed on separate lines to make them easier to read and check-->
+<!--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 both the Azure module and the Azure Resource Manager module. This is intended to help you learn the new commands as well as migrate existing scripts to the new commands.
+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.
 
 ## 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. If you use an earlier version, it won't have the Azure Resource Manager cmdlets described in this article. For details, see:
+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:
 
 * [How to install and configure Azure PowerShell](install-configure-powershell.md) for instructions on setting up Azure PowerShell.
 * [Using Windows PowerShell with Resource Manager](powershell-azure-resource-manager.md) for basics on using Resource Manager.
@@ -27,33 +27,33 @@ If you haven't done so already, install at least the [version number] version of
 ## Command Comparison
 This [table | section] shows the command syntax.
 
-<!--[optional image - to use an image in this article, add a folder with the same name as the article file name without extension, inside the Media folder of the repo. Use only this folder to store the images. Don't attempt to use a common folder to share images you want to use in more than 1 file.]
+<!--[optional image - to use an image in this article, add a folder with the same name as the article file name without extension inside the Media folder of the repo. Use only this folder to store the images. Don't attempt to use a common folder to share images you want to use in more than 1 file.]
 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. 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 all accepted values:--> 
+<!--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:--> 
 
 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 won't render until 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 once it's in GitHub or published to Sandbox.-->
 
 | Service Management | Resource Manager |
 | --- | --- |
 | `syntax` |`syntax` |
 
 <!--if it makes more sense to present this one command block after the other instead of a table, use this. Otherwise, delete-->
 
-[Short intro sentence about the command. Omit if there's really nothing to say. But if it uses approaches such as the pipeline, explain that]:
+[Short intro sentence about the command. Omit if there's nothing to say. But if it uses approaches such as the pipeline, explain that]:
 
     [command string]
 
 ## Script Examples
 Here's an example that uses [cmdlet names)] to [task]. It includes commands that:
 
-* [short verb, uses, has, is, etc]
+* [short verb, uses, has, is, etc.]
 * [next short verb] 
 
 <!--include this statement if it uses variables that weren't introduced earlier--> It includes the following variables:
@@ -88,11 +88,11 @@ Here's an example that uses [cmdlet names)] to [task]. It includes commands that
 
 
 ## Additional Resources
-<!--At a minimum, include a link back to the migration task list article. Use the formats shown below. See create-links-markdown.md for more info -->
+<!--At a minimum, include a link to the migration task list article. Use the formats shown below. See create-links-markdown.md for more info -->
 <!--use this format for links to other articles, such as the migration task list. -->
 [Manage Availability](../articles/virtual-machines/windows/manage-availability.md?toc=/azure/virtual-machines/windows/toc.json)
 
-<!--To link to an ACOM page outside the `/documentation/` subdomain (such as a pricing page, SLA page or anything else that is not a documentation article), use an absolute URL, but omit the locale:
+<!--To link to an ACOM page outside the `/documentation/` subdomain (such as a pricing page, SLA page, or anything else that is not a documentation article), use an absolute URL, but omit the locale:
 
     [link text](https://azure.microsoft.com/pricing/details/virtual-machines/)-->