refactor: formatting README (#30)

Author: tngwilkins

README.md

@@ -1,13 +1,13 @@
 # terraform-example-foundation
 This is an example repo showing how the CFT Terraform modules can be composed to build a secure GCP foundation.
-The supplied structure and code is intended to form a starting point for building your own foundation with pragmatic defaults you can customize to meet your own requirements. Currently, the code leverages Google Cloud Build for deployment of the Terraform from step 2 onwards.
+The supplied structure and code is intended to form a starting point for building your own foundation with pragmatic defaults you can customize to meet your own requirements. Currently, the code leverages Google Cloud Build for deployment of the Terraform from step 1 onwards.
 Cloud Build has been chosen to allow teams to quickly get started without needing to deploy a CI/CD tool, although it is worth noting the code can easily be executed by your preferred tool.
 
 ## Overview
 This repo contains several distinct Terraform projects each within their own directory that must be applied seperately, but in sequence.
 Each of these Terraform projects are to be layered on top of each other, running in the following order.
 
-### 0. [bootstrap](./0-bootstrap/README.md)
+### [0. bootstrap](./0-bootstrap/)
 
 This stage executes the [CFT Bootstrap module](https://github.com/terraform-google-modules/terraform-google-bootstrap) which bootstraps an existing GCP organization, creating all the required GCP resources & permissions to start using the Cloud Foundation Toolkit (CFT).
 This includes; projects, service accounts and a Terraform state bucket. After executing this step, you will have the following structure:
@@ -22,7 +22,7 @@ In addition, this step uses the optional Cloud Build submodule, which sets up Cl
 A simple trigger mechanism is configured, which runs a `terraform plan` for any non master branch and `terraform apply` when changes are merged to the master branch.
 Usage instructions are available in the bootstrap [README](./0-bootstrap/README.md).
 
-### 1. [org](./1-org/README.md)
+### [1. org](./1-org/)
 
 The purpose of this stage is to set up top level folders used to house projects which contain shared resources such as monitoring, networking, org level logging and also to set baseline security settings through organizational policy.
 This will create the following folder & project structure:
@@ -40,6 +40,7 @@ example-organization
         ├── org-shared-vpc-nonprod
         └── org-shared-vpc-prod
 ```
+
 #### Logs
 
 Under the logs folder, two projects are created. One for organization wide audit logs and another for billing logs.
@@ -59,15 +60,15 @@ If you have strong IAM requirements for these monitoring workspaces, it is worth
 Under the networking folder, a project is created per environment (prod & nonprod) which is intended to be used as a [Shared VPC Host project](https://cloud.google.com/vpc/docs/shared-vpc) for all projects in that environment.
 This stage only creates the projects and enables the correct APIs, the following networks stage creates the actual Shared VPC networks.
 
-#### Organization policy
+#### Organization Policies
 
 Finally, the this step also applies a number of baseline [Organizational Policies](https://cloud.google.com/resource-manager/docs/organization-policy/overview).
 It is important to understand what restrictions these policies are applying within your GCP organization, so please take the time to review and update these restrictions to meet your own requirements.
 A full list of policies is [available here](https://cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints).
 
 Usage instructions are available for the org step in the [README](./1-org/README.md).
 
-### 2. [networks](./2-networks/README.md)
+### [2. networks](./2-networks/)
 
 This step focuses on creating a Shared VPC per environment (prod & nonprod) in a standard configuration with a reasonable security baseline. Currently this includes:
 
@@ -83,7 +84,7 @@ This step focuses on creating a Shared VPC per environment (prod & nonprod) in a
 
 Usage instructions are available for the network step in the [README](./2-networks/README.md).
 
-### 3. [projects](./3-projects/README.md)
+### [3. projects](./3-projects/)
 
 This step, is focused on creating service projects in a standard configuration that are attached to the Shared VPC created in the previous step.
 Running this code as-is should generate a structure as shown below:
@@ -104,7 +105,7 @@ If relevant for your use case, there are also two optional submodules which can
 
 Usage instructions are available for the network step in the [README](./3-projects/README.md).
 
-### Final view
+### Final View
 
 Once all steps above have been executed your GCP organization should represent the structure shown below, with projects being the lowest nodes in the tree.