anchor.diff:  
   [NOTE]
   ====
  -Any `*BuildConfig*` objects created as part of `new-app` processing will not be updated with
  +Any `BuildConfig` objects created as part of `new-app` processing will not be updated with
   environment variables passed via the `-e|--env` or `--env-file` argument.
   ====
   
  
positive.code:         supports: "ruby:2.0,ruby"
          version: "2.0"
  ----
  <1> Including *builder* here ensures this `*ImageStreamTag*` appears in the
  web console as a builder.
  ====
  
  
negative.code: 
  |Object |Description
  
  a|`BuildConfig`
  a|A `BuildConfig` is created for each source repository specified in the
  command line. The `BuildConfig` specifies the strategy to use, the source
  location, and the build output location.
  
  a|`ImageStreams`
  a|For `BuildConfig`, two `ImageStreams` are usually created: one to
  represent the input image (the builder image in the case of `Source` builds or
  *FROM* image in case of `Docker` builds), and another one to represent the
  output image. If a container image was specified as input to `new-app`, then an
  image stream is created for that image as well.
  
  a|`DeploymentConfig`
  a|A `DeploymentConfig` is created either to deploy the output of a build, or a
  specified image. The `new-app` command creates xref:../volumes.adoc#dev-guide-volumes[*EmptyDir*
  volumes] for all Docker volumes that are specified in containers included in the
  resulting `DeploymentConfig`.
  
  a|`Service`
  a|The `new-app` command attempts to detect exposed ports in input images. It
  uses the lowest numeric exposed port to generate a service that exposes that
  port. In order to expose a different port, after `new-app` has completed, simply
  