@@ -92,7 +92,7 @@ The value defined in `appsettings.json` file will be overwritten with the Cloud
9292
9393When naming a secret, it is possible to use alphanumeric characters as well as '\_ ' (underscore).
9494
95- There are some reserved words that cannot be accepted:
95+ Some words are reserved and ** cannot** be accepted:
9696
9797* ` COMMAND `
9898* ` HOME `
@@ -103,7 +103,7 @@ There are some reserved words that cannot be accepted:
103103* ` REGION_NAME `
104104* ` CONNECTIONSTRINGS__UMBRACODBDSN `
105105
106- There are also a number of prefixes that are not accepted.
106+ The following prefixes are ** not** accepted.
107107
108108The list consists of:
109109
@@ -131,17 +131,17 @@ The list consists of:
131131
132132### Accepted Prefixes
133133
134- While we have a number of prefixes that are not accepted, we do allow the use of the below prefixes for Secrets on Umbraco Cloud:
134+ The following prefixes are allowed for Secrets on Umbraco Cloud:
135135
136136* ` Umbraco__CMS__Global__Smtp__ `
137- * ` Umbraco__Forms__Security__FormsApiKey `
138- * ` Umbraco__Forms__FieldTypes__Recaptcha `
139- * ` Umbraco__CMS__Integrations `
140- * ` Umbraco__CMS__DeliveryAPI `
141- * ` UMBRACO__LICENSES__YOURPRODUCT `
137+ * ` Umbraco__Forms__Security__FormsApiKey__ `
138+ * ` Umbraco__Forms__FieldTypes__Recaptcha__ `
139+ * ` Umbraco__CMS__Integrations__ `
140+ * ` Umbraco__CMS__DeliveryAPI__ `
141+ * ` UMBRACO__LICENSES__ `
142142
143143It is also possible to use Secrets to save API keys, Passwords, and ReChaptcha for all our Umbraco products on Umbraco Cloud.
144144
145145Do you have an existing or new secret that you want to add to a key vault that conflicts with the name restrictions?
146146
147- Then please contact Umbraco support, then we will then consider it as soon as possible.
147+ Then please contact Umbraco support, then we will consider it as soon as possible.
0 commit comments