anchor.diff:  |Operation |Syntax |Description
   
   |`get`
  -|`oc get _<object_type>_ [_<object_name_or_id>_]`
  +|`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>_`
  +|`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>_`
  +|`oc edit <object_type>/<object_type_name>`
   |Edit the desired object type.
   
  -|`OSC_EDITOR="_<text_editor>_" oc edit \`
  -`_<object_type>_/_<object_type_name>_`
  +|`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>_`
  +|`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>_ \`
  -`_<EN_VAR>_=/_<VALUE>_`
  -|Update the desired object type with a new environment variable
  +|`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>_ \`
  +|`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>_`
  +|`oc label <object_type> <object_name_or_id> \`
  +`<label>`
   |Update the labels on a object.
   
   |`expose`
  -|`oc expose _<object_type>_ _<object_name_or_id>_`
  +|`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>_`
  +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
  +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.
   
  
positive.code: 
  
  |`logs`
  |`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.
  
  |`rsh`
  |`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.
  
  |`port-forward`
  |`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>_`
  |Run a proxy to the Kubernetes API server
  
  |===
  
negative.code: indicated files. Any existing resources are ignored.
  
  |`update`
  |`oc update -f <file_or_dir_path>`
  |Attempt to modify an existing object based on the contents of the specified
  configuration file. The `-f` flag can be passed multiple times with different
  file or directory paths. When the flag is passed multiple times, `oc update`
  