anchor.diff:  
   include::partial$recommended-steps.adoc[tags=evaluate-steps]
   
  -== Integrate
  +== Build your own OTA-enabled solution
   
   === Recommendations
   
  
positive.code: 
  Here are our recommendations for deploying OTA Connect to production:
  
  include::partial$recommended-steps.adoc[tags=deploy-steps]
negative.code: 
  That's why it's better work in phases when setting up your OTA Connect in your organization. We recommend that you work in three main phases:
  
  . __Evaluate OTA Connect__
  . __Build your own OTA-enabled solution__
  . __Deploy your own OTA-enabled solution__
  
  This guide contains chapters to guide you through each phase and the following sections give you an introduction the phased approach:
  
  == Evaluate OTA Connect
  
  During evaluation, you should focus on testing the basic update functionality to make sure that you understand how it works. At this stage you don't need to think about customization or production-level security.
  
  