codatio · pmckinney-codat · Feb 6, 2026 · Feb 4, 2026 · Feb 4, 2026 · Feb 5, 2026
diff --git a/blog/230203-weekly-update.md b/blog/230203-weekly-update.md
@@ -5,7 +5,7 @@ tags: ["Product", "Update"]
 authors: mcclowes
 ---
 
-A new product for easy syncing with bookkeeping software and ERPs, and other qualithy of life improvements.
+A new product for easy syncing with bookkeeping software and ERPs, and other quality of life improvements.
 
 <!--truncate-->
 

diff --git a/blog/230404-product-update-4.md b/blog/230404-product-update-4.md
@@ -32,7 +32,7 @@ We've improved our data type coverage for a number of integrations.
 
 ## Deprecations
 
-Don't forget about these immenent deprecations:
+Don't forget about these imminent deprecations:
 
 - [https://docs.codat.io/updates/230411-api-keys](https://docs.codat.io/updates/230411-api-keys)
 - [https://docs.codat.io/updates/230411-deletion-of-data](https://docs.codat.io/updates/230411-deletion-of-data)

diff --git a/blog/230710-deprecation-v2-categories.md b/blog/230710-deprecation-v2-categories.md
@@ -49,7 +49,7 @@ After the **24th July 2023**, the deprecated endpoints will no longer work, the
 
 :::caution Update: July 24, 2023
 
-**Deprecation compelted**
+**Deprecation completed**
 :::
 
 :::caution Update: July 13, 2023

diff --git a/blog/240925-ui-improvements-update.md b/blog/240925-ui-improvements-update.md
@@ -15,7 +15,7 @@ We have revised and improved the connection flows a small business customer goes
 
 - A **clean and consistent layout and design** to provide recognizable experiences across all our linking journeys.
 - **Improved and simplified copy** that provides enhanced guidance to the user going through the flow.
-- **Autogenerated username and password values** the user can copy and paste to remove ambuguity.
+- **Autogenerated username and password values** the user can copy and paste to remove ambiguity.
 - **Deep links** in the linking journey take users directly to the pages they need to execute the steps of the flow.
 - Links to **end user documentation** that supports your customer in their journey and allows them to troubleshoot as they go.
 

diff --git a/blog/241004-deprecation-rules-service.md b/blog/241004-deprecation-rules-service.md
@@ -33,7 +33,7 @@ If you are currently using company-specific rules with our legacy service, use c
 
 #### Company information using tags
 
-For example, if you previously passed company information via the webhook consumer's path (such as `POST /region/{regionId}/accounts/{accountId}`), you can use `tags` when creating or udating a company as follows:
+For example, if you previously passed company information via the webhook consumer's path (such as `POST /region/{regionId}/accounts/{accountId}`), you can use `tags` when creating or updating a company as follows:
 
 ```json
 {

diff --git a/blog/250110-secure-linking.md b/blog/250110-secure-linking.md
@@ -42,4 +42,4 @@ If you are currently adding query parameters to Link URLs (for example, by appen
 
 #### If using Link SDK
 
-To enforce the imited validity of Link URLs using the Link SDK, you need to retrieve an access token for your customer using the [Get company access token](/platform-api#/operations/get-company-access-token) endpoint and pass it when initializing the SDK. This serves as an equivalent to a one-time password appended to a Link URL.
+To enforce the limited validity of Link URLs using the Link SDK, you need to retrieve an access token for your customer using the [Get company access token](/platform-api#/operations/get-company-access-token) endpoint and pass it when initializing the SDK. This serves as an equivalent to a one-time password appended to a Link URL.
diff --git a/blog/250401-bank-feeds-connections.md b/blog/250401-bank-feeds-connections.md
@@ -25,4 +25,4 @@ This update is relevant for our Bank Feeds clients who use our account mapping U
 
 ## How to get started?
 
-No action is required on your side. If you are currently using our account mapping UI in your application, the component is already avalaible to your customers.
+No action is required on your side. If you are currently using our account mapping UI in your application, the component is already available to your customers.
diff --git a/blog/260102-close-friction-overlay-in-embedded-link.md b/blog/260102-close-friction-overlay-in-embedded-link.md
@@ -5,7 +5,7 @@ tags: ["Product", "Update", "Link", "UX"]
 authors: pmckinney
 ---
 
-We've added a new exit confirmation overlay to Embedded Link. It appears when users attempt to close an in-progess connection flow, helping prevent accidental drop-offs.
+We've added a new exit confirmation overlay to Embedded Link. It appears when users attempt to close an in-progress connection flow, helping prevent accidental drop-offs.
 
 <!--truncate-->
 

diff --git a/blog/260116-xero-pricing.md b/blog/260116-xero-pricing.md
@@ -25,7 +25,7 @@ Depending on your current connection volumes and API usage, you may need to:
 
 - Select a tier.
 - Add a payment method in [Xero’s developer portal](http://developer.xero.com/app/manage/) (required once moving beyond Starter).
-- Monitor and optimise API usage to manage costs.
+- Monitor and optimize API usage to manage costs.
 
 ## What you should do now
 
@@ -34,4 +34,4 @@ To avoid disruption and ensure you’re ready ahead of March, we recommend you:
 - Review [Xero’s pricing and tier model](https://developer.xero.com/pricing#tier-fees-connection-limits-and-api-volume-usage).
 - Login to your [Xero developer app](http://developer.xero.com/app/manage/) and check your API usage.
 - Plan for tier selection/billing readiness ahead of March 2026.
-- Please review your datasets' [sync frequency](https://docs.codat.io/using-the-api/queueing-data-syncs#sync-frequency) in the Codat portal. It is always reccomended that you only sync data as often as is essential for your use-case.
+- Please review your datasets' [sync frequency](https://docs.codat.io/using-the-api/queueing-data-syncs#sync-frequency) in the Codat portal. It is always recommended that you only sync data as often as is essential for your use-case.
diff --git a/cspell.json b/cspell.json
@@ -34,87 +34,197 @@
     }
   ],
   "words": [
+    "Abila",
+    "AEST",
+    "aiwb",
+    "AISP",
     "akxx",
     "API",
     "APIs",
+    "appsettings",
     "authentication",
     "authorization",
+    "autoplay",
+    "Autres",
     "BACS",
+    "bankfeeds",
+    "bankstatement",
+    "Basiq",
+    "bento",
     "BigCommerce",
+    "billpayasync",
+    "billpaysync",
+    "Brex",
+    "brex",
     "Capchase",
     "Chargebee",
+    "chargeback",
+    "chargebacks",
+    "Chargebacks",
+    "Chargify",
+    "chargify",
+    "Clearbooks",
     "Codat's",
     "Codat",
-    "datasource",
-    "datasources",
-    "datatype",
-    "datatypes",
+    "Coltman",
+    "companyid",
+    "costcenters",
+    "Dashboarding",
+    "DDEP",
     "deauthorization",
     "Deauthorized",
+    "deauthorize",
     "decisioning",
+    "demodata",
     "drawdowns",
+    "drillable",
+    "dropoff",
     "dvcm",
+    "EBITDA",
     "eCommerce",
     "endpoint",
     "endpoints",
+    "exez",
+    "exgd",
+    "Fahey",
     "fbrh",
+    "fintech",
     "Financials",
+    "fqly",
     "FreshBooks",
+    "fztf",
+    "GAAP",
+    "gamify",
+    "Gamify",
     "gbol",
+    "generalledgers",
+    "Hairosmith",
     "hbql",
     "hcws",
+    "HMAC",
+    "hostnames",
+    "HSTS",
     "iban",
+    "IDAS",
     "Intacct's",
     "Intacct",
     "Intuit's",
     "Intuit",
+    "Jaro",
     "jcrp",
+    "Kash",
+    "Kashflow",
+    "keyss",
+    "Kleppman",
+    "knfz",
+    "Knowledgebase",
+    "ldgh",
     "Lightspeed",
+    "lqai",
+    "lrhd",
+    "ltes",
+    "ltpp",
     "Maxio",
     "metadata",
+    "miscategorized",
+    "MNDA",
+    "Mobbin",
+    "Monzo",
+    "mqjo",
+    "multicurrency",
+    "Multitenant",
+    "mybank",
     "MYOB",
+    "myshopify",
     "ndsk",
     "neobanks",
     "NetSuite",
+    "OBWAC",
     "olpr",
+    "Organisation",
+    "Organisations",
+    "otherreceipt",
     "Pandle",
     "payables",
+    "paymentmethod",
+    "payrun",
+    "payruns",
     "pbbf",
+    "pbtz",
     "pdvj",
+    "permissioned",
     "Phorest",
+    "PISP",
     "pqsw",
     "Presta",
     "PrestaShop",
     "qhyg",
+    "qkdj",
     "Qualys",
     "qudb",
+    "QWAC",
     "QuickBooks",
+    "quickbooksdesktop",
     "recategorization",
     "recategorize",
     "Recategorize",
     "recategorizing",
     "Recategorizing",
     "Recurly",
+    "Rightworks",
+    "Rockstar",
+    "RPMT",
+    "rqwd",
     "rvam",
+    "rwuv",
+    "SCHG",
+    "SCPN",
+    "SDLC",
     "SDK",
     "SDKs",
+    "shipto",
+    "signum",
+    "skillset",
+    "subjournals",
+    "sumup",
+    "suuo",
     "Svix",
+    "textkey",
+    "textkeys",
     "tgff",
+    "THHMMSS",
     "trji",
     "TrueLayer's",
     "TrueLayer",
-    "usecase",
-    "usecases",
+    "ugxp",
+    "upvr",
+    "Venmo",
+    "Vipps",
+    "vipps",
+    "VNDDEFAULT",
+    "vqzp",
     "vxvy",
     "Wayflyer",
+    "Webroot",
+    "Webservice",
+    "Webservices",
+    "webhookratelimits",
     "webhook",
     "webhooks",
+    "Winkler",
+    "workstream",
+    "workstreams",
     "worksream",
     "writeback",
     "Writeback",
+    "xcwv",
+    "XLSB",
     "Xero's",
     "Xero",
+    "YNAB",
+    "yzth",
     "Zettle",
-    "zpqy"
+    "zpqy",
+    "zsth"
   ]
-} 
+}
-Original file line number
+Diff line change
@@ Expand Up @@
     #### Company information using tags
-    For example, if you previously passed company information via the webhook consumer's path (such as `POST /region/{regionId}/accounts/{accountId}`), you can use `tags` when creating or udating a company as follows:
+    For example, if you previously passed company information via the webhook consumer's path (such as `POST /region/{regionId}/accounts/{accountId}`), you can use `tags` when creating or updating a company as follows:
     ```json
     {
@@ Expand Down @@
Original file line number	Diff line number	Diff line change
Expand Up		@@ -42,4 +42,4 @@ If you are currently adding query parameters to Link URLs (for example, by appen

		#### If using Link SDK

		To enforce the imited validity of Link URLs using the Link SDK, you need to retrieve an access token for your customer using the [Get company access token](/platform-api#/operations/get-company-access-token) endpoint and pass it when initializing the SDK. This serves as an equivalent to a one-time password appended to a Link URL.
		To enforce the limited validity of Link URLs using the Link SDK, you need to retrieve an access token for your customer using the [Get company access token](/platform-api#/operations/get-company-access-token) endpoint and pass it when initializing the SDK. This serves as an equivalent to a one-time password appended to a Link URL.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -25,4 +25,4 @@ This update is relevant for our Bank Feeds clients who use our account mapping U

		## How to get started?

		No action is required on your side. If you are currently using our account mapping UI in your application, the component is already avalaible to your customers.
		No action is required on your side. If you are currently using our account mapping UI in your application, the component is already available to your customers.