anchor.diff:  Builds can be manually invoked using the following command:
   
   ****
  -`$ osc start-build [replaceable]#<buildConfigID>#`
  +`$ osc start-build _<buildConfigID>_`
   ****
   
   They can also be re-run using the `--from-build` flag:
   
   ****
  -`$ osc start-build --from-build=[replaceable]#<buildID>#`
  +`$ osc start-build --from-build=_<buildID>_`
   ****
   
   If the `--follow` flag is specified, the build's logs will be streamed in stdout.
   
   ****
  -`$ osc start-build [replaceable]#<buildConfigID># --follow`
  +`$ osc start-build _<buildConfigID>_ --follow`
   ****
   
   == Canceling a Build
   Builds can be manually canceled using the following command:
   
   ****
  -`$ osc cancel-build [replaceable]#<buildID>#`
  +`$ osc cancel-build _<buildID>_`
   ****
   
   == Accessing Build Logs
   Builds allow access to their logs using following command:
   
   ****
  -`$ osc build-logs [replaceable]#<buildID>#`
  +`$ osc build-logs _<buildID>_`
   ****
   
   == Source Code
  
positive.code: 
  ====
  +
  This defines the image repository that is tied to a Docker image repository located at `[replaceable]#<system-registry>#/[replaceable]#<namespace>#/ruby-20-centos7`.
  The `[replaceable]#<system-registry>#` is defined as a service with the name `docker-registry` running in OpenShift.
  
  . Next, define a build with a strategy that consumes some upstream image; for example:
  +
  
negative.code: command (see link:#describe-buildconfig[below]), and is displayed similar to the following:
  
  ****
  `http://_<openshift_api_host:port>_/osapi/v1beta1/buildConfigHooks/_<build-name>_/_<secret>_/github?namespace=_<namespace>_`
  ****
  
  *Generic Webhooks*
  