Reverted markdown and whitespace fixes. Moving to different PR.

README.md

@@ -2,22 +2,26 @@
 
 # Example infrastructure-modules for Terragrunt
 
-This repo, along with the [terragrunt-infrastructure-live-example
+This repo, along with the [terragrunt-infrastructure-live-example 
 repo](https://github.com/gruntwork-io/terragrunt-infrastructure-live-example), show an example file/folder structure
-you can use with [Terragrunt](https://github.com/gruntwork-io/terragrunt) to keep your
+you can use with [Terragrunt](https://github.com/gruntwork-io/terragrunt) to keep your 
 [Terraform](https://www.terraform.io) code DRY. For background information, check out the [Keep your Terraform code
 DRY](https://github.com/gruntwork-io/terragrunt#keep-your-terraform-code-dry) section of the Terragrunt documentation.
 
 This repo contains the following example code:
 
-* [asg-elb-service](/asg-elb-service): An example of how to deploy an Auto Scaling Group (ASG) with an Elastic Load
+* [asg-elb-service](/asg-elb-service): An example of how to deploy an Auto Scaling Group (ASG) with an Elastic Load 
   Balancer (ELB) in front of it. We run a dirt-simple "web server" on top of the ASG that always returns "Hello, World".
 
-* [mysql](/mysql): An example of how to deploy MySQL on top of Amazon's Relational Database Service (RDS).
+* [mysql](/mysql): An example of how to deploy MySQL on top of Amazon's Relational Database Service (RDS).  
 
-Note: This code is solely for demonstration purposes. This is not production-ready code, so use at your own risk. If
+Note: This code is solely for demonstration purposes. This is not production-ready code, so use at your own risk. If 
 you are interested in battle-tested, production-ready Terraform code, check out [Gruntwork](http://www.gruntwork.io/).
 
+
+
+
+
 ## How do you use these modules?
 
 To use a module, create a  `terragrunt.hcl` file that specifies the module you want to use as well as values for the
@@ -36,14 +40,14 @@ inputs = {
 }
 ```
 
-(*Note: the double slash (`//`) in the `source` URL is intentional and required. It's part of Terraform's Git syntax
+(*Note: the double slash (`//`) in the `source` URL is intentional and required. It's part of Terraform's Git syntax 
 for [module sources](https://www.terraform.io/docs/modules/sources.html).*)
 
-You then run [Terragrunt](https://github.com/gruntwork-io/terragrunt), and it will download the source code specified
-in the `source` URL into a temporary folder, copy your `terragrunt.hcl` file into that folder, and run your Terraform
-command in that folder:
+You then run [Terragrunt](https://github.com/gruntwork-io/terragrunt), and it will download the source code specified 
+in the `source` URL into a temporary folder, copy your `terragrunt.hcl` file into that folder, and run your Terraform 
+command in that folder: 
 
-```text
+```
 > terragrunt apply
 [terragrunt] Reading Terragrunt config file at terragrunt.hcl
 [terragrunt] Downloading Terraform configurations from git::[email protected]:gruntwork-io/terragrunt-infrastructure-modules-example.git//path/to/module?ref=v0.0.1
@@ -52,27 +56,33 @@ command in that folder:
 [...]
 ```
 
-Check out the [terragrunt-infrastructure-live-example
-repo](https://github.com/gruntwork-io/terragrunt-infrastructure-live-example) for examples and the [Keep your Terraform
+Check out the [terragrunt-infrastructure-live-example 
+repo](https://github.com/gruntwork-io/terragrunt-infrastructure-live-example) for examples and the [Keep your Terraform 
 code DRY documentation](https://github.com/gruntwork-io/terragrunt#keep-your-terraform-code-dry) for more info.
 
+
+
+
+
 ## How do you change a module?
 
+
 ### Local changes
 
 Here is how to test out changes to a module locally:
 
 1. `git clone` this repo.
 1. Update the code as necessary.
-1. Go into the folder where you have the `terragrunt.hcl` file that uses a module from this repo (preferably for a
+1. Go into the folder where you have the `terragrunt.hcl` file that uses a module from this repo (preferably for a 
    dev or staging environment!).
 1. Run `terragrunt plan --terragrunt-source <LOCAL_PATH>`, where `LOCAL_PATH` is the path to your local checkout of
-   the module code.
-1. If the plan looks good, run `terragrunt apply --terragrunt-source <LOCAL_PATH>`.
+   the module code. 
+1. If the plan looks good, run `terragrunt apply --terragrunt-source <LOCAL_PATH>`.   
 
-Using the `--terragrunt-source` parameter (or `TERRAGRUNT_SOURCE` environment variable) allows you to do rapid,
+Using the `--terragrunt-source` parameter (or `TERRAGRUNT_SOURCE` environment variable) allows you to do rapid, 
 iterative, make-a-change-and-rerun development.
 
+
 ### Releasing a new version
 
 When you're done testing the changes locally, here is how you release a new version:
@@ -83,14 +93,13 @@ When you're done testing the changes locally, here is how you release a new vers
     1. Using GitHub: Go to the [releases page](/releases) and click "Draft a new release".
     1. Using Git:
 
-    ```sh
+    ```
     git tag -a v0.0.2 -m "tag message"
     git push --follow-tags
     ```
-
 1. Now you can use the new Git tag (e.g. `v0.0.2`) in the `ref` attribute of the `source` URL in `terragrunt.hcl`.
 1. Run `terragrunt plan`.
-1. If the plan looks good, run `terragrunt apply`.
+1. If the plan looks good, run `terragrunt apply`.   
 
 ## Monorepo vs. polyrepo