[CF4SaaS] Review hostname validation backoff schedule (#21618)

Author: RebeccaTamachiro

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule.mdx

@@ -11,7 +11,7 @@ head:
 
 After you create a custom hostname, Cloudflare has to [validate that hostname](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/).
 
-Attempts to validate a Custom Hostname are distributed over 7 days (a total of 75 retries). At the end of this schedule, if the validation is unsuccessful, the custom hostname will be deleted. The function that determines the next check varies based on the number of attempts:
+Attempts to validate a Custom Hostname are distributed over seven days (a total of 75 retries). At the end of this schedule, if the validation is unsuccessful, the custom hostname will be deleted. The function that determines the next check varies based on the number of attempts:
 
 * For the first 10 attempts:
 
@@ -25,7 +25,7 @@ now() + min((floor(60 * pow(1.05, retry_attempt)) * INTERVAL '1 second'), INTERV
 now() + min((floor(60 * pow(1.15, retry_attempt)) * INTERVAL '1 second'), INTERVAL '4 hours')
 ```
 
-The first 10 checks complete within 2 minutes and most checks complete in the first 4 hours. The check back off is capped to a maximum of 4 hours to avoid exponential growth. The back off behavior causes larger gaps between check intervals towards the end of the back off schedule:
+The first 10 checks complete within 20 minutes and most checks complete in the first four hours. The check back off is capped to a maximum of four hours to avoid exponential growth. The back off behavior causes larger gaps between check intervals towards the end of the back off schedule:
 
 | Retry Attempt | In Seconds | In Minutes | In Hours |
 | ------------- | ---------- | ---------- | -------- |