anchor.diff:  
   === replication controller
   
  -Usage: replication controller
  +Usage: replication controller(s) as appropriate
   
   Kubernetes object that ensures N (as specified by the user) instances of a given
   Pod are running at all times.
   
   ''''
  +=== scheduler
  +
  +Usage: scheduler(s) as appropriate
  +
  +Component of the Kubernetes master or OpenShift master that manages the state of
  +the system, places pods on nodes, and ensures that all containers that are
  +expected to be running are actually running.
  +
  +''''
  +=== SkyDNS
  +
  +Usage: SkyDNS
  +
  +Component of the Kubernetes master or OpenShift master that provides
  +cluster-wide DNS resolution of internal hostnames for services and pods.
  +
  +''''
   === Source-to-Image (S2I)
   
   Usage: Source-to-Image for the first time reference; S2I thereafter.
  
positive.code: 
  === OpenShift master
  
  Usage: OpenShift master
  
  OpenShift provides a REST endpoint for interacting with the system.  New
  deployments/configurations are created with the REST API and the state of the
  system can be interrogated through this endpoint as well.
  
  ''''
  
  
negative.code: 
  Although the term _application_ is no longer an official noun in OpenShift,
  customers still create and host applications on OpenShift, and using the term
  within certain contexts is acceptable. For example, the term _application_ may
  refer to some combination of an image, a Git repository, or a replication
  controller, and this _application_ may be running PHP, MySQL, Ruby, JBoss, or
  something else.
  
  Do *NOT* use the term _application_ in a topic or section heading.
  
  