Description of problem:

   After running through an SDN to OVN migration in AWS, we found several opportunities for improvements to documentation

Version-Release number of selected component (if applicable):

    Performed in 4.14.z but these suggestions apply to 4.15.z and 4.16.0 as well

• In Step 2 the note says:
  • This step does not deploy OVN-Kubernetes immediately. Instead, specifying the migration field triggers the Machine Config Operator (MCO) to apply new machine configs to all the nodes in the cluster in preparation for the OVN-Kubernetes deployment.
  • This should be amended with the following:
    • The MCO update will require a reboot.  Wait until the reboots are finished and all nodes are ready [1] and all cluster operators are available [2] before progressing
      • [1] oc get mcp
      •  [2]oc get co
• Step 3 says:
  • Optional: You can disable automatic migration of several OpenShift SDN capabilities to the OVN-Kubernetes equivalents:
  • You don't need to perform Step 2 and then do Step 3 (if needed), it's one or the other.  They way it currently reads you would do Step 2 first and then do Step 3 but you can accomplish Step 2 by doing Step 3. 
• Need a note with Step 9: 
  • Don't expect all cluster operators to be healthy before the reboot.