Skip to content

Commit ad83e83

Browse files
committed
Fixed grammar
1 parent eabcbf9 commit ad83e83

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

umbraco-cloud/go-live/manage-hostnames/rewrites-on-cloud.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,11 @@ The rewrite rules should be added to the `<system.webServer><rewrite>` module in
2020

2121
## Best practices
2222

23-
When you are doing rewrite rules on Umbraco Cloud there are a few important things to keep in mind:
23+
When setting up rewrite rules on Umbraco Cloud, there are a few important things to keep in mind:
2424

25-
* Always make sure that you add a condition that negates the Umbraco Backoffice - `/umbraco`, otherwise, you will not be able to do deployments to/from the environment.
26-
* To be able to continue working locally with your Umbraco Cloud project, you also need to add a condition that negates `localhost`.
27-
* To serve verification files from the `.well-known` path (for example, Apple Pay or Google), follow the [Rewrite rule workaround in the CMS documentation](https://docs.umbraco.com/umbraco-cms/reference/routing/iisrewriterules#example-serving-files-from-the-well-known-path).
25+
* Always include a condition to exclude the Umbraco backoffice path (`/umbraco`). Failing to do so may prevent you from deploying to and from the environment.
26+
* To continue working locally with your Umbraco Cloud project, you should also add a condition to exclude `localhost`.
27+
* To serve verification files from the `.well-known` directory (for example, Apple Pay or Google), follow the [Rewrite rule workaround in the CMS documentation](https://docs.umbraco.com/umbraco-cms/reference/routing/iisrewriterules#example-serving-files-from-the-well-known-path).
2828

2929
## Hiding the default umbraco.io URL
3030

0 commit comments

Comments
 (0)