Run gendocs

docs/user-guide/kubeconfig-file.md

@@ -30,12 +30,15 @@ Documentation for other releases can be found at
 <!-- END STRIP_FOR_RELEASE -->
 
 <!-- END MUNGE: UNVERSIONED_WARNING -->
+
 # kubeconfig files
+
 In order to easily switch between multiple clusters, a kubeconfig file was defined.  This file contains a series of authentication mechanisms and cluster connection information associated with nicknames.  It also introduces the concept of a tuple of authentication information (user) and cluster connection information called a context that is also associated with a nickname.
 
 Multiple kubeconfig files are allowed.  At runtime they are loaded and merged together along with override options specified from the command line (see rules below).
 
 ## Related discussion
+
 https://github.com/GoogleCloudPlatform/kubernetes/issues/1755
 
 ## Example kubeconfig file
@@ -81,6 +84,7 @@ users:
 ```
 
 ## Loading and merging rules
+
 The rules for loading and merging the kubeconfig files are straightforward, but there are a lot of them.  The final config is built in this order:
   1.  Get the kubeconfig  from disk.  This is done with the following hierarchy and merge rules:
 
@@ -115,6 +119,7 @@ The rules for loading and merging the kubeconfig files are straightforward, but
   1.  For any information still missing, use default values and potentially prompt for authentication information
 
 ## Manipulation of kubeconfig via `kubectl config <subcommand>`
+
 In order to more easily manipulate kubeconfig files, there are a series of subcommands to `kubectl config` to help.
 See [kubectl/kubectl_config.md](kubectl/kubectl_config.md) for help.