anchor.diff:  
   [#custom-build]
   == Custom Build
  -Custom builds are the most sophisticated version of builds, allowing developers to define a builder image which is responsible for the entire process of the build. The custom builder image is a plain Docker image within which the author embeds the logic of the desired build process, such as building RPMs or building
  -base Docker images.
  +Custom builds allow developers to define the builder image that is responsible
  +for the entire process of the build. The custom builder image is a plain Docker
  +image were the author embeds the logic of the desired build process, such as
  +building RPMs or building base Docker images.
   
   [#using-docker-credentials-for-pushing-and-pulling-images]
   == Using Docker Credentials for Pushing and Pulling Images
   
  -In case you want to push the output image into a private Docker Registry or pull
  -the builder image from the private Docker Registry that requires authentication
  -or Docker Hub, you have to supply the `.dockercfg` file with valid Docker
  +In order to push the output image into a private Docker Registry or pull the
  +builder image from the private Docker Registry that requires authentication or
  +Docker Hub, supply the `.dockercfg` file with valid Docker
   Registry credentials.
   
   The *_.dockercfg_* JSON file usually exists in your home directory and has
  
positive.code: ----
  ====
  
  Once that's done you're going to get two files: one containing your public key (as
  explained above) and one containing a corresponding private key (one of `id_dsa`, `id_ecdsa`,
  `id_ed25519` or `id_rsa`). With both of these in place you should consult your
  source control management (SCM) system's manual on how to upload the public key.
  The private one will be used to access your private repository.
  
  Kubernetes provides the
  https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/design/secrets.md[Secret]
  resource, which you can use to store your keys. You must create the `*Secret*` first
  before builds can use your ssh key for accessing your private repository.
  The `*data*` field for the `*Secret*` object must contain your private key
  with the value set to the base64-encoded content of that file. For example:
  
  ====
  
  
negative.code: `Output` section inside the `BuildConfig` and set it to the name of the
  `*Secret*` that you created, in this case `*dockerhub*`.
  
  ====
  ----
  "parameters": {
    "output": {
      "to": {
  