anchor.diff:  files can be obtained through https://access.crunchydata.com/ on the downloads
   page.*
   
  -=== Creating a Demo Namespace on Kubernetes
  +=== Creating a Demo Namespace
  +
  +In Kubernetes, a concept called a *namespace* provides the means to separate
  +created resources or components into individual logically grouped partitions.
  +
  +It is considered a best practice to have dedicated namespaces for projects in
  +both testing and production environments.
  +
  +NOTE: All examples in the Crunchy Container Suite operate within the namespace
  +defined by the environment variable `$CCP_NAMESPACE`. The instructions below
  +illustrate how to set up and work within new namespaces or projects in both
  +Kubernetes and OpenShift.
  +
  +==== Kubernetes
   
   This section will illustrate how to set up a new Kubernetes namespace called *demo*, and will
   then show how to provide permissions to that namespace to allow the Kubernetes examples to run
  -within that namespace. This is a *requirement* for running the examples.
  +within that namespace.
   
   First, view currently existing namespaces:
   ....
  
positive.code: 
  === Configure HostPath
  
  HostPath is the simplist storage backend to setup, it only is feasible
  on a single node but is good for testing the examples.  In your *.bashrc*
  file, add the following variables to specify unique settings to
  your hostpath directory:
  ....
  export CCP_SECURITY_CONTEXT=""
  export CCP_STORAGE_PATH=/data
  
negative.code: We do not recommend this authentication policy for a production
  deployment of OCP.
  
  The next step is to create a *demo* namespace to run the examples within. The
  name of this OCP project will be what you supply in the CCP_NAMESPACE
  environment variable:
  ....
  