From f009618ad8c7a0e51d1b6c98a4915e24ca208f05 Mon Sep 17 00:00:00 2001
From: Andy Piper <andypiper@users.noreply.github.com>
Date: Wed, 3 Dec 2025 20:09:34 +0000
Subject: [PATCH] Cleaning up some typos and formatting

Signed-off-by: Andy Piper <andypiper@users.noreply.github.com>
---
 _docs/10_general/02_locations.md                 | 8 ++++----
 _docs/10_general/10_what_we_collect.md           | 2 +-
 _docs/20_install-script/00_light.md              | 2 +-
 _docs/20_install-script/02_custom.md             | 4 ++--
 _docs/20_install-script/10_without-javascript.md | 2 +-
 _docs/20_script-settings/03_overwrite-domain.md  | 2 +-
 _docs/20_script-settings/03_overwrite-path.md    | 2 +-
 _docs/20_script-settings/04_ignore-pages.md      | 2 +-
 _docs/20_script-settings/40_strict-utms.md       | 2 +-
 _docs/30_features/42-exclude-your-ip.md          | 2 +-
 _docs/31_integrations/00_create-plugin.md        | 4 ++--
 _docs/31_integrations/00_swift.md                | 2 +-
 _docs/33_explained/10_team-roles.md              | 2 +-
 _docs/33_explained/20_platform-integration.md    | 2 +-
 _docs/36_legal/00_introduction.md                | 2 +-
 _docs/36_legal/06_data-security-and-ownership.md | 6 +++---
 _docs/50_api/01_introduction.md                  | 2 +-
 _docs/50_api/15_stats-api.md                     | 8 ++++----
 _docs/50_api/20_export-data-points.md            | 6 +++---
 _docs/50_api/35_admin.md                         | 2 +-
 _docs/50_api/40_cors-jsonp.md                    | 2 +-
 _docs/50_api/50_helpers.md                       | 2 +-
 _docs/55_events/00_inline-events.md              | 2 +-
 _docs/55_events/00_send-events-in-ruby.md        | 2 +-
 _docs/55_events/15_metadata.md                   | 6 +++---
 25 files changed, 39 insertions(+), 39 deletions(-)

diff --git a/_docs/10_general/02_locations.md b/_docs/10_general/02_locations.md
index 340b6e8..4c7efbe 100644
--- a/_docs/10_general/02_locations.md
+++ b/_docs/10_general/02_locations.md
@@ -18,11 +18,11 @@ We never collect IP addresses or any form of personal data. Therefore, there is
 
 ## Data Hosting Infrastructure
 
-The data we collect belongs to you. We only collect non-personal data and don't share the data with third parties or transfer it overseas. Your website data never leaves The Netherlands and, therefore, the E.U.  Also, no other third-party vendors have access to any data outside the hosting company that owns the servers on which the data is stored.
+The data we collect belongs to you. We only collect non-personal data and don't share the data with third parties or transfer it overseas. Your website data never leaves The Netherlands and, therefore, the EU.  Also, no other third-party vendors have access to any data outside the hosting company that owns the servers on which the data is stored.
 
