anchor.diff:  [[config-change-trigger]]
   === Configuration Change Trigger
   
  -The `*ConfigChange*` trigger results in a new replication controller whenever
  +The `ConfigChange` trigger results in a new replication controller whenever
   changes are detected in the pod template of the deployment configuration.
   
   [NOTE]
   ====
  -If a `*ConfigChange*` trigger is defined on a deployment configuration,
  +If a `ConfigChange` trigger is defined on a deployment configuration,
   the first replication controller will be automatically created soon after
   the deployment configuration itself is created and it is not paused.
   ====
   
   
  -.A `*ConfigChange*` Trigger
  +.A ConfigChange Trigger
   ====
   
   [source,yaml]
  
positive.code: xref:../dev_guide/application_health.adoc#dev-guide-application-health[readiness
  checks] to determine if a new pod is ready for use. If a readiness check fails,
  the deployment configuration will retry to run the pod until it times out. The
  default timeout is `10m`, a value set in `*TimeoutSeconds*` in
  `*dc.spec.strategy.*params*`.
  
  The xref:rolling-strategy[Rolling strategy] is the default strategy used if
  no strategy is specified on a deployment configuration.
  
negative.code: ----
  $ oc edit dc/<deployment_config>
  ----
  . Add the `serviceAccount` and `serviceAccountName` parameters to the `spec`
  field, and specify the service account you want to use:
  +
  ----
  