anchor.diff:  1.1 to 1.2.
   endif::[]
   ifdef::openshift-enterprise[]
  -3.1 to 3.2, or are applying an asynchronous update to 3.2. These steps will pull
  +3.1 to 3.2, or are applying an asynchronous update to 3.2. These steps pull
   the latest 3.2 logging images.
   endif::[]
   ====
   
   . Ensure you are working in the project where the EFK stack was previously
  -deployed, and stay in that project for the remainder of these steps. For
  -example, if the project is named *logging*:
  +deployed. For example, if the project is named *logging*:
   +
   ----
   $ oc project logging
  
positive.code: $ oc scale dc/logging-es-ops-<unique_name> --replicas=0
  ----
  
  . After your Elasticsearch pods are confirmed to be terminated, you can now rerun
  the deployer to generate any missing or changed features.
  
  ifdef::openshift-origin[]
  .. Follow the same steps as done previously in
  link:../../install_config/aggregate_logging.html#deploying-the-efk-stack[Deploying
  the EFK Stack]. After the deployer completes, re-attach your persistent volumes
  you were using previously.
  endif::openshift-origin[]
  ifdef::openshift-enterprise[]
  .. Follow step 1 as done previously in
  link:../../install_config/aggregate_logging.html#deploying-the-efk-stack[Deploying
  the EFK Stack]. After the deployer completes, as a cluster administrator, re-attach
  your persistent volumes you were using previously and then deploy a template that
  is created by the deployer:
  +
  ====
  ----
  
negative.code: [[manual-upgrading-efk-logging-stack]]
  == Upgrading the EFK Logging Stack
  
  Use the following to upgrade an
  link:../../install_config/aggregate_logging.html[already-deployed EFK logging
  stack].
  
  [NOTE]
  ====
  