anchor.diff:  `oc delete all -l _<label>_`
   .^|Deletes the specified OpenShift object. An object configuration can also be
   passed in through STDIN. The `oc delete all -l _<label>_` operation deletes all
  -objects matching the specified `_<label>_`.
  +objects matching the specified `_<label>_`, including the
  +link:../architecture/core_objects/kubernetes_model.html#replication-controller[replication
  +controller] so that pods are not re-created.
   
   |`expose`
   |`oc expose _<object_type>_ _<object_name_or_id>_`
  -|Looks up a service and exposes it as a route. There is also the ability to expose a deployment config, replication controller, service, or pod as a new service on a specified port. If no labels are specified, the new object will re-use the labels from the object it exposes.
  -
  -
  -|`log`
  -|`oc log -f _<pod_name>_ _<container_name>_`
  +|Looks up a service and exposes it as a route. There is also the ability to
  +expose a deployment configuration, replication controller, service, or pod as a
  +new service on a specified port. If no labels are specified, the new object will
  +re-use the labels from the object it exposes.
  +
  +
  +|`logs`
  +|`oc logs -f _<pod_name>_ _<container_name>_`
   |Retrieves the log output for a specific pod or container. This command does not
   work for other object types.
   
  
positive.code: 
  |`scale`
  |`oc scale _<object_type>_ _<object_id>_ --replicas=_<#_of_replicas>_`
  |Sets the number of desired replicas for a replication controller or a
  deployment configuration to `_<#_of_replicas>_`.
  
  |`update`
  |`oc update -f _<file_or_directory_path>_`
  
negative.code: 
  * A deployment was initiated incorrectly, and you want to cancel it before it can do further damage.
  * There is a security fix you need to apply, and you do not want to wait for an ongoing deployment to complete.
  * A deployment or hook implementation is stuck after running for too long, and you cannot initiate a deployment when there is a deployment already running.
  
  [NOTE]
  ====
  By default, the deployment process is restricted to 6 hours. If a deployment is still in progress after 6 hours, then the containers for the deployment pod and any deployment hook pods are all deleted, and these pods are placed in the Failed state.
  ====
  
  Cancel a running or stuck deployment with the following command:
  