anchor.diff:  
   
   |`logs`
  -|`oc logs -f _<pod_name>_`
  +|`oc logs -f <pod_name>`
   |Retrieve the log output for a specific build, deployment, or pod. This command
   works for builds, build configurations, deployment configurations, and pods.
   
   |`exec`
  -|`oc exec -p _<pod_ID>_ \`
  -`-c _<container_ID>_ -- _<command>_`
  -|Execute a command in a already-running container. It will default to the first container if none is specified.
  +|`oc exec -p <pod_ID> \`
  +`-c <container_ID> -- <command>`
  +|Execute a command in a already-running container. It will default to the first
  +container if none is specified.
   
   |`rsh`
  -|`oc rsh _<pod_ID>_`
  +|`oc rsh <pod_ID>`
   |Open a remote shell session to a container.
   
   |`rsync`
  -|`oc rsync _<local_dir>_ _<pod_ID>_:_<pod_dir>_ \`
  -`-c _<container_ID>_`
  -|Copy contents of local directory to a directory in an already-running pod container. It will default to the first container if none is specified.
  +|`oc rsync <local_dir> <pod_ID>:<pod_dir> \`
  +`-c <container_ID>`
  +|Copy contents of local directory to a directory in an already-running pod
  +container. It will default to the first container if none is specified.
   
   |`port-forward`
  -|`oc port-forward _<pod_ID>_ \`
  -`_<first_port_ID>_ _<second_port_ID>_`
  +|`oc port-forward <pod_ID> \`
  +`<first_port_ID> <second_port_ID>`
   |link:../dev_guide/port_forwarding.html[Forward one or more local ports] to a pod.
   
   |`proxy`
  -|`oc proxy --port=_<port_ID>_ \`
  -`--www=_<static_directory>_`
  +|`oc proxy --port=<port_ID> \`
  +`--www=<static_directory>`
   |Run a proxy to the Kubernetes API server
   
   |===
  
positive.code: indicated files.
  
  |`process`
  |`oc process -f _<template_file_path>_`
  |Transform a project link:../dev_guide/templates.html[template] into a project
  configuration file.
  
  |`run`
  |`oc run NAME --image=image [--env="key=value"] [--port=port] +
  [--replicas=replicas] [--dry-run=bool] [--overrides=inline-json] [options]`
  |Create and run a particular image, possibly replicated. Create a deployment
  config to manage the created container(s). You can choose to run in the
  foreground for an interactive container execution.
  
  |`export`
  |`oc export _<object_type>_ [--options]`
  |Export resources to be used elsewhere.
  
  |`policy`
  
negative.code: |Operation |Syntax |Description
  
  |`get`
  |`oc get <object_type> [<object_name_or_id>]`
  |Return a list of objects for the specified link:#object-types[object type]. If
  the optional `_<object_name_or_id>_` is included in the request, then the list
  of results is filtered by that value.
  
  |`describe`
  |`oc describe <object_type> <object_id>`
  |Returns information about the specific object returned by the query. A specific
  `_<object_name_or_id>_` must be provided. The actual information that is
  available varies as described in link:#object-types[object type].
  
  .3+|`edit`
  |`oc edit <object_type>/<object_type_name>`
  |Edit the desired object type.
  
  |`OSC_EDITOR="<text_editor>" oc edit \`
  `<object_type>/<object_type_name>`
  |Edit the desired object type with a specified text editor.
  
  |`oc edit <object_type>/<object_type_name> \`
  `--output-version=<object_type_version> \`
  `-o <object_type_format>`
  |Edit the desired object in a specified format (eg: JSON).
  
  |`env`
  |`oc env <object_type>/<object_type_name> \`
  `<var_name>=<value>`
  |Update the desired object type with a new environment variable.
  
  |`volume`
  |`oc volume <object_type>/<object_type_name> \`
  `[--option]`
  |Modify a link:../dev_guide/volumes.html[volume].
  
  |`label`
  |`oc label <object_type> <object_name_or_id> \`
  `<label>`
  |Update the labels on a object.
  
  |`expose`
  |`oc expose <object_type> <object_name_or_id>`
  |Look up a service and expose 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.
  
  |`delete`
  a|`oc delete -f <file_path>`
  
  `oc delete <object_type> <object_name_or_id>`
  
  `oc delete <object_type> -l <label>`
  
  `oc delete all -l <label>`
  .^|Delete the specified 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_concepts/deployments.html#replication-controllers[replication
  controller] so that pods are not re-created.
  
  