Update README.md

Author: anthony-c-martin

generator/README.md

@@ -31,11 +31,12 @@ View the Pipeline Configuration [here](/azure-pipelines-autogen.yml).
 2. Create a Pull Request from [`autogenerate`](https://github.com/Azure/azure-resource-manager-schemas/tree/autogenerate) to [`master`](https://github.com/Azure/azure-resource-manager-schemas/tree/master).
 3. If there are any modifications to [schemas/common/autogeneratedResources.json](/schemas/common/autogeneratedResources.json), push a commit to the autogenerate branch to make any corresponding changes to [schemas/2014-04-01-preview/deploymentTemplate.json](/schemas/2014-04-01-preview/deploymentTemplate.json) and [schemas/2015-01-01/deploymentTemplate.json](/schemas/2015-01-01/deploymentTemplate.json).
 
-#### Onboarding teams to autogeneration pipeline
-
-1. Run `npm run list-basepaths` to discover the specs repo path containing the swagger definitions.
-1. Run `npm run generate-single {basePath}` to generate schemas for them. Save the console output to file.
-1. Remove all references to the provider namespace from [schemas/2019-04-01/deploymentTemplate.json](/schemas/2019-04-01/deploymentTemplate.json).
-1. Add the {basePath} to the autogenlist array in [autogenlist.ts](./autogenlist.ts).
-1. Commit all the changed files, and submit a PR to this repo with title "Onboarding {provider} for autogeneration". Include the full output saved in step 2 as a comment.
-1. Ensure all CI tests pass, and ask the team to review the PR (including tool output) to ensure that all expected resources have been detected and generated as expected.
+#### Onboarding to the autogeneration pipeline
+
+1. Follow the steps listed under [Getting Started](#getting-started). The following commands assume you are running in the `generator` directory.
+3. Run `npm run list-basepaths` to discover the specs repo path containing the swagger definitions.
+4. Run `npm run generate-single {basePath}` to generate schemas for them. Save the console output to file.
+5. Manually remove any existing references to your provider namespace (if any) from [schemas/2019-04-01/deploymentTemplate.json](/schemas/2019-04-01/deploymentTemplate.json).
+6. Add the {basePath} to the autogenlist array in [autogenlist.ts](./autogenlist.ts).
+7. Commit all the changed files, and submit a PR to this repo with title "Onboarding {provider} for autogeneration". Include the full output saved in step 2 as a comment.
+8. Ensure all CI tests pass, and ask the team to review the PR (including tool output) to ensure that all expected resources have been detected and generated as expected.