chore: re-format docs (#1014)

Author: nfx

docs/guides/aws-workspace.md

@@ -130,7 +130,7 @@ module "vpc" {
   single_nat_gateway   = true
   create_igw           = true
 
-  public_subnets  = [cidrsubnet(var.cidr_block, 3, 0)]
+  public_subnets = [cidrsubnet(var.cidr_block, 3, 0)]
   private_subnets = [cidrsubnet(var.cidr_block, 3, 1),
   cidrsubnet(var.cidr_block, 3, 2)]
 

docs/resources/job.md

@@ -168,7 +168,7 @@ By default, all users can create and modify jobs unless an administrator [enable
 
 The `timeouts` block allows you to specify `create` and `update` timeouts if you have an `always_running` job. Please launch `TF_LOG=DEBUG terraform apply` whenever you observe timeout issues.
 
-```hcl
+```
 timeouts {
   create = "20m"
   update = "20m

docs/resources/mws_networks.md

@@ -38,7 +38,7 @@ module "vpc" {
   enable_nat_gateway   = true
   create_igw           = true
 
-  public_subnets  = [cidrsubnet(var.cidr_block, 3, 0)]
+  public_subnets = [cidrsubnet(var.cidr_block, 3, 0)]
   private_subnets = [cidrsubnet(var.cidr_block, 3, 1),
   cidrsubnet(var.cidr_block, 3, 2)]
 

docs/resources/mws_workspaces.md

@@ -228,7 +228,7 @@ In addition to all arguments above, the following attributes are exported:
 
 The `timeouts` block allows you to specify `create`, `read` and `update` timeouts. It usually takes 5-7 minutes to provision Databricks E2 Workspace and another couple of minutes for your local DNS caches to resolve. Please launch `TF_LOG=DEBUG terraform apply` whenever you observe timeout issues.
 
-```hcl
+```
 timeouts {
   create = "30m"
   read   = "10m"

docs/resources/permissions.md

@@ -116,7 +116,7 @@ resource "databricks_group" "eng" {
 }
 
 data "databricks_node_type" "smallest" {
-    local_disk = true
+  local_disk = true
 }
 
 resource "databricks_instance_pool" "this" {

docs/resources/pipeline.md

@@ -9,45 +9,45 @@ Use `databricks_pipeline` to deploy [Delta Live Tables](https://docs.databricks.
 
 ```hcl
 resource "databricks_notebook" "dlt_demo" {
-...
+  #...
 }
 
 resource "databricks_pipeline" "this" {
-    name = "Pipeline Name"
-    storage = "/test/first-pipeline"
-    configuration = {
-        key1 = "value1"
-        key2 = "value2"
-    }
+  name    = "Pipeline Name"
+  storage = "/test/first-pipeline"
+  configuration = {
+    key1 = "value1"
+    key2 = "value2"
+  }
 
-    cluster {
-        label = "default"
-        num_workers = 2
-        custom_tags = {
-            cluster_type = "default"
-        }
+  cluster {
+    label       = "default"
+    num_workers = 2
+    custom_tags = {
+      cluster_type = "default"
     }
+  }
 
-    cluster {
-        label = "maintenance"
-        num_workers = 1
-        custom_tags = {
-            cluster_type = "maintenance"
-        }
+  cluster {
+    label       = "maintenance"
+    num_workers = 1
+    custom_tags = {
+      cluster_type = "maintenance"
     }
+  }
 
-    library {
-        notebook {
-            path = databricks_notebook.dlt_demo.id
-        }
+  library {
+    notebook {
+      path = databricks_notebook.dlt_demo.id
     }
+  }
 
-    filters {
-        include = ["com.databricks.include"]
-        exclude = ["com.databricks.exclude"]
-    }
+  filters {
+    include = ["com.databricks.include"]
+    exclude = ["com.databricks.exclude"]
+  }
 
-    continuous = false
+  continuous = false
 }
 ```
 

docs/resources/sql_permissions.md

@@ -25,7 +25,7 @@ The created cluster could be referred to by providing its ID as `cluster_id` pro
 ```hcl
 resource "databricks_sql_permissions" "foo_table" {
   cluster_id = databricks_cluster.cluster_name.id
-  ...
+  #...
 }
 ```