Skip to content

Commit 48c6ff3

Browse files
committed
Fixed vale errors
1 parent 0daf631 commit 48c6ff3

31 files changed

+47
-48
lines changed

16/umbraco-engage/SUMMARY.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@
133133
* [Retention periods of data](security-and-privacy/retention-periods-of-data.md)
134134
* [Anonymization](security-and-privacy/anonymization.md)
135135
* [GDPR & EU regulation](security-and-privacy/gdpr/README.md)
136-
* [How to become GDPR compliant using cookiebot](security-and-privacy/gdpr/how-to-become-gdpr-compliant-using-cookiebot.md)
136+
* [How to become GDPR compliant using Cookiebot](security-and-privacy/gdpr/how-to-become-gdpr-compliant-using-cookiebot.md)
137137
* [How it works](security-and-privacy/how-it-works.md)
138138

139139
## Tutorials

16/umbraco-engage/developers/ab-testing/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
description: Umbraco Engage offers multiple ways for performaing A/B tests on your website.
2+
description: Umbraco Engage offers multiple ways for performing A/B tests on your website.
33
hidden: true
44
---
55

16/umbraco-engage/developers/analytics/location.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -111,5 +111,4 @@ From the country, you can drill down to the city. This will then filter the disp
111111

112112
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.
113113

114-
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.
115-
114+
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.

16/umbraco-engage/developers/analytics/what-is-measured-by-default.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,4 +32,4 @@ For a request to be considered a valid pageview, the following conditions have t
3232

3333
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.
3434

35-
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.
35+
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.

16/umbraco-engage/developers/headless/using-the-marketing-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ An example of configuration in `AppSettings.json` file:
4646
}
4747
```
4848

49-
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.
49+
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.
5050

5151
| **Key** | **Description** | **Default Value** |
5252
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |

16/umbraco-engage/developers/introduction/dataflow-pipeline/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,4 +12,4 @@ description: >-
1212
3. [Data processing](data-parsing.md): The data is processed at a later moment to make it more efficient and normalized
1313
4. [Data reporting](reporting.md): Finally the data is reported within Umbraco Engage
1414

15-
The concept of this dataflow is the most important concept to grasp when using Umbraco Engage.
15+
The concept of this Dataflow is the most important concept to grasp when using Umbraco Engage.

16/umbraco-engage/developers/introduction/dataflow-pipeline/data-collection.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ There are different [configuration options](../../settings/configuration.md) to
3737

3838
* 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.
3939
* The IP Address is anonymized by default. There is an option to change this
40-
* 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.
40+
* 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.
4141

4242
## Client-side collection
4343

16/umbraco-engage/developers/introduction/dataflow-pipeline/data-parsing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,5 +61,5 @@ If using [Umbraco in a load-balanced configuration](../../../getting-started/for
6161

6262
There is probably no or little reason to store this data forever. That is why we have two settings to clean up this data.
6363

64-
* 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.
64+
* 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.
6565
* 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.

16/umbraco-engage/developers/introduction/dataflow-pipeline/data-storage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ The lower the value you set, the less memory Umbraco Engage uses on your web ser
2525

2626
## Data storage
2727

28-
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.
28+
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.
2929

3030
The data collected from clientside events is stored in the table `umbracoEngageAnalyticsRawClientSideData`.
3131

16/umbraco-engage/developers/introduction/performance.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,9 @@ Umbraco Engage is optimized for performance and you configure it to optimize the
1010

1111
## Separate processes for storing, parsing, and reporting
1212

13-
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.
13+
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.
1414

15-
The collection is done in memory of the web server (or webservers if you have multiple web servers in a load-balanced
15+
The collection is done in memory of the web server (or webservers) if you have multiple web servers in a load-balanced environment.
1616

1717
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.
1818

0 commit comments

Comments
 (0)