Skip to content

Commit 394f818

Browse files
authored
Update umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md
1 parent 9d0439b commit 394f818

File tree

1 file changed

+1
-1
lines changed
  • umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently

1 file changed

+1
-1
lines changed

umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ For the following scenarios you may find that deployments (and other operations)
2121

2222
This error usually mean that the user's account does not have the same user name and password on the environment you're deploying to. So when that user is deploying from development to staging they will get this error if they either don't exist on the staging environment or if their password is different between the dev and staging environment.
2323

24-
## My project fails to upgrade (e.g. Standard → Pro) with build errors
24+
## My project fails to upgrade (for example, Standard → Pro) with build errors
2525

2626
This can happen if your project contains very long file or folder paths (typically over 200 characters). During a plan upgrade, the deployment process may fail to find certain files, resulting in errors such as:
2727

0 commit comments

Comments
 (0)