make improvements from PR feedback

Co-authored-by: George L. Yermulnik <[email protected]>

README.md

@@ -551,16 +551,16 @@ Example:
 
     **Warning:** If you use Terraform workspaces, DO NOT use this workaround ([details](https://github.com/antonbabenko/pre-commit-terraform/issues/203#issuecomment-918791847)). Wait to [`force-init`](https://github.com/antonbabenko/pre-commit-terraform/issues/224) option implementation.
 
-5. `terraform_validate` in a 0.15+ module with configuration_aliases errors out
+5. `terraform_validate` in a repo with Terraform module, written using Terraform 0.15+ and which uses provider `configuration_aliases` ([Provider Aliases Within Modules](https://www.terraform.io/language/modules/develop/providers#provider-aliases-within-modules)), errors out.
 
-   When running the hook where you have configuration_aliases defined as required in the terraform block, terraform will throw an error like:
+   When running the hook against Terraform code where you have provider `configuration_aliases` defined in a `required_providers` configuration block, terraform will throw an error like:
    >
    >
    > Error: Provider configuration not present
    > To work with <resource> its original provider configuration at provider["registry.terraform.io/hashicorp/aws"].<provider_alias> is required, but it has been removed. This occurs when a provider configuration is removed while
    > objects created by that provider still exist in the state. Re-add the provider configuration to destroy <resource>, after which you can remove the provider configuration again.
 
-   This is a [known issue](https://github.com/hashicorp/terraform/issues/28490) with Terraform and how providers are initialized in 0.15 and later. To work around this for now you can add an exclude to the `terraform_validate` hook like this:
+   This is a [known issue](https://github.com/hashicorp/terraform/issues/28490) with Terraform and how providers are initialized in Terraform 0.15 and later. To work around this you can add an `exclude` parameter to the configuration of `terraform_validate` hook like this:
    ```yaml
    - id: terraform_validate
      exclude: [^/].+$
@@ -581,20 +581,23 @@ Example:
    ' | tee aliased-providers.tf.json
    ```
 
-   Save this as .generate-providers.sh in the root of your repository and place it in the and add a hook to run that first, like so:
+   Save it as `.generate-providers.sh` in the root of your repository and add a `pre-commit` hook to run it before all other hooks, like so:
    ```yaml
-   - repo: local
-     hooks:
-       - id: generate-terraform-providers
-          name: generate-terraform-providers
-          require_serial: true
-          entry: .generate-providers.sh
-          language: script
-          files: (\.tf|\.tfvars)$
-          pass_filenames: false
+   - repos:
+     - repo: local
+       hooks:
+         - id: generate-terraform-providers
+            name: generate-terraform-providers
+            require_serial: true
+            entry: .generate-providers.sh
+            language: script
+            files: (\.tf|\.tfvars)$
+            pass_filenames: false
+     - repo: https://github.com/pre-commit/pre-commit-hooks
+   [...]
    ```
 
-   **Note:** This latter method will leave an "aliased-providers.tf.json" file in your path. You will either want to automate a way to clean this up or add it to your gitignore or both.
+   **Note:** The latter method will leave an "aliased-providers.tf.json" file in your repo. You will either want to automate a way to clean this up or add it to your `.gitignore` or both.
 
 ### terrascan