[SaaS]Update versioning.mdx

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/versioning.mdx

@@ -47,7 +47,7 @@ Though you can use [CNAME validation](#cname-validation), we recommend you eithe
 
 Custom Hostnames can also be validated once Cloudflare detects that the Custom Hostname is a CNAME record pointing to the fallback record configured for the SSL for SaaS domain. Though this is the simplest validation method, it increases the risk of errors. Since a CNAME record would also route traffic to Cloudflare’s edge, traffic may reach our edge before the Custom Hostname has completed validation or the SSL certificate has issued.
 
-Once you have tested and added the hostname validation step to your Custom Hostname creation process, please contact your Cloudflare Account Team to schedule a date to migrate your SSL for SaaS v1 zones. Your Cloudflare Account Team will work with you to validate your existing Custom Hostnames without downtime.
+Once you have tested and added the hostname validation step to your Custom Hostname creation process, please contact your account team to schedule a date to migrate your SSL for SaaS v1 zones. Your account team will work with you to validate your existing Custom Hostnames without downtime.
 
 ## If you are using BYOIP or Apex Proxying:
 
@@ -78,34 +78,34 @@ You can revert the migration at any time.
 
 Before your migration, you should:
 
-1. To test validation methods, set up a test zone and ask your Solutions Engineer (SE) to enable SSL for SaaS v2.
-2. Wait for your SE to run our pre-migration tool. This tool groups your hostnames into one of the following statuses:
+1. To test validation methods, set up a test zone and ask your account team to enable SSL for SaaS v2.
+2. Wait for your account team to run our pre-migration tool. This tool groups your hostnames into one of the following statuses:
    * `test_pending`: In the process of being verified or was unable to be verified and re-queued for verification. A custom hostname will be re-queued 25 times before moving to the `test_failed` status.
    * `test_active`: Passed CNAME verification
    * `test_active_apex`: Passed Apex Proxy verification
    * `test_blocked`: Hostname will be blocked during the migration because hostname belongs to a banned zone. Contact your CSM to verify banned custom hostnames and proceed with the migration.
    * `test_failed`: Failed hostname verification 25 times
-3. Review the results of our pre-migration tool (run by your Solutions Engineer) using one of the following methods:
+3. Review the results of our pre-migration tool (run by your account team) using one of the following methods:
    * Via the API: `https://api.cloudflare.com/client/v4/zones/{zone_tag}/custom_hostnames?hostname_status={status}`
-   * Via a CSV file (provided by your SE)
+   * Via a CSV file (provided by your account team)
    * Via the Cloudflare dashboard:
      ![Review SSL migration status in the dashboard](~/assets/images/cloudflare-for-platforms/ssl-migration-status.png)
-4. Approve the migration. Your Cloudflare account team will work with you to schedule a migration window for each of your SSL for SaaS zones.
+4. Approve the migration. Your account team will work with you to schedule a migration window for each of your SSL for SaaS zones.
 
 ## During the migration
 
 After the migration has started and has had some time to progress, Cloudflare will generate a list of Custom Hostnames that failed to migrate and ask for your approval to complete the migration. When you give your approval, the migration will be complete, SSL for SaaS v1 will be disabled for the zone, and any Custom Hostname that has not completed hostname validation will no longer function.
 
 The migration timeline depends on the number of Custom Hostnames. For example, if a zone has fewer than 10,000 Custom Hostnames, the list can be generated around an hour after beginning the migration. If a zone has millions of Custom Hostnames, it may take up to 24 hours to identify instances that failed to successfully migrate.
 
-When your Cloudflare Account Team asks for approval to complete the migration, please respond in a timely manner. You will have **two weeks** to validate any remaining Custom Hostnames before they are systematically deleted.
+When your account team asks for approval to complete the migration, please respond in a timely manner. You will have **two weeks** to validate any remaining Custom Hostnames before they are systematically deleted.
 
 ## When is the migration?
 
 The migration process starts on March 31, 2021 and will continue until final deprecation on September 1, 2021.
 
-If you would like to begin the migration process before March 31, 2021, please contact your Cloudflare Account Team and they will work with you to expedite the process. Otherwise, your Cloudflare Account Team will reach out to you with a time for a migration window so that your zones are migrated before **September 1, 2021** end-of-life date.
+If you would like to begin the migration process before March 31, 2021, please contact your account team and they will work with you to expedite the process. Otherwise, your account team will reach out to you with a time for a migration window so that your zones are migrated before **September 1, 2021** end-of-life date.
 
 ## What if I have additional questions?
 
-If you have any questions, please contact your Cloudflare Account Team or [[email protected]](mailto:[email protected]).
+If you have any questions, please contact your account team or [[email protected]](mailto:[email protected]).