anchor.diff:  ----
   
   === How this works?
  -For the profiles to work, by default a subdirectories will be created in *$HOME/.oc/profiles* with the profile name. A file called *$HOME/.oc/active_profile*
  +For the profiles to work, by default a subdirectory will be created in *$HOME/.oc/profiles* with the profile name. A file called *$HOME/.oc/active_profile*
   will hold also the name of the active profile, if there is a cluster up. Removing the cluster will remove the subdirectory holding all
   the profile data.
   
   We're using --host-data-config and --host-data-dir to retain the configuration of the cluster, as we understand this is basic for daily
   use of the tool. And we use --keep-config to retain this information.
   
  -We're also binding the cluster to 127.0.0.1 as this is the way to make the cluster secure, and reproducible, as ip changes when you move from network
  -to network, and since otherwise, anyone could just log into your running cluster if you had a cluster up, since it's using AnyPasswd identity provider.
  +We're also binding the cluster to 127.0.0.1 as this is the way to make the cluster secure, and reproducible, as the ip address changes when you move from network
  +to network. Also, anyone can log into your running cluster if you had a cluster up, since it's using *AnyPasswd* identity provider.
   
  -We also do 2 really convenient things for developers:
  +We also do two really convenient things for developers:
   
   * We create an *admin/admin* user that will be a *cluster-admin*, so you can login as admin from the web console
  -* We add the *sudoer* role to *system:authenticated* so that any user can do impersonate as *cluster-admin* and there's no need to change user profiles
  +* We add the *sudoer* role to *system:authenticated* so that any user can impersonate *cluster-admin* without needing to change user profiles
   
   
   == Convenience methods for working with persistent volumes
  -As probably any user will need to work with persistent services, we have added 2 convenience methods for working with volumes. One for cluster-specific
  +Most users will need to work with persistent services, so we have added two convenience methods for working with volumes. One for cluster-specific
   volumes, and another for shared volumes (similating NFS server behaviors).
   
   * oc-cluster create-volume volumeName [size|10Gi] [path|/Users/jmorales/.oc/profiles/<profile>/volumes/<volumeName>]
  
positive.code: than this tool's.
  
  == Contributing
  Pull Request, and issues to make the tool are welcome. Don't just for it, but contribute back with your use cases. Once we have the plugin mechanism, this will be easier to do.
  Also, we would love all this use cases to be in ôc cluster* but until that doesn't happen, we will keep using and maintaining this tool.
  
  *This work is done by the OpenShift Evangelist team*
  
negative.code: https://127.0.0.1:8443/console
  ----
  
  I need to log in to the origin container, to check something:
  
  ----
  $ oc-cluster ssh
  