Cloud-provider.md

@@ -32,10 +32,11 @@ Next you'll create 2 users accounts, one that will manage the infrastructure and
    `variable "aws_bot_access_key" { default = "AWS_ACCESS_KEY" }`  
    `variable "aws_bot_secret_key" { default = "AWS_SECRET_ACCESS_KEY" }`  
 
-5. [Create an AWS S3 bucket](https://s3.console.aws.amazon.com/s3/home) in the **region you intend to launch machines**.
-    - The bucket **does not** need to have public access.
+5. [Create an AWS S3 bucket](https://s3.console.aws.amazon.com/s3/home) in the **region you intend to launch machines**.  
+    - The bucket **does not** need to have public access.  
+
     - Assign the name to `aws_bucket_name`.  
-   `variable "aws_bucket_name" { default = "your_bucket_name"}`
+   `variable "aws_bucket_name" { default = "your_bucket_name"}`  
 
 6. Next we're going to create a placeholder hosted zone to create a `reusable_delegation_set` and reusable name servers to point our domain to in later steps.  
    - Create a "placeholder" [hosted zone](https://console.aws.amazon.com/route53/v2/hostedzones#) (domain does not need to exist).  
@@ -45,9 +46,8 @@ Next you'll create 2 users accounts, one that will manage the infrastructure and
      `aws route53 create-reusable-delegation-set --caller-reference="unique" --hosted-zone-id="YOUR_ZONE_ID"`  
 
    - Finally, get the ID created from the command and place it in `envs/your_env_folder/vars.tf` assigning it to `placeholder_reusable_delegationset_id`.  
-
      `variable "placeholder_reusable_delegationset_id" { default = "ID_CREATED_FROM_COMMAND" }`
-     
+
 Now a placeholder hosted zone with 4 nameservers will be "saved" in route53 that we can point any domain in our registrars to (which is covered in the [next step](domain)) and not worry about changing them again. Its rather convoluted compared to digital oceans `ns1.digitalocean.com...` convention but it gets the job done.  
 
 7. Continue onto [Remote backend](#remote-backend-optional) or [Domain](domain).