-The data is hosted fully secured and encrypted in The Netherlands, [part of the EU](https://european-union.europa.eu/principles-countries-history/country-profiles/netherlands_en). [Worldstream](https://www.worldstream.com/) and [Leaseweb](https://www.leaseweb.com/) own the servers, both dutch companies that adhere to EU law and GDPR policy. 
+The data is hosted fully secured and encrypted in The Netherlands, [part of the EU](https://european-union.europa.eu/principles-countries-history/country-profiles/netherlands_en). [Worldstream](https://www.worldstream.com/) and [Leaseweb](https://www.leaseweb.com/) own the servers, both Dutch companies that adhere to EU law and GDPR policy. 
 
-We use a CDN for most of our customers. The CDN is called Bunny CDN and is part of a company called [BunnyWay](https://bunny.net/cdn/), located in Slovenia, [part of the EU](https://european-union.europa.eu/principles-countries-history/country-profiles/slovenia_en). Simple Analytics and Bunny CDN have signed a written agreement protecting data exits. 
+We use a CDN for most of our customers. The CDN is called Bunny CDN and is part of a company called [BunnyWay](https://bunny.net/cdn/), located in Slovenia, [part of the EU](https://european-union.europa.eu/principles-countries-history/country-profiles/slovenia_en). Simple Analytics and Bunny CDN have signed a written agreement protecting data exits.
 
 ## Data Security
 
@@ -38,7 +38,7 @@ We don't transfer your visitors' data outside of the EU. This includes no data t
 
 The EU-US Privacy Shield Framework was invalidated by the Court of Justice of the European Union. Called the ["Schrems II"](https://iapp.org/news/a/the-schrems-ii-decision-eu-us-data-transfers-in-question/) decision, which refers to the ruling that transferring data to US providers violates GDPR regulation. This has been the ruling since July 2020. We have been compliant since the start of our business in 2018.
 
-Are you coming from Google Analytics? Please read our blog post on the [differences between Google Analytics and Simple Analytics](https://www.simpleanalytics.com/blog/why-simple-analytics-is-a-great-alternative-to-google-analytics). You can import your Google Anlaytics data into Simple Analytics.
+Are you coming from Google Analytics? Please read our blog post on the [differences between Google Analytics and Simple Analytics](https://www.simpleanalytics.com/blog/why-simple-analytics-is-a-great-alternative-to-google-analytics). You can import your Google Analytics data into Simple Analytics.
 
 ## Protecting your privacy
 
diff --git a/_docs/10_general/10_what_we_collect.md b/_docs/10_general/10_what_we_collect.md
index 10bf5fa..4038b2e 100644
--- a/_docs/10_general/10_what_we_collect.md
+++ b/_docs/10_general/10_what_we_collect.md
@@ -159,7 +159,7 @@ We track these UTM codes:
 - `utm_medium` (e.g.: `search`)
 - `utm_campaign` (e.g.: `get_customers_02`)
 - `utm_content` (e.g.: `sidebar`)
-- _`utm_term` (this is deprecated as it is intented to contain user data)_
+- _`utm_term` (this is deprecated as it is intended to contain user data)_
 
 Website owners can add a URL parameter to links to their website, like `ref=...`, `source=...` or `utm_source=...`. These are all saved as the `utm_source`. Read more on [using URL parameters](/how-to-use-url-parameters).
 
diff --git a/_docs/20_install-script/00_light.md b/_docs/20_install-script/00_light.md
index e76a9fd..51cc4dd 100644
--- a/_docs/20_install-script/00_light.md
+++ b/_docs/20_install-script/00_light.md
@@ -27,7 +27,7 @@ Source: [giftofspeed.com](https://www.giftofspeed.com/gzip-test/) for Brotli, [a
 
 ## Features
 
-Obviously not all features are available in our light script. Here an comparison of both versions:
+Obviously not all features are available in our light script. Here is a comparison of both versions:
 
 | Feature                                         | `latest.js` | `light.js` |
 | :---------------------------------------------- | :---------: | :--------: |
diff --git a/_docs/20_install-script/02_custom.md b/_docs/20_install-script/02_custom.md
index caee013..5cdf65f 100644
--- a/_docs/20_install-script/02_custom.md
+++ b/_docs/20_install-script/02_custom.md
@@ -5,11 +5,11 @@ permalink: /trigger-custom-page-views
 last_modified_at: 2022-04-14
 ---
 
-Normally you want to trigger a custom page view for _Single Page Apps_ (SPA's) like React, Vue, and Angular. Because pages are not completely reloaded on navigation we need a way to track those navigations as page views.
+Normally you want to trigger a custom page view for _Single Page Apps_ (SPAs) like React, Vue, and Angular. Because pages are not completely reloaded on navigation we need a way to track those navigations as page views.
 
 For some analytics tools like Google Analytics you need to trigger a page view via their script. For Simple Analytics this is different.
 
-> With Simple Analytics there is **no** need to implement anything to detect page views in SPA's. It all works out of the box.
+> With Simple Analytics there is **no** need to implement anything to detect page views in SPAs. It all works out of the box.
 
 <details>
 <summary>Technical explanation</summary>
diff --git a/_docs/20_install-script/10_without-javascript.md b/_docs/20_install-script/10_without-javascript.md
index 105c124..02164f1 100644
--- a/_docs/20_install-script/10_without-javascript.md
+++ b/_docs/20_install-script/10_without-javascript.md
@@ -7,7 +7,7 @@ last_modified_at: 2022-04-14
 
 Normally you would collect page view via our [open source JavaScript](/script). But there are other way to collect those. You can either send data via [your own server](/server-side-tracking) or send it through a pixel (a small GIF image).
 
-> By default we already include a pixel (image) with our `<noscript>` tag. This tag gets executed when a visitor disabled JavaScript in their browser. The pixel inside the tag will still record that page view. The data connected to that page view is limited, but still useful for the overal picture.
+> By default we already include a pixel (image) with our `<noscript>` tag. This tag gets executed when a visitor disabled JavaScript in their browser. The pixel inside the tag will still record that page view. The data connected to that page view is limited, but still useful for the overall picture.
 
 To collect page views with our pixel you can add parameters to the URL of the image:
 
diff --git a/_docs/20_script-settings/03_overwrite-domain.md b/_docs/20_script-settings/03_overwrite-domain.md
index 1eb9020..e75dbf0 100644
--- a/_docs/20_script-settings/03_overwrite-domain.md
+++ b/_docs/20_script-settings/03_overwrite-domain.md
@@ -16,7 +16,7 @@ Make sure to include the our `simpleanalyticscdn.com` script (note the **cdn** p
 <script async data-hostname="" src="https://scripts.simpleanalyticscdn.com/latest.js"></script>
 ```
 
-You see that we added an attribute (`data-hostname=""`) to the script tag and `hostname` param to the `img` tag. If you add your domain to it (eg `example.com`) it will look like this:
+You see that we added an attribute (`data-hostname=""`) to the script tag and `hostname` param to the `img` tag. If you add your domain to it (e.g. `example.com`) it will look like this:
 
 <!-- prettier-ignore -->
 ```html
diff --git a/_docs/20_script-settings/03_overwrite-path.md b/_docs/20_script-settings/03_overwrite-path.md
index 412a9b5..9ebf30c 100644
--- a/_docs/20_script-settings/03_overwrite-path.md
+++ b/_docs/20_script-settings/03_overwrite-path.md
@@ -10,7 +10,7 @@ Let's say you want to change the path of your page views (and events). You have
 
 > You can not overwrite the hash from the URL, only the path.
 
-This is how you set up a `myPathOverwriter`-function for that usecase:
+This is how you set up a `myPathOverwriter`-function for that use case:
 
 ```html
 <script>
diff --git a/_docs/20_script-settings/04_ignore-pages.md b/_docs/20_script-settings/04_ignore-pages.md
index 811662f..1ac7265 100644
--- a/_docs/20_script-settings/04_ignore-pages.md
+++ b/_docs/20_script-settings/04_ignore-pages.md
@@ -38,7 +38,7 @@ If you want to block all these pages you can separate them with a comma:
 
 ## Wildcards
 
-If you need to match a part of a string you need to add an wildcard asterisk (`*`).
+If you need to match a part of a string you need to add a wildcard asterisk (`*`).
 
 Let's say you have these pages:
 
diff --git a/_docs/20_script-settings/40_strict-utms.md b/_docs/20_script-settings/40_strict-utms.md
index de0d040..1092608 100644
--- a/_docs/20_script-settings/40_strict-utms.md
+++ b/_docs/20_script-settings/40_strict-utms.md
@@ -6,7 +6,7 @@ created_at: 2022-07-26
 last_modified_at: 2022-07-26
 ---
 
-When collecting UTM codes, we allow to skip the `utm_` part:
+When collecting UTM codes, we allow you to skip the `utm_` part:
 
 - `utm_source` / `source` / `ref`
 - `utm_medium` / `medium`
diff --git a/_docs/30_features/42-exclude-your-ip.md b/_docs/30_features/42-exclude-your-ip.md
index 559a45d..3074d66 100644
--- a/_docs/30_features/42-exclude-your-ip.md
+++ b/_docs/30_features/42-exclude-your-ip.md
@@ -7,7 +7,7 @@ last_modified_at: 2025-01-09
 
 This feature allows you to exclude specific IP addresses from being tracked or block your own visits locally on your computer by modifying its hosts file. Excluded IPs or blocked domains ensure visits from internal users or other known sources don’t impact your analytics data. This is helpful for maintaining cleaner, more accurate insights.
 
-## Block IP's in the dashboard
+## Block IPs in the dashboard
 
 The exclusion applies only to visits from the moment you save the IP addresses. Previous visits from these IPs will remain in your analytics data. To ensure privacy, we never store the IP addresses of visitors. The only IPs stored are the ones you manually input into this feature. Currently, only IPv4 addresses are supported.
 
diff --git a/_docs/31_integrations/00_create-plugin.md b/_docs/31_integrations/00_create-plugin.md
index 58a6339..d88bfe2 100644
--- a/_docs/31_integrations/00_create-plugin.md
+++ b/_docs/31_integrations/00_create-plugin.md
@@ -58,7 +58,7 @@ Custom settings should be specified like this: `customSettings: { collectDarkMod
 
 A few examples: WordPress, Drupal, Google Tag Manager, and Cloudflare.
 
-The settings below should be changable via the UI of the plugin. All changed settings need to be passed to the `<script>`-tag. For example:
+The settings below should be changeable via the UI of the plugin. All changed settings need to be passed to the `<script>`-tag. For example:
 
 <!-- prettier-ignore -->
 ```html
@@ -111,7 +111,7 @@ In the UI of the System plugin, we need to be able to change all settings. See h
 
 ### System plugin checklist
 
-- [ ] [All settings](#settings) below are changable via the UI of the plugin
+- [ ] [All settings](#settings) below are changeable via the UI of the plugin
 - [ ] Settings are hidden by default (if possible)
 - [ ] Add ignore admins feature (if possible)
 - [ ] Allow custom settings (key, value)
diff --git a/_docs/31_integrations/00_swift.md b/_docs/31_integrations/00_swift.md
index 4b384d7..68b3db4 100644
--- a/_docs/31_integrations/00_swift.md
+++ b/_docs/31_integrations/00_swift.md
@@ -56,7 +56,7 @@ SimpleAnalytics.shared.track(path: ["detailview", "item1", "edit"])
 This will be converted to a pageview on `/detailview/item1/edit` on Simple Analytics.
 
 ### Tracking Events
-Use events to track interactions or noticable events like errors or success on a page.
+Use events to track interactions or noticeable events like errors or success on a page.
 ```swift
 SimpleAnalytics.shared.track(event: "logged in")
 ```
diff --git a/_docs/33_explained/10_team-roles.md b/_docs/33_explained/10_team-roles.md
index a6de8cf..30e4141 100644
--- a/_docs/33_explained/10_team-roles.md
+++ b/_docs/33_explained/10_team-roles.md
@@ -21,7 +21,7 @@ Analysts play a crucial role in working with the dashboards, goals, and events.
 
 ## Developer
 
-Developers focus on the technical aspects of the analytics dashboard. They can do everything that an analyist can and more. They can add websites to the team, and modify website settings such as visibility (public/private), custom domain, and alerts for no traffic. Additionally, developers have the authority to reset website data, which can be useful during significant updates or troubleshooting.
+Developers focus on the technical aspects of the analytics dashboard. They can do everything that an analyst can and more. They can add websites to the team, and modify website settings such as visibility (public/private), custom domain, and alerts for no traffic. Additionally, developers have the authority to reset website data, which can be useful during significant updates or troubleshooting.
 
 ## Finance Manager
 
diff --git a/_docs/33_explained/20_platform-integration.md b/_docs/33_explained/20_platform-integration.md
index 344347d..84387a7 100644
--- a/_docs/33_explained/20_platform-integration.md
+++ b/_docs/33_explained/20_platform-integration.md
@@ -32,7 +32,7 @@ The only thing that's required, is enabling this script somewhere in the `<body>
 ```
 
 - *`<customer_domain>`* (required) is the stable identifier you create for that site on day one. Usually this is `customerxxx.yourplatform.com`, or `customerdomain.com`. Keep it even if the user changes domains later. It's also the hostname the Simple Analytics users will see in their dashboard.
-- *`<your-platform-name>`* (required) is a unique name of your platform (eg.: `netlify`, `partner.com`, `kennis.shop`). This helps us linking all domains to your platform. Allowing us to give your users tailored instructions.
+- *`<your-platform-name>`* (required) is a unique name of your platform (e.g.: `netlify`, `partner.com`, `kennis.shop`). This helps us linking all domains to your platform. Allowing us to give your users tailored instructions.
 - *`<affiliate-code>`* (optional) is a unique code you can get from us which we use to attach it to every hit so new sign ups are credited to your account. This is optional.
 
 ## Optional event tracking
diff --git a/_docs/36_legal/00_introduction.md b/_docs/36_legal/00_introduction.md
index aabb734..adcb09f 100644
--- a/_docs/36_legal/00_introduction.md
+++ b/_docs/36_legal/00_introduction.md
@@ -43,6 +43,6 @@ You can find more information about the data we collect [here](/data-collection)
 
 Your data are **fully encrypted** on our dedicated servers. We only rely on **European, GDPR-compliant providers** to ensure that your data are handled as safely as possible.
 
-We retain your data as long as your Simple Analytics account is active (and in correspondance to your subscription plan) and never share the data with third parties. **You control your data** and can export it at any time.
+We retain your data as long as your Simple Analytics account is active (and in correspondence to your subscription plan) and never share the data with third parties. **You control your data** and can export it at any time.
 
 You can find out more about our security and ownership policies [here](/data-security-and-ownership).
diff --git a/_docs/36_legal/06_data-security-and-ownership.md b/_docs/36_legal/06_data-security-and-ownership.md
index 99ec8c6..8371b8f 100644
--- a/_docs/36_legal/06_data-security-and-ownership.md
+++ b/_docs/36_legal/06_data-security-and-ownership.md
@@ -14,7 +14,7 @@ We do everything in our power to keep your data safe. We collect the bare minimu
 
 ## Data Hosting Infrastructure
 
-The data we collect belongs to you. We only collect non-personal data and don’t share the data with third parties or transfer it overseas. Your website data never leaves the Netherlands and, therefore, the E.U. Also, no service providers receive any data except for our hosting provider- who is under binding obligations of confidentiality.
+The data we collect belongs to you. We only collect non-personal data and don’t share the data with third parties or transfer it overseas. Your website data never leaves the Netherlands and, therefore, the EU. Also, no service providers receive any data except for our hosting provider- who is under binding obligations of confidentiality.
 
 The data is hosted fully secured and encrypted in The Netherlands, [part of the EU](https://european-union.europa.eu/principles-countries-history/country-profiles/netherlands_en). [Worldstream](https://www.worldstream.com/) and [Leaseweb](https://www.leaseweb.com/) own the servers, both Dutch companies that adhere to EU law and GDPR policy.
 
@@ -22,7 +22,7 @@ We use a CDN for most of our customers. The CDN is called Bunny CDN and is part
 
 ## Data Security
 
-[Simple Analytics](https://simpleanalytics.com/) (and our hosting parties) possess organizational and technical measures to protect the data. Customer data is encrypted both at rest and in transit. Only Simple Analytics holds the decryption keys, ensuring data confidentiality. Even our hosting providers cannot access the data in the clear. Any questions related to our security policy and measures can be sent to info@simpleanalytics.com
+[Simple Analytics](https://simpleanalytics.com/) (and our hosting parties) possess organizational and technical measures to protect the data. Customer data is encrypted both at rest and in transit. Only Simple Analytics holds the decryption keys, ensuring data confidentiality. Even our hosting providers cannot access the data in the clear. Any questions related to our security policy and measures can be sent to <info@simpleanalytics.com>
 
 ## Data Retention
 
@@ -42,7 +42,7 @@ We give customers full ownership and value from their data. Our plugins seamless
 
 Simple Analytics makes no claim over your data. We do not store, sell, or use it for our purposes. **Your data belongs to you**.
 
-Your subscription pays for the service - not your data. We are an independently funded company with no ties to large corporations or the ad tech industry and do not use your data for marketing, for retargeting, for developing other services, and so on. 
+Your subscription pays for the service - not your data. We are an independently funded company with no ties to large corporations or the ad tech industry and do not use your data for marketing, for retargeting, for developing other services, and so on.
 
 ## We Don’t Sell Your Data
 
diff --git a/_docs/50_api/01_introduction.md b/_docs/50_api/01_introduction.md
index 921e862..78a87af 100644
--- a/_docs/50_api/01_introduction.md
+++ b/_docs/50_api/01_introduction.md
@@ -31,7 +31,7 @@ There are a few ways to interact with our API. We have the Stats API for aggrega
      </a>
 </div>
 
-Depending on the public settings of a website you'll need to autenticate. Learn [how to authenticate with Simple Analytics APIs](/api/authenticate).
+Depending on the public settings of a website you'll need to authenticate. Learn [how to authenticate with Simple Analytics APIs](/api/authenticate).
 
 <style>
      .apis {
diff --git a/_docs/50_api/15_stats-api.md b/_docs/50_api/15_stats-api.md
index 2a67c91..eb27ce5 100644
--- a/_docs/50_api/15_stats-api.md
+++ b/_docs/50_api/15_stats-api.md
@@ -33,18 +33,18 @@ The complete list of all query params you can use with the latest Stats API.
 
 - `version` the version of the API (the latest version is `{{ site.api_version }}`)
 - `start` the start date with this format `YYYY-MM-DD` (defaults to 1 month ago)
-- `end` the end data with above format (defaults to today)
+- `end` the end date with the above format (defaults to today)
 - `limit` a limit for the fields (1-1000)
 - `timezone` a valid time zone like `Europe/Amsterdam` (with capitals)
 - `info` shows more information about fields in the response (defaults to true)
 - `callback` wraps the response in a callback for [JSONP](https://en.wikipedia.org/wiki/JSONP)
 - [`events` a list of specified events and how much they occurred](#events)
 - `interval` for histogram field: `hour`, `day`, `week`, `month`, or `year` (`hour` added in version 6)
-- `fields` a comma seperated list of fields you want to get returned:
+- `fields` a comma separated list of fields you want to get returned:
   - `pageviews` the total amount of page views in the specified period
   - `visitors` the total amount of visitors (unique page views) in the specified period
   - `histogram` an array with page views and visitors per day
-  - `pages` a comma seperated list of pages you want to get stats for
+  - `pages` a comma separated list of pages you want to get stats for
   - `countries` a list of country codes
   - `referrers` a list of referrers (normalized)
   - `utm_sources` a list of UTM sources
@@ -76,7 +76,7 @@ You can filter the returned data. Here is the list of filters you can use.
 - `utm_content` filter by a UTM content
 - `utm_term` filter by a UTM term
 - `browser_name` filter by a browser name
-- `os_name` filter by a OS name
+- `os_name` filter by an OS name
 - `device_type` filter by a device type (mobile, tablet, desktop, tv)
 
 These filters don't have effect on the `events` query parameter.
diff --git a/_docs/50_api/20_export-data-points.md b/_docs/50_api/20_export-data-points.md
index b860039..30a3953 100644
--- a/_docs/50_api/20_export-data-points.md
+++ b/_docs/50_api/20_export-data-points.md
@@ -23,7 +23,7 @@ When using the API, it's recommended [to generate the export URL](/api/helpers#g
 
 | Field               | Type    | Description                                                                                                                                                |
 | ------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| added_unix          | number  | The time of the page view in unix time format                                                                                                              |
+| added_unix          | number  | The time of the page view in UNIX time format                                                                                                              |
 | added_iso           | date    | The time of the page view in ISO8601 format                                                                                                                |
 | hostname            | string  | The hostname of the website                                                                                                                                |
 | hostname_original   | string  | When the hostname is overwritten, we store the original hostname                                                                                           |
@@ -86,7 +86,7 @@ In short: apply an `Api-Key`-header where the key starts with `sa_api_key_...` a
 
 ## Selecting fields
 
-You can specify all fields you like to export. Add them as a comma seperated list (e.g.: `&fields=added_iso,hostname,path`).
+You can specify all fields you like to export. Add them as a comma separated list (e.g.: `&fields=added_iso,hostname,path`).
 
 <details>
 <summary>Request example (for developers)</summary>
@@ -145,7 +145,7 @@ Because metadata fields are defined by the user, we don't know the fields upfron
 
 Fields in the API and exporter have a type appended to them. You can see fields like `metadata.fieldname_text`, `metadata.fieldname_date`, `metadata.fieldname_bool`, or `metadata.fieldname_int` (where fieldname is a user-defined name). Some metadata fields can have both, for example, `metadata.projectID_text` and `metadata.projectID_int`. If a text looks like a number, we convert it to an integer and we keep the text version.
 
-When you see something prefixed with `metadata.sa_urlparam_`, it's a paramter from the [allowed URL parameters feature](/allow-params).
+When you see something prefixed with `metadata.sa_urlparam_`, it's a parameter from the [allowed URL parameters feature](/allow-params).
 
 ## Event counts
 
diff --git a/_docs/50_api/35_admin.md b/_docs/50_api/35_admin.md
index 5adb930..d8c45d7 100644
--- a/_docs/50_api/35_admin.md
+++ b/_docs/50_api/35_admin.md
@@ -46,7 +46,7 @@ curl -X "POST" "http://localhost:3000/api/websites/add" \
 
 ### Labels
 
-If you want to keep track of your websites in a different way. A label could help. This is how that looks at the websites overview page:
+If you want to keep track of your websites in a different way, a label could help. This is how a labels looks on the websites overview page:
 
 <img loading="lazy" src="https://assets.simpleanalytics.com/docs/dashboard/labels-in-website-overview.png" alt="Simple Analytics websites overview with custom labels" class="border">
 
diff --git a/_docs/50_api/40_cors-jsonp.md b/_docs/50_api/40_cors-jsonp.md
index 9a6b895..b99fa58 100644
--- a/_docs/50_api/40_cors-jsonp.md
+++ b/_docs/50_api/40_cors-jsonp.md
@@ -25,4 +25,4 @@ $.ajax({
 });
 ```
 
-We append the `Access-Control-Allow-Origin`-header with the `*`-value , so any modern browser should accept the request without any effort.
+We append the `Access-Control-Allow-Origin`-header with the `*`-value, so any modern browser should accept the request without any effort.
diff --git a/_docs/50_api/50_helpers.md b/_docs/50_api/50_helpers.md
index 68bd0e2..9937475 100644
--- a/_docs/50_api/50_helpers.md
+++ b/_docs/50_api/50_helpers.md
@@ -10,7 +10,7 @@ We added a few helpers to make it easier to work with our API.
 
 ## Time zones
 
-In all requests you can specify your time zone. In the Stats API we default to your website setting, in the Export APIs we default to UTC. Speficy your time zone to always get the same results.
+In all requests you can specify your time zone. In the Stats API we default to your website setting, in the Export APIs we default to UTC. Specify your time zone to always get the same results.
 
 A list of valid time zones can be found at the Wikipedia page ["List of tz database time zones"](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List). For example, `Europe/Amsterdam` is a valid time zone. You should specify the time zone like this in your requests: `timezone=UTC`.
 
diff --git a/_docs/55_events/00_inline-events.md b/_docs/55_events/00_inline-events.md
index 98602ed..e09b423 100644
--- a/_docs/55_events/00_inline-events.md
+++ b/_docs/55_events/00_inline-events.md
@@ -31,7 +31,7 @@ To track a click, add `data-simple-event="event_name"` to any clickable elemen
 
 Tracking form submissions
 
-Simply put `data-simple-event="form_name"` on your form tag. When the user submits, the script send an event with the name of the form and the text of the submit button, then submits the form.
+Simply put `data-simple-event="form_name"` on your form tag. When the user submits, the script sends an event with the name of the form and the text of the submit button, then submits the form.
 
 ```html
 <form action="/signup" data-simple-event="signup_form">
diff --git a/_docs/55_events/00_send-events-in-ruby.md b/_docs/55_events/00_send-events-in-ruby.md
index 2611770..9b970b8 100644
--- a/_docs/55_events/00_send-events-in-ruby.md
+++ b/_docs/55_events/00_send-events-in-ruby.md
@@ -24,7 +24,7 @@ def self.trigger(event_name)
   new.trigger(event_name)
 end
 
-# EventData makes sure the data is corrent when sending to
+# EventData makes sure the data is correct when sending to
 # API endpoint
 class EventData
   attr_reader: version,: ua,: platform,: hostname,: date,: events
diff --git a/_docs/55_events/15_metadata.md b/_docs/55_events/15_metadata.md
index c9404a8..4423fcc 100644
--- a/_docs/55_events/15_metadata.md
+++ b/_docs/55_events/15_metadata.md
@@ -97,11 +97,11 @@ You can specify the metadata callback function via `data-metadata-collector`. Le
 ></script>
 ```
 
-The function you specify in `data-metadata-collector` recieves an object with 2 values: `type` and `path`. Value `type` is either `pageview` or `event`. The `path` is a the path of the page. For example, `/contact`. Make sure to always return an object.
+The function you specify in `data-metadata-collector` receives an object with 2 values: `type` and `path`. Value `type` is either `pageview` or `event`. The `path` is the path of the page. For example, `/contact`. Make sure to always return an object.
 
 ## Metadata keys
 
-We replace non-alphanummeric characters with an underscore. We also trim underscores from the front and end of the key.
+We replace non-alphanumeric characters with an underscore. We also trim underscores from the front and end of the key.
 
 ```js
 sa_event("click_signup", { "$%!k_e___y__": "value" });
@@ -152,7 +152,7 @@ There are some limitations to numbers within metadata objects:
 
 ### Date
 
-When sending dates in JavaScript they will be converted to a string. For example, `new Date()` becomes <code>{{ "now"  | date: '%s' | date: '%Y-%m-%dT%H:%M:%S.123Z' }}</code>. We recommend wrapping your datas in a [`new Date()` constructor](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/Date) or converting to text via [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString). That way you're always sure you're sending dates in the right format.
+When sending dates in JavaScript they will be converted to a string. For example, `new Date()` becomes <code>{{ "now"  | date: '%s' | date: '%Y-%m-%dT%H:%M:%S.123Z' }}</code>. We recommend wrapping your dates in a [`new Date()` constructor](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/Date) or converting to text via [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString). That way you're always sure you're sending dates in the right format.
 
 ```js
 sa_event("click_signup", { created_at: new Date() });