anchor.diff:  
   [NOTE]
   ====
  -In order to preserve customized SCCs during upgrades editing settings on the default SCCs
  -other than priority, users, and groups is not recommended.
  -====
  -
  -== Updating the default Security Context Constraints
  +In order to preserve customized SCCs during upgrades, do not edit settings on
  +the default SCCs other than priority, users, and groups.
  +====
  +
  +== Updating the Default Security Context Constraints
   
   Default SCCs will be created when the master is started if they are missing. To reset SCCs
   to defaults, or update existing SCCs to new default definitions after an upgrade you may:
  
positive.code: It is recommended that
  link:../architecture/additional_concepts/storage.html[persistent storage] using
  `*PersistentVolume*` and `*PersistentVolumeClaim*` objects be used for
  link:../install_config/install/docker_registry.html[registry deployments]. If you are testing and
  would like to instead use the `oadm registry` command with the `--mount-host`
  option, you must first create a new link:service_accounts.html[service account]
  for the registry and add it to the *privileged* SCC. See the
  link:../install_config/install/docker_registry.html#storage-for-the-registry[Administrator
  Guide] for full instructions.
  
  
negative.code: 
  [NOTE]
  ====
  In order to preserve customized SCCs during upgrades, do not edit settings on
  the default SCCs other than priority, users, and groups.
  ====
  
  . Edit the *restricted* SCC:
  