Make markdownlint happy about whitespace

Use "make mdlint" to check current status

CHANGELOG.md

 # Minikube Release Notes
 
-# Version 1.1.1 - 2019-06-07
+## Version 1.1.1 - 2019-06-07
 
 * Upgrade to kubernetes 1.14.3 [#4444](https://github.com/kubernetes/minikube/pull/4444)
 * fix ShowDriverDeprecationNotification config setting [#4431](https://github.com/kubernetes/minikube/pull/4431)
@@ -27,7 +27,8 @@
 * Get current profile if no arguments given [#4335](https://github.com/kubernetes/minikube/pull/4335)
 * Skip kvm network deletion if private network doesn't exist [#4331](https://github.com/kubernetes/minikube/pull/4331)
 
-Huge thank you for this release towards our contributors: 
+Huge thank you for this release towards our contributors:
+
 - Abdulla Bin Mustaqeem
 - Anders Björklund
 - Andy Daniels
@@ -169,6 +170,7 @@ Thank you to the contributors whose work made v1.1 into something we could all b
 * ```#compdef``` must be the first line [#4015](https://github.com/kubernetes/minikube/pull/4015)
 
 Huge thank you for this release towards our contributors:
+
 - Abdulla Bin Mustaqeem
 - Anders F Björklund
 - Andy Daniels

docs/configuring_kubernetes.md

@@ -5,14 +5,13 @@ To use this feature, you can use the `--extra-config` flag on the `minikube star
 
 This flag is repeated, so you can pass it several times with several different values to set multiple options.
 
-
 ## Selecting a Kubernetes version
 
 minikube defaults to the latest stable version of Kubernetes. You may select a different Kubernetes release by using the `--kubernetes-version` flag, for example:
 
   `minikube start --kubernetes-version=v1.10.13`
- 
-minikube follows the [Kubernetes Version and Version Skew Support Policy](https://kubernetes.io/docs/setup/version-skew-policy/), so we guarantee support for the latest build for the last 3 minor Kubernetes releases. When practical, minikube extends this policy two additional minor releases so that users can emulate legacy environments. 
+
+minikube follows the [Kubernetes Version and Version Skew Support Policy](https://kubernetes.io/docs/setup/version-skew-policy/), so we guarantee support for the latest build for the last 3 minor Kubernetes releases. When practical, minikube extends this policy two additional minor releases so that users can emulate legacy environments.
 
 As of April 2019, this means that minikube supports and actively tests against the latest builds of:
 

docs/contributors/releasing_minikube.md

@@ -96,7 +96,7 @@ Verify release checksums by running`make check-release`
 
 ## Update minikube frontpage
 
-We document the last 3 releases on our frontpage. Please add it to the list: https://github.com/kubernetes/minikube/blob/master/README.md
+We document the last 3 releases on our frontpage. Please add it to the list: <https://github.com/kubernetes/minikube/blob/master/README.md>
 
 ## Update official Kubernetes docs
 

docs/contributors/roadmap.md

@@ -21,7 +21,7 @@ Please send a PR to suggest any improvements to it.
 ## (#3) Cross-platform
 
 - [ ] Users should never need to separately install supporting binaries [#3975](https://github.com/kubernetes/minikube/issues/3975) [#4391](https://github.com/kubernetes/minikube/issues/4391)
-- [ ] Simplified installation process across all supported platforms 
+- [ ] Simplified installation process across all supported platforms
 
 ## (#4) Support all Kubernetes features
 

docs/drivers.md

@@ -29,7 +29,6 @@ Check your installed virsh version:
 
 If your version of virsh is newer than 1.3.1 (January 2016), you may download our pre-built driver:
 
-
 ```shell
 curl -LO https://storage.googleapis.com/minikube/releases/latest/docker-machine-driver-kvm2 \
   && sudo install docker-machine-driver-kvm2 /usr/local/bin/
@@ -37,12 +36,13 @@ curl -LO https://storage.googleapis.com/minikube/releases/latest/docker-machine-
 
 If your version of virsh is older than 1.3.1 (Januarry 2016), you may build your own driver binary if you have go 1.12+ installed.
 
-```shell
+```console
 $ sudo apt install libvirt-dev
 $ git clone https://github.com/kubernetes/minikube.git
 $ cd minikube
 $ make out/docker-machine-driver-kvm2
 $ sudo install out/docker-machine-driver-kvm2 /usr/local/bin
+$
 ```
 
 To finish the kvm installation, start and verify the `libvirtd` service
@@ -191,7 +191,7 @@ and run minikube as usual:
 minikube start
 ```
 
-# Troubleshooting
+## Troubleshooting
 
 minikube is currently unable to display the error message received back from the VM driver. Users can however reveal the error by passing `--alsologtostderr -v=8` to `minikube start`. For instance:
 
@@ -201,8 +201,8 @@ minikube start --vm-driver=kvm2 --alsologtostderr -v=8
 
 Output:
 
-```
+```text
 Found binary path at /usr/local/bin/docker-machine-driver-kvm2
 Launching plugin server for driver kvm2
-Error starting plugin binary: fork/exec /usr/local/bin/docker-machine-driver-kvm2: exec format error   
+Error starting plugin binary: fork/exec /usr/local/bin/docker-machine-driver-kvm2: exec format error
 ```

docs/http_proxy.md

@@ -44,7 +44,6 @@ To set these environment variables permanently, consider adding these to your [s
 
 As of v1.0, minikube automatically configures the Docker instance inside of the VM to use the proxy environment variables, unless you have specified a `--docker-env` override. If you need to manually configure Docker for a set of proxies, use:
 
-
 ```shell
 minikube start \
   --docker-env=HTTP_PROXY=$HTTP_PROXY \

docs/networking.md

@@ -22,7 +22,6 @@ We also have a shortcut for fetching the minikube IP and a service's `NodePort`:
 
 `minikube service --url $SERVICE`
 
-
 ### Increasing the NodePort range
 
 By default, minikube only exposes ports 30000-32767. If this is not enough, you can configure the apiserver to allow all ports using:
@@ -31,7 +30,6 @@ By default, minikube only exposes ports 30000-32767. If this is not enough, you
 
 This flag also accepts a comma separated list of ports and port ranges.
 
-
 ## Access to LoadBalancer services using `minikube tunnel`
 
 Services of type `LoadBalancer` can be exposed via the `minikube tunnel` command.
@@ -77,5 +75,4 @@ minikube tunnel --cleanup
 
 If you want to avoid entering the root password, consider setting NOPASSWD for "ip" and "route" commands:
 
-https://superuser.com/questions/1328452/sudoers-nopasswd-for-single-executable-but-allowing-others
-
+<https://superuser.com/questions/1328452/sudoers-nopasswd-for-single-executable-but-allowing-others>

docs/offline.md

@@ -18,7 +18,7 @@ As of v1.0, `minikube start` is offline compatible out of the box. Here are some
 For offline use on other hosts, one can copy the contents of `~/.minikube/cache`. As of the v1.0 release, this directory
 contains 685MB of data:
 
-```
+```text
 cache/iso/minikube-v1.0.0.iso
 cache/images/gcr.io/k8s-minikube/storage-provisioner_v1.8.1
 cache/images/k8s.gcr.io/k8s-dns-sidecar-amd64_1.14.13
@@ -38,5 +38,3 @@ cache/v1.14.0/kubelet
 ```
 
 If any of these files exist, minikube will use copy them into the VM directly rather than pulling them from the internet.
-
-

docs/syncing-files.md

@@ -6,8 +6,7 @@ As soon as a VM is created, minikube will populate the root filesystem with any
 
 For example, running the following commands will result in `/etc/OMG` being added with the contents of `hello` into the minikube VM:
 
-
-```
+```shell
 mkdir -p ~/.minikube/files/etc
 echo hello > ~/.minikube/files/etc/OMG
 minikube start