Bump crate-ci/typos from 1.34.0 to 1.35.3 (#1066)

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Nihal Gonsalves <[email protected]>

Author: dependabot[bot]

.github/workflows/lint.yml

@@ -14,4 +14,4 @@ jobs:
       - name: Checkout Actions Repository
         uses: actions/checkout@v4
       - name: Spell Check Repo
-        uses: crate-ci/typos@v1.34.0
+        uses: crate-ci/typos@v1.35.3

docs/migrating-to-revenuecat/sdk-or-not/sdk-less-integration.mdx

@@ -23,7 +23,7 @@ If you want to manually send purchases to RevenueCat, you can do so by sending r
 
 All RevenueCat data and integration features, including [charts](/dashboard-and-metrics/charts), [customer history](/dashboard-and-metrics/customer-history), [purchase lifecycle events](/integrations/integrations), [webhooks](/integrations/webhooks), [integrations with third party tools](/integrations/third-party-integrations), and [scheduled data exports](/integrations/scheduled-data-exports) work without integrating the SDK. RevenueCat's data features provide data at a higher level of granularity than the reports available from the app stores directly, allow tying data directly to your customer's profiles, and allow syncing this data to your own backend or data warehouse or to third party tools.
 
-One important factor to decide before integrating RevenueCat is what to use as the customer identity, also referred to as App User ID. If you are already using a unique app user ID in your backend, it is often best to use this for RevenueCat as well. Otherwise, RevenueCat can generate anonyomous App User IDs for you; however, you won't be able to link customer identity across different tools that way.
+One important factor to decide before integrating RevenueCat is what to use as the customer identity, also referred to as App User ID. If you are already using a unique app user ID in your backend, it is often best to use this for RevenueCat as well. Otherwise, RevenueCat can generate anonymous App User IDs for you; however, you won't be able to link customer identity across different tools that way.
 
 If you are planning on using RevenueCat integrations with third party tools, please note that some of them require special customer identifiers. These are generally using specific RevenueCat [customer attributes](/customers/customer-attributes) that will need to be set [via the REST API](/api-v1#tag/customers/operation/update-subscriber-attributes). You can find information about the required customer attributes in the documentation for the respective [third-party integration](/integrations/third-party-integrations).