anchor.diff:  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*`.
  +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.
  
positive.code:     memory: "256Mi" <2>
  ----
  
  <1> `*cpu*` is in CPU units: `100m` represents 0.1 CPU units (100 * 1e-3).
  <2> `*memory*` is in bytes: `256Mi` represents 268435456 bytes (256 * 2 ^ 20).
  ====
  
  However, if a quota has been defined for your project, one of the following two
  items is required:
  
  - A `*resources*` section set with an explicit `*requests*`:
  +
  ====
  [source,yaml]
  
negative.code: [[config-change-trigger]]
  === Configuration Change Trigger
  
  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,
  the first replication controller will be automatically created soon after
  the deployment configuration itself is created and it is not paused.
  ====
  
  
  .A ConfigChange Trigger
  ====
  
  [source,yaml]
  