anchor.diff:  
   |`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>_`.
  +|Sets the number of desired replicas for a
  +link:../architecture/core_objects/kubernetes_model.html#replication-controller[replication
  +controller] or a link:../dev_guide/deployments.html[deployment configuration] to
  +`_<#_of_replicas>_`.
   
   |`update`
   |`oc update -f _<file_or_directory_path>_`
  
positive.code: ----
  
  After running this command, the deployment eventually shuts down and transitions to a Failed status.
  
  
negative.code: `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>_`, 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 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.
  
  