Update kubernetes provider

website/source/docs/providers/kubernetes/index.html.markdown

@@ -16,7 +16,7 @@ Use the navigation to the left to read about the available resources.
 
 ## Example Usage
 
-```
+```hcl
 provider "kubernetes" {
   config_context_auth_info = "ops"
   config_context_cluster   = "mycluster"
@@ -58,11 +58,12 @@ Read [more about `kubectl` in the official docs](https://kubernetes.io/docs/user
 
 The other way is **statically** define all the credentials:
 
-```
+```hcl
 provider "kubernetes" {
   host     = "https://104.196.242.174"
   username = "ClusterMaster"
   password = "MindTheGap"
+
   client_certificate     = "${file("~/.kube/client-cert.pem")}"
   client_key             = "${file("~/.kube/client-key.pem")}"
   cluster_ca_certificate = "${file("~/.kube/cluster-ca-cert.pem")}"

website/source/docs/providers/kubernetes/r/config_map.html.markdown

@@ -13,11 +13,12 @@ Config Map can be used to store fine-grained information like individual propert
 
 ## Example Usage
 
-```
+```hcl
 resource "kubernetes_config_map" "example" {
   metadata {
     name = "my-config"
   }
+
   data {
     api_host = "myhost:443"
     db_host  = "dbhost:5432"

website/source/docs/providers/kubernetes/r/namespace.html.markdown

@@ -13,15 +13,17 @@ Read more about namespaces at https://kubernetes.io/docs/user-guide/namespaces/
 
 ## Example Usage
 
-```
+```hcl
 resource "kubernetes_namespace" "example" {
   metadata {
     annotations {
       name = "example-annotation"
     }
+
     labels {
       mylabel = "label-value"
     }
+
     name = "TerraformExampleNamespace"
   }
 }

website/source/docs/providers/kubernetes/r/secret.html.markdown

@@ -18,7 +18,7 @@ The resource will by default create a secret which is available to any pod in th
 
 ## Example Usage
 
-```
+```hcl
 resource "kubernetes_secret" "example" {
   metadata {
     name = "basic-auth"