anchor.diff:  invoked by the OpenShift STI image builder and it could be a simple Bash script
   or a static Go binary.
   
  -Because the *_test/run_* script performs the STI build, you must have the STI
  -binary available on your system. See the STI
  -https://github.com/openshift/source-to-image/blob/master/README.md#installation[README]
  -file and follow the installation instructions if required.
  -
  -Because STI puts together the application source code and Docker image, to test
  -it you need a sample application source you can use during the test to verify
  -that the application source is successfully converted into a Docker image. The
  -sample application should be simple, but it should also exercise the `assemble`
  -command.
  -
  -== Using `sti create`
  +The *_test/run_* script performs the STI build, so you must have the STI binary
  +available on your system. If required, follow the installation instructions in
  +the STI
  +https://github.com/openshift/source-to-image/blob/master/README.md#installation[README].
  +
  +STI combines the application source code and Docker image, so in order to test
  +it you need a sample application source to verify that the source successfully
  +converts into a Docker image. The sample application should be simple, but it
  +should also exercise the `assemble` command.
  +
  +== Generating Scripts and Tools
   The STI tooling comes with powerful generation tools to speed up the process of
  -creating a new STI image. The
  -https://github.com/openshift/source-to-image/blob/master/docs/cli.md#sti-create[`sti
  -create` command] produces all necessary STI scripts and testing tools along with
  -the *_Makefile_*. The generated *_test/run_* script must be adjusted to be
  +creating a new STI image. The `sti create` command produces all necessary STI
  +scripts and testing tools along with the *_Makefile_*:
  +****
  +`$ sti create _<image name>_ _<destination directory>_`
  +****
  +
  +The generated *_test/run_* script must be adjusted to be
   useful, but it provides a good starting point to begin developing.
   
  -NOTE: The *_test/run_* script produced by the `sti create` command requires that the sample application sources are inside the *_test/test-app_* directory.
  +[NOTE]
  +====
  +The *_test/run_* script produced by the `sti create` command requires that the sample application sources are inside the *_test/test-app_* directory.
  +====
   
   == Testing Locally
   The easiest way to run the STI image tests locally is to use the generated
  
positive.code: ====
  
  [options="nowrap"]
  ----
  $ sti build file:///path-to-sample-app BUILDER_IMAGE_NAME OUTPUT_APPLICATION_IMAGE_NAME
  ----
  ====
  
  . If you support *_save-artifacts_*, execute step 2 again to verify that restoring artifacts works properly.
  
  . Run the container:
  +
  ====
  
  ----
  $ docker run OUTPUT_APPLICATION_IMAGE_NAME
  ----
  ====
  
  . Verify the container is running and the application is responding.
  
negative.code: +
  ====
  
  ****
  `$ docker run _<BUILDER_IMAGE_NAME>_`
  ****
  ====
  
  . Build the image:
  