anchor.diff:  
   * *Set up full device-credential provisioning for your devices*
   +
  -At this point you should have your own fleet root certificate which you register with the OTA COnnect server under your production login.
  +At this point you should have your own fleet root certificate which you register with the OTA Connect server under your production login.
   +
   You should ideally have an automated process to sign your device certificates and install them on your disk images before they flashed to the target boards.
   +
  
positive.code: 
  * *Set up different user logins*
  +
  In OTA Connect, all devices and software belong to one *user* login. However, you don't want to mix up test software and production software by creating them all under the same user.
  +
  In a proper production workflow, you'll need separate user logins to manage the different stages:
  +
  . A developer user such as "dev@acme.com".
  . A QA user such as ""qa@acme.com"".
  . A production user such as "prod@acme.com"".
  +
  These logins provide you with a convenient way of clearly separating your development, QA and production resources.
  
  ////
  COMMENTING OUT UNTIL ORGANIZATIONS STOPS BEING "ALPHA"
  
negative.code: +
  After you've finished integration and development, you'll need to move disk images from one account to another. For example, you might want to send a development build that you’re happy with to the QA team, or send that build to the deployment team once it’s passed QA.
  
  //  end::deploy-steps[]
  