anchor.diff:  
   *Generic Webhooks*
   
  -Generic webhooks can be invoked from any system capable of making a web
  -request. As with a GitHub webhook, you must specify a `*secret*` which will be
  -part of the URL, the caller must use to trigger the build. The secret ensures
  -the uniqueness of the URL, preventing others from triggering the build.
  -The following is an example trigger definition JSON within the `*BuildConfig*`:
  -
  -====
  -
  -----
  -{
  -  "type": "Generic",
  -  "generic": {
  -    "secret": "secret101"
  -  }
  -}
  +Generic webhooks can be invoked from any system capable of making a web request.
  +As with a GitHub webhook, you must specify a `*secret*` which will be part of
  +the URL, the caller must use to trigger the build. The secret ensures the
  +uniqueness of the URL, preventing others from triggering the build. The
  +following is an example trigger definition YAML within the `*BuildConfig*`:
  +
  +====
  +[source,yaml]
  +----
  +type: "Generic"
  +generic:
  +  secret: "secret101"
   ----
   ====
   
  
positive.code: process and resulting image, you can add environment variables to the
  `*dockerStrategy*` definition of the `*BuildConfig*`.
  
  The environment variables defined there are inserted as a single ENV Dockerfile
  instruction right after the FROM instruction, so that it can be referenced later
  on within the Dockerfile.
  
  The variables are defined during build and stay in the output image, therefore
  they will be present in any container that runs that image as well.
  
negative.code: === Configuration Change Triggers
  A configuration change trigger allows a build to be automatically invoked as
  soon as a new `*BuildConfig*` is created. The following is an example trigger
  definition YAML within the `*BuildConfig*`:
  
  ====
  [source,yaml]
  ----
    type: "ConfigChange"
  ----
  ====
  
  [NOTE]
  