Skip to content

Commit 5f83cf1

Browse files
authored
More small fixes
1 parent 49ae345 commit 5f83cf1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

umbraco-cloud/go-live/manage-hostnames/hostname-pre-validation.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -47,15 +47,15 @@ Umbraco Cloud will provide two DNS records:
4747
Value: Points to a domain under Umbraco's control (e.g., \<hostname\>.53231a669c5282f8.dcv.cloudflare.com).
4848

4949
{% hint style="info" %}
50-
DNS propagation times can vary. Changes may take a few minutes to several hours to become active globally. Tools like https://www.nslookup.io/ can help verify that your records are live.
50+
DNS propagation times can vary. Changes may take a while to become active globally. Tools like https://www.nslookup.io/ can help verify that your records are live.
5151
{% endhint %}
5252

5353

5454
### 3. Check Validation Status
5555

5656
Return to the Hostname page in Umbraco Cloud. You'll see a Hostname Information Box showing the current status of your validation.
5757

58-
The status will change to Active when everything is set up correctly. The hostname is validated, and the TLS certificate issued.
58+
The status will change to Active when everything is set up correctly. The hostname is validated, and the TLS certificate is issued.
5959

6060
<figure><img src="images/pre-validation-status-modal.png" alt="This is an image of the Pre-Validation status modal"></figure>
6161

@@ -78,7 +78,7 @@ Umbraco Cloud will automatically handle future certificate renewals without the
7878

7979
## Custom Certificate
8080

81-
If you plan to use a [custom certificate](security-certificates), the Hostname Pre-Validation method can be used to prove ownership of the hostname before binding the custom certificate.
81+
If you plan to use a [custom certificate](security-certificates), the Hostname Pre-Validation method can be used to prove ownership of the hostname. This is done before binding the custom certificate.
8282

8383
You can do this by following these steps:
8484

0 commit comments

Comments
 (0)