From e8e4798f5030642ef4595b0f82904a852dd8c8de Mon Sep 17 00:00:00 2001 From: Avi Garg <32339251+avisionx@users.noreply.github.com> Date: Sat, 13 Oct 2018 15:31:09 +0530 Subject: [PATCH] Grammatical fixes in README.md --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 70a1bae672e3..a2b9d8c3b645 100644 --- a/README.md +++ b/README.md @@ -11,17 +11,17 @@ In the Azure Developer Experience workflow, you are at Step 3: [API Design Review](https://github.com/Azure/adx-documentation-pr#begin-api-design-review) -> [Engage with ADX team](https://github.com/Azure/adx-documentation-pr/blob/master/README.md#engage-with-adx-team) -> _**[Swagger specification](https://github.com/Azure/adx-documentation-pr#create-swagger-specification)**_ -> [SDKs](https://github.com/Azure/adx-documentation-pr#sdks) -> [CLIs](https://github.com/Azure/adx-documentation-pr#clis) -If you're a spec author looking for information about all of of the repositories and steps in the pipeline, go back to the [adx-documentation-pr](https://github.com/Azure/adx-documentation-pr) repository. Make sure to [join the Github Azure organization](http://aka.ms/azuregithub) to get access to that repo. +If you're a spec author looking for information about all of the repositories and steps in the pipeline, go back to the [adx-documentation-pr](https://github.com/Azure/adx-documentation-pr) repository. Make sure to [join the Github Azure organization](http://aka.ms/azuregithub) to get access to that repo. ## Getting started - Our [Contribution guidelines](./.github/CONTRIBUTING.md) walks you through the process of contributing to this repository. - The [/documentation](./documentation/) folder contains reference documentation for all aspects of Swagger and our recommended patterns. Start with the [Creating Swagger](./documentation/creating-swagger.md) page. -- If you are using **Swashbuckle** to generate a swagger spec from your .NET WEB API then please take a look at this [repo]( https://github.com/Azure/swashbuckle-resource-provider). +- If you are using **Swashbuckle** to generate a swagger spec from your .NET WEB API, then please take a look at this [repo]( https://github.com/Azure/swashbuckle-resource-provider). ## Directory Structure The structure of the directory should strictly follow these rules: -- The top level folder must be the service name +- The top-level folder must be the service name - The second level must be the API versions - The third level must be the format of the specification - The fourth level must be the specifications @@ -62,10 +62,10 @@ The structure should appear like so: └── readme.md ``` -Currently, the specifications are expected to be in Swagger JSON format +Currently, the specifications are expected to be in Swagger JSON format. ## Next steps The next step in the process after a spec is completed is to generate SDKs. Go to the [SDKs section](https://github.com/Azure/adx-documentation-pr#sdks) of the Azure Developer Experience guide for more information. --- -_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 [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments._ \ No newline at end of file +_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 [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments._