Fixing cfg docs for better presentation on godoc.org
diff --git a/cfg/cfg.go b/cfg/cfg.go
index 6204bad..b491b49 100644
--- a/cfg/cfg.go
+++ b/cfg/cfg.go
@@ -30,29 +30,30 @@
 //       version: ^1.0.0
 //
 // These elements are:
-// - package: The top level package is the location in the GOPATH. This is used
-//   for things such as making sure an import isn't also importing the top level
-//   package.
-// - homepage: To find the place where you can find details about the package or
-//   applications. For example, http://k8s.io
-// - license: The license is either an SPDX license string or the filepath to the
-//   license. This allows automation and consumers to easily identify the license.
-// - owners: The owners is a list of one or more owners for the project. This
-//   can be a person or organization and is useful for things like notifying the
-//   owners of a security issue without filing a public bug.
-// - ignore: A list of packages for Glide to ignore importing. These are package
-//   names to ignore rather than directories.
-// - import: A list of packages to import. Each package can include:
-//     - package: The name of the package to import and the only non-optional item.
-//     - version: A semantic version, semantic version range, branch, tag, or
-//       commit id to use.
-//     - repo: If the package name isn't the repo location or this is a private
-//       repository it can go here. The package will be checked out from the
-//       repo and put where the package name specifies. This allows using forks.
-//     - vcs: A VCS to use such as git, hg, bzr, or svn. This is only needed
-//       when the type cannot be detected from the name. For example, a repo
-//       ending in .git or on GitHub can be detected to be Git. For a repo on
-//       Bitbucket we can contact the API to discover the type.
-// - devImport: A list of development packages. Each package has the same details
-//   as those lised under import.
+//
+//    - package: The top level package is the location in the GOPATH. This is used
+//      for things such as making sure an import isn't also importing the top level
+//      package.
+//    - homepage: To find the place where you can find details about the package or
+//      applications. For example, http://k8s.io
+//    - license: The license is either an SPDX license string or the filepath to the
+//      license. This allows automation and consumers to easily identify the license.
+//    - owners: The owners is a list of one or more owners for the project. This
+//      can be a person or organization and is useful for things like notifying the
+//      owners of a security issue without filing a public bug.
+//    - ignore: A list of packages for Glide to ignore importing. These are package
+//      names to ignore rather than directories.
+//    - import: A list of packages to import. Each package can include:
+//        - package: The name of the package to import and the only non-optional item.
+//        - version: A semantic version, semantic version range, branch, tag, or
+//          commit id to use.
+//        - repo: If the package name isn't the repo location or this is a private
+//          repository it can go here. The package will be checked out from the
+//          repo and put where the package name specifies. This allows using forks.
+//        - vcs: A VCS to use such as git, hg, bzr, or svn. This is only needed
+//          when the type cannot be detected from the name. For example, a repo
+//          ending in .git or on GitHub can be detected to be Git. For a repo on
+//          Bitbucket we can contact the API to discover the type.
+//    - devImport: A list of development packages. Each package has the same details
+//      as those lised under import.
 package cfg