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: [[update-dependencies]]
  === Updating dependencies
  
  If your work requires a change to the dependencies, you need to incorporate the updated
  information to the Glide files.
  
  . Edit the _glide.yaml_ file to change the dependency list as needed.
  
  . Delete the _glide.lock_ file and re-create the vendor directory by link:#bootstrap-dependencies[bootstrapping] it. Glide will recognize
  that there is no lock file and recalculate the required dependencies.
  
  . Check-in the updated _glide.lock_ file and the updated _glide.yaml_.
  
  . Test that everything still compiles with the new lock file in place.
  
  [[build-minishift]]
  == Building Minishift
  
negative.code: [[integration-tests]]
  === Running integration tests
  
  Integration tests utilize https://github.com/DATA-DOG/godog[`godog`], which uses Gherkin (Cucumber) to define test cases.
  The test cases are defined in *_test/integration/+*+.feature_*.
  Per default, the tests are executed against the binary created by `make build`, that is *_$GOPATH/bin/minishift_*.
  To run the tests, run:
  
  ----
  $ make integration
  ----
  
  To run integration tests against a Minishift binary in a different location you can use the `MINISHIFT_BINARY` argument:
  
  ----
  $ make integration MINISHIFT_BINARY=<path-to-custom-binary>
  ----
  
  Additional properties for Godog runner can be specified with `GODOG_OPTS` argument.
  The following options are available:
  
  - `tags`: Use `tags` to ensure that scenarios and features containing at least one of the selected tags are executed.
  