anchor.diff:  build phases.
   <6> Additional default environment variable that will be added to
   every build.
  -<7> Labels to be applied to every image built. Users can override these in their `*BuildConfig*`.
  -<8> Build pods will only run on nodes with the `*key1=value2*` and `*key2=value2*` labels.
  -    Users can define a different set of `*nodeSelectors*` for their builds in which case these
  +<7> Labels to be applied to every image built. Users can override these in their `BuildConfig`.
  +<8> Build pods will only run on nodes with the `key1=value2` and `key2=value2` labels.
  +    Users can define a different set of `nodeSelectors` for their builds in which case these
       values will be ignored.
   <9> Build pods will have these annotations added to them.
  -<10> Sets the default resources to the build pod if the `*BuildConfig*` doesn't have related resource defined.
  -
  -====
  -
  -Restart the master service for the changes to take effect:
  -
  -====
  +<10> Sets the default resources to the build pod if the `BuildConfig` does not have related resource defined.
  +
  +====
  +
  +. Restart the master service for the changes to take effect:
  ++
   ----
   # systemctl restart atomic-openshift-master
   ----
  -====
   
   [[setting-global-build-overrides]]
   == Setting Global Build Overrides
   
  -To configure the `*BuildOverrides*` plug-in, add a configuration for it in the
  +To configure the `BuildOverrides` plug-in:
  +
  +. Add a configuration for it in the
   *_/etc/origin/master/master-config.yaml_* file on masters:
  -
  ++
   ====
   [source,yaml]
   ----
  
positive.code: builds that are re-run from existing build configurations or builds will get the
  new settings.
  
  The `*BuildDefaults*` admission control plug-in allows administrators to set
  global defaults for settings such as the Git HTTP and HTTPS proxy, as well as
  default environment variables and image labels. These defaults do not overwrite
  values that have been configured for a specific build. However, if those values
  are not present on the build definition, they are set to the default value.
  
  The `*BuildOverrides*` admission control plug-in allows administrators to
  override a setting in a build, regardless of the value stored in the build. It
  currently supports overriding the `*forcePull*` flag on a build strategy to
  enforce always refreshing the local image during a build by pulling the image
  from the registry. This ensures that a user can only build with an image that
  they are allowed to pull. The plug-in can also be configured to apply a set of
  
negative.code:             key2: value2
            annotations: <4>
              key1: value1
              key2: value2
  ----
  <1> Force all builds to pull their builder image and any source images before
  starting the build.
  <2> Additional labels to be applied to every image built. Labels
  defined here take precedence over labels defined in `BuildConfig`.
  <8> Build pods will only run on nodes with the `key1=value2` and `key2=value2` labels.
      Users can define additional key/value labels to further constrain the set of nodes
      a build runs on, but the *node* must have at least these labels.
  <9> Build pods will have these annotations added to them.
  ====
  
  . Restart the master service for the changes to take effect:
  +
  ====
  ----
  # systemctl restart atomic-openshift-master
  ----
  ====
  // end::installconfig_build_defaults_overrides[]
  