docs: fix hcl use on production acls guide (#6739)

Also clean up some general whitespace formatting.

website/source/docs/guides/production-acls.html.md

@@ -45,8 +45,8 @@ on them when you apply the token.
 # agent.hcl 
 {
   acl = {
-  	enabled = true, 
-  	default_policy = "deny",
+    enabled = true
+    default_policy = "deny"
     enable_token_persistence = true
   }
 }
@@ -270,7 +270,7 @@ Finally, add the token to the service definition.
       "timeout": "1s"
     }
   }
- } 
+}
 ```
 
 If the service is running, you will need to restart it. Unlike with agent 
@@ -337,9 +337,8 @@ The data file must contain a valid token.
 ``` 
 # dns-token.json
 {
-  "Token":"5467d69a-5f19-469b-0543-12a487eecc66" 
+  "Token": "5467d69a-5f19-469b-0543-12a487eecc66"
 }
-
 ``` 
 
 Note, if you have multiple agents serving DNS requests you can use the same
@@ -444,13 +443,13 @@ not even to view the token you used to access the UI.
 # operator-ui.hcl
 service_prefix "" {
   policy = "read"
-  } 
+}
 key_prefix "" {
   policy = "read"
-  }
+}
 node_prefix "" {
   policy = "read"
-  }
+}
 ```
 
 ## Summary