diff --git a/16/umbraco-engage/SUMMARY.md b/16/umbraco-engage/SUMMARY.md
index 8566a19e7fd..a3072873f0d 100644
--- a/16/umbraco-engage/SUMMARY.md
+++ b/16/umbraco-engage/SUMMARY.md
@@ -133,7 +133,7 @@
* [Retention periods of data](security-and-privacy/retention-periods-of-data.md)
* [Anonymization](security-and-privacy/anonymization.md)
* [GDPR & EU regulation](security-and-privacy/gdpr/README.md)
- * [How to become GDPR compliant using cookiebot](security-and-privacy/gdpr/how-to-become-gdpr-compliant-using-cookiebot.md)
+ * [How to become GDPR compliant using Cookiebot](security-and-privacy/gdpr/how-to-become-gdpr-compliant-using-cookiebot.md)
* [How it works](security-and-privacy/how-it-works.md)
## Tutorials
diff --git a/16/umbraco-engage/developers/ab-testing/README.md b/16/umbraco-engage/developers/ab-testing/README.md
index 2c6df9be2e7..7d6f5516146 100644
--- a/16/umbraco-engage/developers/ab-testing/README.md
+++ b/16/umbraco-engage/developers/ab-testing/README.md
@@ -1,5 +1,5 @@
---
-description: Umbraco Engage offers multiple ways for performaing A/B tests on your website.
+description: Umbraco Engage offers multiple ways for performing A/B tests on your website.
hidden: true
---
diff --git a/16/umbraco-engage/developers/analytics/location.md b/16/umbraco-engage/developers/analytics/location.md
index e35d96bbfdd..27ae66b24d1 100644
--- a/16/umbraco-engage/developers/analytics/location.md
+++ b/16/umbraco-engage/developers/analytics/location.md
@@ -111,5 +111,4 @@ From the country, you can drill down to the city. This will then filter the disp
A community package called "[Engage LocationHeaders](https://github.com/hjaltedaniel-umbraco/Umbraco.Community.Engage.LocationHeaders)" is available. It's a lightweight package that enriches analytics and segmentation data with location information extracted from the HTTP headers, based on the sample code above.
-The package is designed to work out-of-the-box on **Umbraco Cloud**, using location headers automatically injected by services like **Cloudflare** or **Azure Front Door**. This allows Umbraco Engage to tap into geographic information such as **country**, **region**, and **city**, without the need for client-side geolocation or third-party services.
-
+The package works out-of-the-box on **Umbraco Cloud**, using location headers injected by services like **Cloudflare** or **Azure Front Door**. This lets Umbraco Engage access geographic details such as **country**, **region**, and **city**, without relying on client-side geolocation or third-party services.
diff --git a/16/umbraco-engage/developers/analytics/what-is-measured-by-default.md b/16/umbraco-engage/developers/analytics/what-is-measured-by-default.md
index 5cfd0f492c9..7c4457b37bf 100644
--- a/16/umbraco-engage/developers/analytics/what-is-measured-by-default.md
+++ b/16/umbraco-engage/developers/analytics/what-is-measured-by-default.md
@@ -32,4 +32,4 @@ For a request to be considered a valid pageview, the following conditions have t
With the collected data, the Analytics reports in Umbraco Engage can be visualized. It also allows us to calculate other metrics, such as conversion rates, bounce rates, and landing & exit pages.
-If you [include the client-side collection script](client-side-events-and-additional-javascript-files/additional-measurements-with-the-analytics-scripts.md) as well, you can also capture behavioural data of your visitors.
+By [including the client-side collection script](client-side-events-and-additional-javascript-files/additional-measurements-with-the-analytics-scripts.md), you can also capture visitor behavior data.
diff --git a/16/umbraco-engage/developers/headless/using-the-marketing-api.md b/16/umbraco-engage/developers/headless/using-the-marketing-api.md
index 13b02ac4766..b4d8f3fa3bb 100644
--- a/16/umbraco-engage/developers/headless/using-the-marketing-api.md
+++ b/16/umbraco-engage/developers/headless/using-the-marketing-api.md
@@ -46,7 +46,7 @@ An example of configuration in `AppSettings.json` file:
}
```
-The settings can be changed at runtime without restarting the website for these changes to take effect. These configurations will toggle whether Umbraco Engage will apply segmentation to the various Content Delivery API endpoints when applicable.
+The settings can be changed at runtime without restarting the website for these changes to take effect. These configurations will toggle whether Umbraco Engage will apply segmentation to the different Content Delivery API endpoints when applicable.
| **Key** | **Description** | **Default Value** |
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
diff --git a/16/umbraco-engage/developers/introduction/dataflow-pipeline/README.md b/16/umbraco-engage/developers/introduction/dataflow-pipeline/README.md
index d3a6b1a88d1..21931e78c7e 100644
--- a/16/umbraco-engage/developers/introduction/dataflow-pipeline/README.md
+++ b/16/umbraco-engage/developers/introduction/dataflow-pipeline/README.md
@@ -12,4 +12,4 @@ description: >-
3. [Data processing](data-parsing.md): The data is processed at a later moment to make it more efficient and normalized
4. [Data reporting](reporting.md): Finally the data is reported within Umbraco Engage
-The concept of this dataflow is the most important concept to grasp when using Umbraco Engage.
+The concept of this Dataflow is the most important concept to grasp when using Umbraco Engage.
diff --git a/16/umbraco-engage/developers/introduction/dataflow-pipeline/data-collection.md b/16/umbraco-engage/developers/introduction/dataflow-pipeline/data-collection.md
index a022925f244..76385aff695 100644
--- a/16/umbraco-engage/developers/introduction/dataflow-pipeline/data-collection.md
+++ b/16/umbraco-engage/developers/introduction/dataflow-pipeline/data-collection.md
@@ -37,7 +37,7 @@ There are different [configuration options](../../settings/configuration.md) to
* You can limit the amount of data records stored in memory. If you are limited in memory you can adjust these settings to fit your needs.
* The IP Address is anonymized by default. There is an option to change this
-* You can turn off server-side tracking. This can be useful if not every page request reaches your website. This could be the case if you're using CloudFlare for example.
+* You can turn off server-side tracking. This can be useful if not every page request reaches your website. This could be the case if you're using Cloudflare.
## Client-side collection
diff --git a/16/umbraco-engage/developers/introduction/dataflow-pipeline/data-parsing.md b/16/umbraco-engage/developers/introduction/dataflow-pipeline/data-parsing.md
index cc34656e22a..3fcfc3d71ed 100644
--- a/16/umbraco-engage/developers/introduction/dataflow-pipeline/data-parsing.md
+++ b/16/umbraco-engage/developers/introduction/dataflow-pipeline/data-parsing.md
@@ -61,5 +61,5 @@ If using [Umbraco in a load-balanced configuration](../../../getting-started/for
There is probably no or little reason to store this data forever. That is why we have two settings to clean up this data.
-* The first setting is '`AnonymizeDataAfterDays`'. After the set number of days, the data will be anonymized. This means the data will still be shown in aggregate reports like pageviews, used browsers, number of visitors, etcetera, but it can not be related to an individual visitor anymore.
+* The first setting is '`AnonymizeDataAfterDays`'. After the set number of days, the data will be anonymized. This means the data will still be shown in aggregate reports like pageviews, used browsers, number of visitors but it can not be related to an individual visitor anymore.
* The second setting is '`DeleteDataAfterDays`'. With this setting the data will be deleted after a set number of days. The reason is that it does not make sense to store your data for all eternity.
diff --git a/16/umbraco-engage/developers/introduction/dataflow-pipeline/data-storage.md b/16/umbraco-engage/developers/introduction/dataflow-pipeline/data-storage.md
index df8d638f717..ec04cb08e84 100644
--- a/16/umbraco-engage/developers/introduction/dataflow-pipeline/data-storage.md
+++ b/16/umbraco-engage/developers/introduction/dataflow-pipeline/data-storage.md
@@ -25,7 +25,7 @@ The lower the value you set, the less memory Umbraco Engage uses on your web ser
## Data storage
-The data will be stored as quickly as possible to minimize the needed resources. For this reason, the the data collected from client-side events will be stored in so-called raw tables in a non-normalized. This data will be processed in [the next step](data-parsing.md) of the data flow.
+The data will be stored as quickly as possible to minimize the needed resources. For this reason, the data collected from client-side events will be stored in so-called raw tables in a non-normalized. This data will be processed in [the next step](data-parsing.md) of the data flow.
The data collected from clientside events is stored in the table `umbracoEngageAnalyticsRawClientSideData`.
diff --git a/16/umbraco-engage/developers/introduction/performance.md b/16/umbraco-engage/developers/introduction/performance.md
index 3b709d9d06a..2f1365c8c76 100644
--- a/16/umbraco-engage/developers/introduction/performance.md
+++ b/16/umbraco-engage/developers/introduction/performance.md
@@ -10,9 +10,9 @@ Umbraco Engage is optimized for performance and you configure it to optimize the
## Separate processes for storing, parsing, and reporting
-As documented in the [dataflow process](dataflow-pipeline/) there are different steps for [collecting](dataflow-pipeline/data-collection.md), [storing](dataflow-pipeline/data-storage.md), [parsing](dataflow-pipeline/data-parsing.md), and [reporting](dataflow-pipeline/reporting.md) the data. This is primarily done for performance reasons.
+As documented in the [Dataflow process](dataflow-pipeline/) there are different steps for [collecting](dataflow-pipeline/data-collection.md), [storing](dataflow-pipeline/data-storage.md), [parsing](dataflow-pipeline/data-parsing.md), and [reporting](dataflow-pipeline/reporting.md) the data. This is primarily done for performance reasons.
-The collection is done in memory of the web server (or webservers if you have multiple web servers in a load-balanced
+The collection is done in memory of the web server (or webservers) if you have multiple web servers in a load-balanced environment.
Storing causes the data to flow from the memory to the database. The memory is free again and can be used for other data. The data is stored in the raw data tables at that moment.
diff --git a/16/umbraco-engage/getting-started/for-developers/content-security-policy-nonce-configuration.md b/16/umbraco-engage/getting-started/for-developers/content-security-policy-nonce-configuration.md
index f57e72d0307..945035299e9 100644
--- a/16/umbraco-engage/getting-started/for-developers/content-security-policy-nonce-configuration.md
+++ b/16/umbraco-engage/getting-started/for-developers/content-security-policy-nonce-configuration.md
@@ -4,9 +4,9 @@ description: >-
nonce to scripts & styles injected by Engage.
---
-# Content Security Policy nonce configuration
+# Content Security Policy (CSP) nonce configuration
-Engage automatically injects different scripts and styles into the returned HTML when requesting content. It also adds the option to set a nonce for the duration of a request to be picked up and added to said scripts and styles. This can be used when a CSP requires a nonce for scripts.
+Engage automatically injects different scripts and styles into the returned HTML when requesting content. It also allows setting a nonce for the duration of a request that can be picked up and added to said scripts and styles. This can be used when a CSP requires a nonce for scripts.
## How to set a nonce
diff --git a/16/umbraco-engage/getting-started/for-developers/troubleshooting-installations.md b/16/umbraco-engage/getting-started/for-developers/troubleshooting-installations.md
index ac4f2ae688d..e8033e103f5 100644
--- a/16/umbraco-engage/getting-started/for-developers/troubleshooting-installations.md
+++ b/16/umbraco-engage/getting-started/for-developers/troubleshooting-installations.md
@@ -16,7 +16,7 @@ The most common reasons for this are:
* Database connectivity issues.
* Incompatible SQL Server version.
-* No COLUMNS STORE index support on Azure SQL lower than S3.
+* No COLUMNSTORE index support on Azure SQL lower than S3.
### Exception
@@ -47,10 +47,10 @@ await app.BootUmbracoAsync();
#### When running on Azure SQL tier lower than S3
-Azure SQL lower than S3 doesn't support creating COLUMN STORE indexes. To work around this follow these steps:
+Azure SQL lower than S3 doesn't support creating COLUMNSTORE indexes. To work around this follow these steps:
1. Scale your Azure SQL environment to S3.
2. Restart the site.
3. Scale back to your initial Azure SQL tier.
-The COLUMN STORE indexes are created and can be used in a lower tier.
+The COLUMNSTORE indexes are created and can be used in a lower tier.
diff --git a/16/umbraco-engage/installation/installation.md b/16/umbraco-engage/installation/installation.md
index 191a482a278..e28d8d50145 100644
--- a/16/umbraco-engage/installation/installation.md
+++ b/16/umbraco-engage/installation/installation.md
@@ -129,10 +129,10 @@ The following Google Analytics bridging or blocker script loading types are curr
### Cookie consent
-If you need to influence the default [The Umbraco Engage cookie](../marketers-and-editors/introduction/the-umbraco-engage-cookie.md) behaviour please go [here](../security-and-privacy/gdpr/). Or go to an example [implementation using Cookiebot](../security-and-privacy/gdpr/how-to-become-gdpr-compliant-using-cookiebot.md) which can be used as an example for other cookie consent providers.
+To change the default [Umbraco Engage cookie](../marketers-and-editors/introduction/the-umbraco-engage-cookie.md) behavior, see the [GDPR & EU regulation](../security-and-privacy/gdpr/) article. Alternatively, check the [implementation using Cookiebot](../security-and-privacy/gdpr/how-to-become-gdpr-compliant-using-cookiebot.md), which can serve as a reference for other cookie consent providers.
{% hint style="warning" %}
-If you [change the default cookie behaviour](../developers/introduction/the-umbraco-engage-cookie/) make sure to perform a **client side reload of the initial page after cookie consent**. If this is not done, visitor referrer and/or campaigns will not be tracked.
+If you [change the default cookie behavior](../developers/introduction/the-umbraco-engage-cookie/) make sure to perform a **client side reload of the initial page after cookie consent**. If this is not done, visitor referrer and/or campaigns will not be tracked.
{% endhint %}
### Load balancing and CM / CD environments
diff --git a/16/umbraco-engage/installation/troubleshooting-installs.md b/16/umbraco-engage/installation/troubleshooting-installs.md
index d612934e236..ddf433310e4 100644
--- a/16/umbraco-engage/installation/troubleshooting-installs.md
+++ b/16/umbraco-engage/installation/troubleshooting-installs.md
@@ -48,7 +48,7 @@ Go to a form and add a new question. Do you see this option?
Go to **Engage** -> **Settings** -> **Create a new goal**. Do you see the following option called **Umbraco Forms Submission**?
-
+
If you see both options, Umbraco Forms has been configured correctly. If not, ensure that your development team has installed the additional Umbraco Engage [UmbracoForms NuGet package](https://www.nuget.org/packages/Umbraco.Engage.Forms).
diff --git a/16/umbraco-engage/marketers-and-editors/ab-testing/setting-up-the-ab-test.md b/16/umbraco-engage/marketers-and-editors/ab-testing/setting-up-the-ab-test.md
index 1c631cee10d..410c726d511 100644
--- a/16/umbraco-engage/marketers-and-editors/ab-testing/setting-up-the-ab-test.md
+++ b/16/umbraco-engage/marketers-and-editors/ab-testing/setting-up-the-ab-test.md
@@ -38,7 +38,7 @@ After that, you have to specify the type of test and set up the specific test. I
As a final step, you need to specify which goal you want to measure, as it is all about optimizing for this goal. Set the audience that you want to include in the test.
-
+
## Launching the A/B test
diff --git a/16/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/single-page-ab-test.md b/16/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/single-page-ab-test.md
index 159701f57fd..dac11e5e437 100644
--- a/16/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/single-page-ab-test.md
+++ b/16/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/single-page-ab-test.md
@@ -60,4 +60,4 @@ Finish the steps in the [Settings up the A/B test](../setting-up-the-ab-test.md)
Because of the unique implementation of Umbraco Engage, the content will automatically be updated for this variant.
-The algorithm will determine which variant of the propety needs to be rendered.
+The algorithm will determine which variant of the property needs to be rendered.
diff --git a/16/umbraco-engage/marketers-and-editors/ab-testing/what-is-ab-testing.md b/16/umbraco-engage/marketers-and-editors/ab-testing/what-is-ab-testing.md
index 24da876440c..2366a82ac0b 100644
--- a/16/umbraco-engage/marketers-and-editors/ab-testing/what-is-ab-testing.md
+++ b/16/umbraco-engage/marketers-and-editors/ab-testing/what-is-ab-testing.md
@@ -7,7 +7,7 @@ description: >-
It goes too far to give a total overview of what A/B testing is. There are some great resource out there that can inspire you and can go in real depth what A/B testing is.
-For now we will stick with this explaination: A/B testing is a methodical way of testing (and hopefully improving) your website. By serving multiple versions of a webpage, content block, or website to different visitors, gathering data on which version performs better for a specific goal.
+For now we will stick with this explanation: A/B testing is a methodical way of testing (and hopefully improving) your website. By serving multiple versions of a webpage, content block, or website to different visitors, gathering data on which version performs better for a specific goal.
## Why should you A/B test your website?
@@ -30,4 +30,4 @@ Many books explain the importance of A/B testing and why you should start testin
* Dan Siroker and Pete Koomen. _A/B Testing. The most powerful way to turn clicks into customers_. Hoboken, New Jersey: John Wiley & Sons, Inc., 2013. [Print](https://www.amazon.com/Testing-Most-Powerful-Clicks-Customers/dp/1118792416)
* Chris Goward. _You should test that!_ Indianapolis, Indiana: John Wiley & Sons, Inc., 2013. [Print](https://www.amazon.com/You-Should-Test-That-Optimization/dp/1118301307)
-* Will Kurt. _Bayesian statistics the fun way._ San Fransisco, William Pollock, 2019. [Print](https://www.amazon.com/Bayesian-Statistics-Fun-Will-Kurt/dp/1593279566)
+* Will Kurt. _Bayesian statistics the fun way._ San Francisco, William Pollock, 2019. [Print](https://www.amazon.com/Bayesian-Statistics-Fun-Will-Kurt/dp/1593279566)
diff --git a/16/umbraco-engage/marketers-and-editors/analytics/campaigns.md b/16/umbraco-engage/marketers-and-editors/analytics/campaigns.md
index 7781a52d612..190deaae60b 100644
--- a/16/umbraco-engage/marketers-and-editors/analytics/campaigns.md
+++ b/16/umbraco-engage/marketers-and-editors/analytics/campaigns.md
@@ -11,7 +11,7 @@ In the **Campaigns** tab of the Umbraco Engage, you can view all analytics data
You can add five different parameters to your URLs:
* `utm_source`: Identify the advertiser, site, publication that is sending traffic to your property. For example: google, newsletter4, billboard.
-* `utm_medium`: The advertising or marketing medium. For example: cpc, banner, email newsletter.
+* `utm_medium`: The advertising or marketing medium. For example: Cost Per Click (CPC), banner, email newsletter.
* `utm_campaign`: The individual campaign name, slogan, promo code for a product.
* `utm_term`: Identify paid search keywords. If you are manually tagging paid keyword campaigns, you should also use _utm_term_ to specify the keyword.
* `utm_content`: Used to differentiate similar content or links within the same ad. For example: if you have two call-to-action links within the same email message, you can use _utm_content_ and set different values for each so you can tell which version is more effective.
diff --git a/16/umbraco-engage/marketers-and-editors/analytics/what-is-measured-by-default.md b/16/umbraco-engage/marketers-and-editors/analytics/what-is-measured-by-default.md
index 5e014ac3b85..97ee8d1d8c9 100644
--- a/16/umbraco-engage/marketers-and-editors/analytics/what-is-measured-by-default.md
+++ b/16/umbraco-engage/marketers-and-editors/analytics/what-is-measured-by-default.md
@@ -18,4 +18,4 @@ Serverside the following data is tracked:
With the data collected, the Analytics reports in Umbraco Engage can be visualized. It also allows us to calculate other metrics, such as conversion rates, bounce rates, and landing & exit pages.
-If you [include the clientside collection script](../../developers/analytics/client-side-events-and-additional-javascript-files/) as well, you can also capture behavioural data of your visitors.
+By [including the clientside collection script](../../developers/analytics/client-side-events-and-additional-javascript-files/), you can also capture visitor behavior data.
diff --git a/16/umbraco-engage/marketers-and-editors/personalization/creating-a-segment.md b/16/umbraco-engage/marketers-and-editors/personalization/creating-a-segment.md
index bfa6d2715b1..1e4c9985658 100644
--- a/16/umbraco-engage/marketers-and-editors/personalization/creating-a-segment.md
+++ b/16/umbraco-engage/marketers-and-editors/personalization/creating-a-segment.md
@@ -14,7 +14,7 @@ You must first define these segments and then you can start personalizing the we
Segments are created via the Umbraco Engage segment builder, located under the **Personalization** and the **Segments** tab.
-
Segment buillder.
+
Segment builder.
To create a new segment, follow these steps:
diff --git a/16/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/campaign-scoring.md b/16/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/campaign-scoring.md
index e7e9c942d02..318ee8b2ab5 100644
--- a/16/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/campaign-scoring.md
+++ b/16/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/campaign-scoring.md
@@ -19,12 +19,12 @@ Campaigns are automatically scored by using utm-parameters, that you may be alre
Each parameter must be paired with a value that you assign. Each parameter-value pair then contains campaign-related information.
-For example, if you want to link from a newsletter to the pricing page of the umbraco.com, you can use the following parameters:
+For example, if you want to link from a newsletter to the pricing page of the `umbraco.com`, you can use the following parameters:
* `utm_source` = newsletter-july-2024 to identify that this visitor came from this specific newsletter
* `utm_medium` = newsletter to show that the medium was a newsletter
-* `utm_campaign` = more_signups because that newsletter was part of a bigger campaign
-* `utm_content` = bottom_button to identify a specific link in the newsletter
+* `utm_campaign` = `more_signups` because that newsletter was part of a bigger campaign
+* `utm_content` = `bottom_button` to identify a specific link in the newsletter
If you want to use these parameters you'll need to set the URL as:
@@ -72,7 +72,7 @@ An example of this tab could look like this:
In the last row, for example, the `utm_source` is "**Activate account**", `utm_medium` is "**email**" and `utm_content` is **click here to activate your account**. The URL that the visitor used to get to the website looked something like `https://?utm_source=activate account&utm_medium=email&utm_content=click here to activate your account.`
-Every unscored campaign can be assigned to a campaign group by clicking on the "**Assign**" button. If you do that a popup will open that allows you to assign the specific campaign to one of your created campaign groups.
+Every Unscored campaign can be assigned to a campaign group by clicking on the "**Assign**" button. If you do that a popup will open that allows you to assign the specific campaign to one of your created campaign groups.
@@ -86,6 +86,6 @@ Assigning this to "**A campaign group for developers**" ensures all visitors wit
On this tab, you will see all the campaigns that are linked already to a campaign group.
-
Scored campaings.
+
Scored campaigns.
You can assign the campaign to a different campaign group or delete it from the existing campaign group. By deleting it, the campaign will go back to the tab "Unscored campaigns".
diff --git a/16/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/content-scoring.md b/16/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/content-scoring.md
index e760a246cbc..4c872b3ebad 100644
--- a/16/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/content-scoring.md
+++ b/16/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/content-scoring.md
@@ -12,7 +12,7 @@ To do this navigate to a node in Umbraco and open the content app "**Personaliza
Open personalization on content node.
-You can navigate to the tab "**Content scoring**" to score this Umbraco page. Writting your content for a specific set of personas you can assign a score that will be added to this persona or customer journey step.
+You can navigate to the tab "**Content scoring**" to score this Umbraco page. Writing your content for a specific set of personas you can assign a score that will be added to this persona or customer journey step.
Set up the score and save the scoring.
diff --git a/16/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/setting-up-personas.md b/16/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/setting-up-personas.md
index 4b51271ce01..5a802cdd49f 100644
--- a/16/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/setting-up-personas.md
+++ b/16/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/setting-up-personas.md
@@ -14,7 +14,7 @@ Here you can create one or more persona groups, and within each group, you can c
## Personas
-Personas are an important concept for implicit personalization in Umbraco Engage. A persona is an archetypical user whose goals, needs, and characteristics represent a group of visitors to your website. By creating personas you can define behavior on your website and personalize the website experience depending on the persona's needs.
+Personas are an important concept for implicit personalization in Umbraco Engage. A persona is an archetypal user whose goals, needs, and characteristics represent a group of visitors to your website. By creating personas you can define behavior on your website and personalize the website experience depending on the persona's needs.
Creating personas is something that you should do for your website. If it's your first time coming up with personas we always advise creating a maximum of 3 personas.
diff --git a/16/umbraco-engage/marketers-and-editors/personalization/setting-up-personalization.md b/16/umbraco-engage/marketers-and-editors/personalization/setting-up-personalization.md
index ea89c83022a..3f6b67fbb16 100644
--- a/16/umbraco-engage/marketers-and-editors/personalization/setting-up-personalization.md
+++ b/16/umbraco-engage/marketers-and-editors/personalization/setting-up-personalization.md
@@ -52,7 +52,7 @@ For example, you can specify a different title for this variant:
While previewing the personalization, you will see an extra querystring in the URL: `https:///?engagePreviewAppliedPersonalization=`
-This is only visiblee when previewing your personalization. Once published, visitors will see a single URL, and depending on their segment, they will view different content.
+This is only visible when previewing your personalization. Once published, visitors will see a single URL, and depending on their segment, they will view different content.
After publishing the website, visitors in the segment will see the personalized variant, while others will see the default content.
diff --git a/16/umbraco-engage/marketers-and-editors/profiling/README.md b/16/umbraco-engage/marketers-and-editors/profiling/README.md
index fe0a9d11bf7..1875f3b1c75 100644
--- a/16/umbraco-engage/marketers-and-editors/profiling/README.md
+++ b/16/umbraco-engage/marketers-and-editors/profiling/README.md
@@ -7,7 +7,7 @@ hidden: true
# Profiling
-The **Profiles** section offers an overview of all the visitors that visited your website. Access the profiles section by navigating to the **Engage** section and then to the **Profiles** subsection in the topmenu.
+The **Profiles** section offers an overview of all the visitors that visited your website. Access the profiles section by navigating to the **Engage** section and then to the **Profiles** subsection in the top menu.
diff --git a/16/umbraco-engage/marketers-and-editors/settings/setting-up-goals.md b/16/umbraco-engage/marketers-and-editors/settings/setting-up-goals.md
index d9d29d5a647..924a0d1d497 100644
--- a/16/umbraco-engage/marketers-and-editors/settings/setting-up-goals.md
+++ b/16/umbraco-engage/marketers-and-editors/settings/setting-up-goals.md
@@ -14,7 +14,7 @@ In the Goals menu, you can set up goals and specify their value.
You have a complete overview of all of the goals that are currently set:
-
+
From this page, you can edit existing goals or set up new goals.
diff --git a/16/umbraco-engage/security-and-privacy/gdpr/how-to-become-gdpr-compliant-using-cookiebot.md b/16/umbraco-engage/security-and-privacy/gdpr/how-to-become-gdpr-compliant-using-cookiebot.md
index edc96bd9b42..a46ccd5c250 100644
--- a/16/umbraco-engage/security-and-privacy/gdpr/how-to-become-gdpr-compliant-using-cookiebot.md
+++ b/16/umbraco-engage/security-and-privacy/gdpr/how-to-become-gdpr-compliant-using-cookiebot.md
@@ -4,7 +4,7 @@ description: >-
with GDPR.
---
-# How to become GDPR compliant using cookiebot
+# How to become GDPR compliant using Cookiebot
Integrating a cookie consent banner service such as CookieBot allows you to configure parts of Umbraco Engage based on [user consent](../../developers/introduction/the-umbraco-engage-cookie/module-permissions.md).
diff --git a/16/umbraco-engage/support.md b/16/umbraco-engage/support.md
index 41e49ea9769..f7d041868f4 100644
--- a/16/umbraco-engage/support.md
+++ b/16/umbraco-engage/support.md
@@ -9,4 +9,4 @@ description: >-
Seeking support or guidance? Go to [umbraco.com](https://umbraco.com) and look for the friendly speech bubble icon in the bottom right corner of your screen. Click on it, and you can open a new support request.
-To be able to get all the information about your Umbraco support account, make sure you are logged in before creating a support request.
+To get all the information about your Umbraco Support account, make sure you are logged in before creating a support request.
diff --git a/16/umbraco-engage/tutorials/how-to-get-started-with-personalization.md b/16/umbraco-engage/tutorials/how-to-get-started-with-personalization.md
index 4537481245d..008d414c1c0 100644
--- a/16/umbraco-engage/tutorials/how-to-get-started-with-personalization.md
+++ b/16/umbraco-engage/tutorials/how-to-get-started-with-personalization.md
@@ -9,7 +9,7 @@ description: >-
Personalization in Umbraco Engage, and in general, requires building personas, segmenting visitors, and collecting lots of data. Follow this tutorial to get started with all of this.
{% hint style="info" %}
-A big part of personalizing your website content is collecting data to use as a base for personalization. Steps 1-4 take you through setting Enage up to collect the required data. You need to collect enough data to move on to step 5.
+A big part of personalizing your website content is collecting data to use as a base for personalization. Steps 1-4 take you through setting Engage up to collect the required data. You need to collect enough data to move on to step 5.
{% endhint %}
## Tutorial Content
diff --git a/16/umbraco-engage/upgrading/migrate-from-umarketingsuite.md b/16/umbraco-engage/upgrading/migrate-from-umarketingsuite.md
index ebb4ce8bd37..6ede83b170a 100644
--- a/16/umbraco-engage/upgrading/migrate-from-umarketingsuite.md
+++ b/16/umbraco-engage/upgrading/migrate-from-umarketingsuite.md
@@ -15,7 +15,7 @@ Since the latest version of uMarketingSuite runs on Umbraco 13, upgrading to Umb
**Important:** This migration guide does **not** cover the upgrade process from Umbraco 13 to 16. For guidance on upgrading Umbraco CMS, see the [Version Specific Upgrades](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/upgrading/version-specific#id-13.latest-to-the-latest-version) article in the Umbraco CMS Documentation.
{% endhint %}
-While it’s technically possible to migrate directly from uMarketingSuite on Umbraco 13 to Umbraco Engage on Umbraco 16, it is recommended to split the process:
+Migrating directly from uMarketingSuite on Umbraco 13 to Umbraco Engage on Umbraco 16 is technically possible. However, it is recommended to split the process:
* First, use this guide to migrate from uMarketingSuite to Umbraco Engage while still on Umbraco 13.
* Then, upgrade both the CMS and the Engage package to version 16.
@@ -59,7 +59,7 @@ Are you using separate databases for uMarketingSuite and Umbraco? In that case,
Run this script on your locally restored database to prepare for the migration.
{% endfile %}
-2. Verify that uMarketingSuite & uMarketingSuite addon version checks return the expected results.
+2. Verify that uMarketingSuite & uMarketingSuite add-on version checks return the expected results.
3. Verify that the uMarketingSuite table integrity check returns the expected results.
{% hint style="info" %}
@@ -198,7 +198,7 @@ You can find additional information on migrating the add-on packages for Umbraco
UI Changes
* The uMarketingSuite folder within `App_Plugins` has been renamed from `uMarketingSuite` to `Umbraco.Engage`. This folder is no longer stored on disk due to the use of the `Umbraco.Engage.StaticAssets` package.
-* The Umbraco Forms addon folder within `App_Plugins` has been renamed from `uMarketingSuite.UmbracoForms` to `Umbraco.Engage.Forms`. This folder is no longer stored on disk due to changes in version 16 of the `Umbraco.Engage.Forms` package.
+* The Umbraco Forms add-on folder within `App_Plugins` has been renamed from `uMarketingSuite.UmbracoForms` to `Umbraco.Engage.Forms`. This folder is no longer stored on disk due to changes in version 16 of the `Umbraco.Engage.Forms` package.
* The Cockpit Partial View has been moved from `Partials/uMarketingSuite/Cockpit` to `Partials/Umbraco.Engage/Cockpit`. This file is no longer stored on disk due to the use of the `Umbraco.Engage.StaticAssets` package.
@@ -388,7 +388,7 @@ dotnet add package Umbraco.Engage.Headless
If you are using the uMarketingSuite.Commerce package, all the commerce data has been migrated to Umbraco Engage using the scripts in Step 4.
-You can install the Umbraco Engage Commerce addon package using the following command:
+You can install the Umbraco Engage Commerce add-on package using the following command:
```bash
dotnet add package Umbraco.Engage.Commerce
diff --git a/16/umbraco-engage/upgrading/version-specific-upgrade-notes.md b/16/umbraco-engage/upgrading/version-specific-upgrade-notes.md
index 2894bf6ede8..7f2e15ecdcb 100644
--- a/16/umbraco-engage/upgrading/version-specific-upgrade-notes.md
+++ b/16/umbraco-engage/upgrading/version-specific-upgrade-notes.md
@@ -16,11 +16,11 @@ When upgrading to a new minor or patch version, learn about the changes in the [
### v16.0.0 (Umbraco Engage v16 Launch)
-With the introduction of Engage version 16, several breaking changes have been introduced to accommodate the transitions between multiple major versions of the core CMS.
+With the introduction of Engage version 16, breaking changes have been introduced to accommodate the transitions between multiple major versions of the core CMS.
#### Clientside Analytics
-Engage includes various optional scripts that can be included in the front-end, which interact with various API endpoints. Some of these endpoints have changed. If any firewall rules are in place involving the front-end reaching Umbraco APIs, the following paths need to be allowed through:
+Engage includes different optional scripts that can be included in the front-end, which interact with different API endpoints. Some of these endpoints have changed. If any firewall rules are in place involving the front-end reaching Umbraco APIs, the following paths need to be allowed through:
```
/umbraco/engage/pagedata/collect
@@ -30,8 +30,8 @@ Engage includes various optional scripts that can be included in the front-end,
#### Umbraco Member Detection & Storage
-The detection and storage of logged-in Umbraco Members have changed significantly between versions 13 and 16 of Engage. In older versions of v13, any kind of login claim would be detected as a valid member, causing the visitor to be marked as 'Identified' and get linked to any member claim ID. This has changed over various minor versions of v13 to only allow for Umbraco Members to prevent other login methods from interfering with Engage.
+The detection and storage of logged-in Umbraco Members have changed between versions 13 and 16 of Engage. In older v13 versions, any login claim was detected as a valid member. This caused visitors to be marked as 'Identified' and linked to the claim ID. This has changed over minor versions of v13 to only allow for Umbraco Members to prevent other login methods from interfering with Engage.
-Engage v16 will strictly enforce the storage of Umbraco Members only, attempting to update any existing pageview data that detects a logged-in member. This migration includes switching from integer IDs to GUID keys, validating the GUIDs against the existing Umbraco Members, and enforcing the datatype to a unique identifier.
+Engage v16 will strictly enforce the storage of Umbraco Members only, attempting to update any existing pageview data that detects a logged-in member. This migration switches from integer IDs to GUID keys. It validates the GUIDs against existing Umbraco Members and enforces the datatype as a unique identifier.
This **will** result in data loss if non-Umbraco members or no longer existing members were stored in the `MembershipProviderKey` column in the `umbracoEngageAnalyticsPageview` table.
 (1).png)
