anchor.diff:  $ make fmtcheck
   ----
   
  -You can correct the formatting errors yourself or instruct the violations to be corrected automatically
  -with the following command:
  +You can correct the formatting errors yourself or instruct the violations to be corrected automatically with the following command:
   
   ----
   $ make fmt
  
positive.code: $ minishift start
  ----
  
  This command will run Minishift from _$GOPATH/bin/minishift_, if you set up your Go
  workspace as described in the link:#creating-the-go-workspace[Creating the Go workspace] section.
  
  You can also execute the binaries directly from the _out_ directory of
  the checkout. Depending on your operating system, the binary is in one of the following
  directories:
  
  * _out/darwin-amd64_
  * _out/linux-amd64_
  * _out/windows-amd64_
  
  For more minishift commands and flags, see the link:../command-ref/minishift{outfilesuffix}[Minishift command reference] documentation.
  
  [[unit-tests]]
  === Running unit tests
  
negative.code: [[update-dependencies]]
  === Updating dependencies
  
  If your work requires a change to the dependencies, you need to update the Glide configuration.
  
  . Edit *_glide.yaml_* to change the dependencies as needed.
  
  . Delete *_glide.lock_*  and re-create the vendor directory by running `make vendor`.
   Glide will recognize that there is no lock file and recalculate the required dependencies.
  
  . Check-in the updated *_glide.yaml_* and *_glide.lock_*.
  
  . Test that everything still compiles with the new lock file in place: `make clean && make`.
  
  TIP: In some cases the Glide cache located under *_~/.glide/cache_* can get corrupted.
  If you seeing Glide errors during `make vendor`, you can clear the Glide cache via `glide cc`.
  
  [[build-minishift]]
  == Building Minishift
  