diff --git a/content/_snippets/_view-google-analytics.mdx b/content/_snippets/_view-google-analytics.mdx
index d86ccbc..a3c4b76 100644
--- a/content/_snippets/_view-google-analytics.mdx
+++ b/content/_snippets/_view-google-analytics.mdx
@@ -2,5 +2,5 @@ import { Callout } from 'fumadocs-ui/components/callout';
To see a full example of the features available with App Snippets, Assets, and Settings, take a look at the Google Analytics 4 app on Github.
-View Google Analytics App on Github
+View Google Analytics App on GitHub
\ No newline at end of file
diff --git a/content/_snippets/_view-google-tag-manager.mdx b/content/_snippets/_view-google-tag-manager.mdx
index 50ae0de..7133051 100644
--- a/content/_snippets/_view-google-tag-manager.mdx
+++ b/content/_snippets/_view-google-tag-manager.mdx
@@ -2,5 +2,5 @@ import { Callout } from 'fumadocs-ui/components/callout';
To see a full example of the features available with App Snippets, Assets, and Settings, take a look at the Google Tag Manager app on Github.
-View Google Tag Manager App on Github
+View Google Tag Manager App on GitHub
\ No newline at end of file
diff --git a/content/_snippets/_view-intro-theme.mdx b/content/_snippets/_view-intro-theme.mdx
index dff20d1..b615885 100644
--- a/content/_snippets/_view-intro-theme.mdx
+++ b/content/_snippets/_view-intro-theme.mdx
@@ -1,5 +1,5 @@
import { Callout } from 'fumadocs-ui/components/callout';
-[Spark](https://github.com/NextCommerceCo/spark) is the recommended starter theme for the 29 Next platform, built with Tailwind CSS and available on Github as a starting point and guide for store themeing.
+[Spark](https://github.com/NextCommerceCo/spark) is the recommended starter theme for the Next Commerce platform, built with Tailwind CSS and available on GitHub as a starting point and guide for store theming.
\ No newline at end of file
diff --git a/content/docs/admin-api/guides/order-management.mdx b/content/docs/admin-api/guides/order-management.mdx
index 41c43e7..766b246 100644
--- a/content/docs/admin-api/guides/order-management.mdx
+++ b/content/docs/admin-api/guides/order-management.mdx
@@ -10,7 +10,7 @@ import { Callout } from 'fumadocs-ui/components/callout';
import MoveFulfillmentOrders from '../../../_snippets/_moving-fulfillment-orders.mdx';
import SplitFulfillmentOrders from '../../../_snippets/_splitting-fulfillment-orders.mdx';
-Order management operations can be automated through the Admin API for more efficient operations and bulk actions on large quanities of orders.
+Order management operations can be automated through the Admin API for more efficient operations and bulk actions on large quantities of orders.
Below are best practices and guides for common scenarios merchants and partners use to manage orders on the Admin API.
@@ -108,17 +108,17 @@ Below is an example POST request to the [ordersLinesCreate](/docs/admin-api/refe
#### Collect Payment for Outstanding Balance
-Orders can have an outstanding balance owed by the customer as a result of changing items on the order. To collect the outstanding balance, use the [ordersCollectPaymentCreate](/docs/admin-api/reference/orders/ordersCollectPaymentCreate) endpoint to initate a payment transaction with the order's initial payment method.
+Orders can have an outstanding balance owed by the customer as a result of changing items on the order. To collect the outstanding balance, use the [ordersCollectPaymentCreate](/docs/admin-api/reference/orders/ordersCollectPaymentCreate) endpoint to initiate a payment transaction with the order's initial payment method.
```json title="Collect Payment for Outstanding Balance" http-method="POST" http-target="https://{store}.29next.store/api/admin/orders/{number}/collect-payment/"
{
- "send_payment_notification": true // optionally send notificaiton to customer
+ "send_payment_notification": true // optionally send notification to customer
}
```
### Order Refunds
-Order management actions that require refunding and removing items from an order can be done through the refund flow. The refund flow is espcially useful when creating partial refunds or creating refunds for items that have already shipped to the customer.
+Order management actions that require refunding and removing items from an order can be done through the refund flow. The refund flow is especially useful when creating partial refunds or creating refunds for items that have already shipped to the customer.
#### Refund Flow
```mermaid
@@ -132,7 +132,7 @@ stateDiagram-v2
```
Refunding specific items of an order is a 3-step process:
-1. Retreive order line items using the [ordersRetrieve](/docs/admin-api/reference/orders/ordersRetrieve) endpoint.
+1. Retrieve order line items using the [ordersRetrieve](/docs/admin-api/reference/orders/ordersRetrieve) endpoint.
2. Calculate the refund using the [ordersRefundCalculateCreate](/docs/admin-api/reference/orders/ordersRefundCalculateCreate) endpoint.
3. Create the refund using the [ordersRefundCreate](/docs/admin-api/reference/orders/ordersRefundCreate) endpoint.
@@ -142,7 +142,7 @@ Order Refund Calculate APIs are only available on `2024-04-01` version and newer
#### Retrieve Order Lines
-Below is an abreviated example request to [ordersRetrieve](/docs/admin-api/reference/orders/ordersRetrieve) endpoint to get the line items of the order.
+Below is an abbreviated example request to [ordersRetrieve](/docs/admin-api/reference/orders/ordersRetrieve) endpoint to get the line items of the order.
```json title="Retrieve Order Details" http-method="GET" http-target="https://{store}.29next.store/api/admin/orders/{number}/"
{
@@ -196,7 +196,7 @@ Below is the response from the [ordersRefundCalculateCreate](/docs/admin-api/ref
"amount_incl_tax": "3.99", // amount to be refunded incl tax
"amount_excl_tax": "3.99", // amount to be refunded excl tax
"total_tax": "0.00", // shipping tax to be refunded
- "refundable_amount": "4.99" // shipping amount avialable to refund
+ "refundable_amount": "4.99" // shipping amount available to refund
},
"transactions": [
{
@@ -205,7 +205,7 @@ Below is the response from the [ordersRefundCalculateCreate](/docs/admin-api/ref
"refundable_amount": "184.96" // amount available to refund with this transaction
}
],
- "amount_excl_tax": "63.98", // total amoutn excl tax being refunded
+ "amount_excl_tax": "63.98", // total amount excl tax being refunded
"amount_incl_tax": "63.98", // total amount incl to be refunded
"total_tax": "0.00", // total tax being refunded
"currency": "USD"
@@ -257,11 +257,11 @@ Unfulfilled items always restock as `cancel`, so any refund of unshipped items n
-Depending on the product type and status of the line items being refunded, there are differen't restock actions available.
+Depending on the product type and status of the line items being refunded, there are different restock actions available.
**Physical Product**
- If unfulfilled, restock_type must be `cancel`.
-- If fullfilled, restock_type can be `return` or `no_restock`.
+- If fulfilled, restock_type can be `return` or `no_restock`.
**Digital Product**
- If unfulfilled, restock_type must be `cancel`.
@@ -382,7 +382,7 @@ Canceling an order is a common order management task when you need to cancel the
```json title="Cancel Order Request" http-method="POST" http-target="https://{store}.29next.store/api/admin/orders/{number}/cancel/"
{
- "cancel_reason": "Customer wants to cancel", // Appropiate cancel reason message
+ "cancel_reason": "Customer wants to cancel", // Appropriate cancel reason message
"full_refund": true, // Refund all remaining payments or not
"send_cancel_notification": true // Send the customer a notification or not
}
diff --git a/content/docs/admin-api/guides/payment-methods/bankcard.mdx b/content/docs/admin-api/guides/payment-methods/bankcard.mdx
index 7574a79..40c710c 100644
--- a/content/docs/admin-api/guides/payment-methods/bankcard.mdx
+++ b/content/docs/admin-api/guides/payment-methods/bankcard.mdx
@@ -94,7 +94,7 @@ Group membership, distribution weighting, and soft-decline retries are configure
Tokenize cards in our iFrame payment form before you send them to the Admin API. Your checkout never handles raw card data, which keeps it out of PCI scope.
-Try the [Demo](https://nextcommerceco.github.io/demo-iframe-payment-form/). The source is on [Github](https://github.com/NextCommerceCo/demo-iframe-payment-form/blob/main/index.html).
+Try the [Demo](https://nextcommerceco.github.io/demo-iframe-payment-form/). The source is on [GitHub](https://github.com/NextCommerceCo/demo-iframe-payment-form/blob/main/index.html).
`payment.js` is a script hosted by Next Commerce. It exposes the `NextPayment` class, which mounts the card number and security code fields in iFrames, validates them, and returns a token. You can style the fields to match the rest of your form.
diff --git a/content/docs/admin-api/guides/payment-methods/paypal.mdx b/content/docs/admin-api/guides/payment-methods/paypal.mdx
index aa458de..97aaf01 100644
--- a/content/docs/admin-api/guides/payment-methods/paypal.mdx
+++ b/content/docs/admin-api/guides/payment-methods/paypal.mdx
@@ -39,7 +39,7 @@ When creating a new order using PayPal using the orders_create API method, you m
You can optionally provide a `paypal_account` when creating the order to use a PayPal account other than the store default PayPal account.
-### Redirect Customer to Paypal
+### Redirect Customer to PayPal
The response when creating the order will provide a `payment_complete_url`. Your application should redirect the customer to this URL for completing the payment on PayPal.
```json title="Response with Payment Complete URL"
@@ -58,9 +58,9 @@ import RedirectPaymentStep3 from '../../../../_snippets/_redirect-payment-flows-
### Upsells
-Paypal supports one-click upsells through the [ordersAddLineItemsCreate](/docs/admin-api/reference/orders/ordersAddLineItemsCreate) API, enabling additional items to be added to the order with a payment transaction.
+PayPal supports one-click upsells through the [ordersAddLineItemsCreate](/docs/admin-api/reference/orders/ordersAddLineItemsCreate) API, enabling additional items to be added to the order with a payment transaction.
-To process upsells, the Paypal account must have [Reference Transactions](https://developer.paypal.com/api/nvp-soap/do-reference-transaction-soap/) enabled and configured on the store.
+To process upsells, the PayPal account must have [Reference Transactions](https://developer.paypal.com/api/nvp-soap/do-reference-transaction-soap/) enabled and configured on the store.
-If the store Paypal account has reference transactions enabled, the [ordersCreate](/docs/admin-api/reference/orders/ordersCreate) API response will include `supports_post_purchase_upsells: true`, signaling you can process one-click upsell transactions.
+If the store PayPal account has reference transactions enabled, the [ordersCreate](/docs/admin-api/reference/orders/ordersCreate) API response will include `supports_post_purchase_upsells: true`, signaling you can process one-click upsell transactions.
diff --git a/content/docs/admin-api/guides/subscription-management.mdx b/content/docs/admin-api/guides/subscription-management.mdx
index baa1aae..0cadafb 100644
--- a/content/docs/admin-api/guides/subscription-management.mdx
+++ b/content/docs/admin-api/guides/subscription-management.mdx
@@ -15,7 +15,7 @@ Subscription management actions most often times will only affect future renewal
### Create Subscription
-Subscriptions can be created directly through the [subscriptionsCreate](/docs/admin-api/reference/subscriptions/subscriptionsCreate) Admin API endpoint for scenarios such as custom order flows or importing subcriptions from another platform.
+Subscriptions can be created directly through the [subscriptionsCreate](/docs/admin-api/reference/subscriptions/subscriptionsCreate) Admin API endpoint for scenarios such as custom order flows or importing subscriptions from another platform.
```json title="Create Subscription" http-method="POST" http-target="https://{store}.29next.store/api/admin/subscriptions/"
{
@@ -52,7 +52,7 @@ Updating subscription recurring items and pricing can be done through [subscript
**Adding an Additional Product**
-To add a new product to a subscription, use the [subscriptionLinesCreate](/docs/admin-api/reference/subscriptions/subscriptionsLinesCreate) Admin API endpoint with the product, price, and quanity details.
+To add a new product to a subscription, use the [subscriptionLinesCreate](/docs/admin-api/reference/subscriptions/subscriptionsLinesCreate) Admin API endpoint with the product, price, and quantity details.
```json title="Adding an Additional Product" http-method="POST" http-target="https://{store}.29next.store/api/admin/subscriptions/{id}/lines/"
{
@@ -64,7 +64,7 @@ To add a new product to a subscription, use the [subscriptionLinesCreate](/docs/
**Updating an Existing Line Item Product Price**
-To update and existing product price and quantity on a subscription line, use the [subscriptionsLinesUpdate](/docs/admin-api/reference/subscriptions/subscriptionsLinesUpdate) Admin API endpoint with the new price, and new quanity details.
+To update and existing product price and quantity on a subscription line, use the [subscriptionsLinesUpdate](/docs/admin-api/reference/subscriptions/subscriptionsLinesUpdate) Admin API endpoint with the new price, and new quantity details.
```json title="Updating an Existing Product" http-method="PUT" http-target="https://{store}.29next.store/api/admin/subscriptions/{id}/lines/{lineId}/"
{
@@ -86,7 +86,7 @@ Subscriptions must have at least one line item with a product, you can alternati
### Updating Renewal Schedule
-Changing the renewal schedule of a subscription can be achived with a PATCH request to the [subscriptionsPartialUpdate](/docs/admin-api/reference/subscriptions/subscriptionsPartialUpdate) endpoint with a new `interval` and `interval_count`, ie 30 days.
+Changing the renewal schedule of a subscription can be achieved with a PATCH request to the [subscriptionsPartialUpdate](/docs/admin-api/reference/subscriptions/subscriptionsPartialUpdate) endpoint with a new `interval` and `interval_count`, ie 30 days.
```json title="Update Subscription Renewal Schedule" http-method="PATCH" http-target="https://{store}.29next.store/api/admin/subscriptions/{id}/"
{
@@ -170,7 +170,7 @@ To change the bankcard on a subscription, pass a new `card_token` with a PATCH r
To update a bankcard on a subscription, you must use the **[iFrame to tokenize](/docs/admin-api/guides/payment-methods/bankcard)** the bankcard and use the `card_token` when updating the subscription itself.
-The new bankcard will be automatically verfied with a `verify` request to a payment gateway to ensure the new bankcard is valid and can be used for future renewals. If the bankcard cannot be verified, the update request will fail and return an error.
+The new bankcard will be automatically verified with a `verify` request to a payment gateway to ensure the new bankcard is valid and can be used for future renewals. If the bankcard cannot be verified, the update request will fail and return an error.
**New Bankcard Payment Method Flow**
```mermaid
@@ -205,7 +205,7 @@ stateDiagram-v2
### Retrying Renewal
-Subscriptions that are `past_due` status can be attemted to retry the renewal, often combined with a new `payment_gateway`, by using the [subscriptionsRetryCreate](/docs/admin-api/reference/subscriptions/subscriptionsRetryCreate) endpoint.
+Subscriptions that are `past_due` status can be attempted to retry the renewal, often combined with a new `payment_gateway`, by using the [subscriptionsRetryCreate](/docs/admin-api/reference/subscriptions/subscriptionsRetryCreate) endpoint.
```json title="Retry Subscription Renewal" http-method="POST" http-target="https://{store}.29next.store/api/admin/subscriptions/{id}/retry/"
{
diff --git a/content/docs/apps/app-kit.mdx b/content/docs/apps/app-kit.mdx
index 5b0d483..1e59a3d 100644
--- a/content/docs/apps/app-kit.mdx
+++ b/content/docs/apps/app-kit.mdx
@@ -11,14 +11,14 @@ import { Callout } from 'fumadocs-ui/components/callout';
App Kit is a command line tool for developers to build and maintain apps that extend storefront themes with [Event Trackers](/docs/apps/event-tracking).
-App Kit is only required for Apps that extend to the storefront with App Snippets, [Server to Server Apps](/docs/apps/guides/server-to-server-apps) do not need to use App Kit to complete the Oauth Flow for your App to access the Admin API.
+App Kit is only required for Apps that extend to the storefront with App Snippets, [Server to Server Apps](/docs/apps/guides/server-to-server-apps) do not need to use App Kit to complete the OAuth Flow for your App to access the Admin API.
-[See Full Instructions on Github](https://github.com/NextCommerceCo/app-kit) or [Install App Kit from PyPi](https://pypi.org/project/next-app-kit/)
+[See Full Instructions on GitHub](https://github.com/NextCommerceCo/app-kit) or [Install App Kit from PyPI](https://pypi.org/project/next-app-kit/)
## Installation
-App Kit is a python package available on [PyPi](https://pypi.org/project/next-app-kit/)
+App Kit is a python package available on [PyPI](https://pypi.org/project/next-app-kit/)
If you already have `python` and `pip`, install with the following command:
diff --git a/content/docs/apps/guides/dispute-service.mdx b/content/docs/apps/guides/dispute-service.mdx
index b8d3b74..55b7ed2 100644
--- a/content/docs/apps/guides/dispute-service.mdx
+++ b/content/docs/apps/guides/dispute-service.mdx
@@ -11,7 +11,7 @@ import { Tab, Tabs } from 'fumadocs-ui/components/tabs';
Dispute service apps are integrations that manage the processing of payment disputes (alerts and chargebacks) on behalf of merchants seamlessly within the platform.
-Dispute Service Apps are [Server to Server Apps](/docs/apps/guides/server-to-server-apps) that use the Oauth flow to obtain API Access and then use the [Admin APIs](/docs/admin-api) and [Webhooks](/docs/webhooks) to subscribe to store event activity.
+Dispute Service Apps are [Server to Server Apps](/docs/apps/guides/server-to-server-apps) that use the OAuth flow to obtain API Access and then use the [Admin APIs](/docs/admin-api) and [Webhooks](/docs/webhooks) to subscribe to store event activity.
## Disputes
@@ -114,7 +114,7 @@ To create a dispute in the store using the [disputesCreate](/docs/admin-api/refe
"arn": "string", // optional
"case_number": "string", // optional
"happened_at": "2019-08-24T14:15:22Z", // date when dispute occurred
- "amount": "string", // dispute amount, sometimes doesnt match transaction amount
+ "amount": "string", // dispute amount, sometimes doesn't match transaction amount
"currency": "USD", // dispute currency
}
```
diff --git a/content/docs/apps/guides/fulfillment-service.mdx b/content/docs/apps/guides/fulfillment-service.mdx
index 6cc9e3b..e5b0c6d 100644
--- a/content/docs/apps/guides/fulfillment-service.mdx
+++ b/content/docs/apps/guides/fulfillment-service.mdx
@@ -83,7 +83,7 @@ When new orders are created, the fulfillment orders are assigned to the location
The location `callback` is a URL the store will send `Fulfillment Request` webhooks to notify them of a new fulfillment assigned. Fulfillment Services need to query their [Assigned Fulfillment Orders](#assigned-fulfillment-orders) to retrieve the fulfillment order details.
-Fulfullment Requests are sent to the location `callback` + `/fulfillment-order-notification/`.
+Fulfillment Requests are sent to the location `callback` + `/fulfillment-order-notification/`.
**Fulfillment assignment request types are:**
diff --git a/content/docs/apps/oauth/getting-started.mdx b/content/docs/apps/oauth/getting-started.mdx
index 346cc97..b4fa866 100644
--- a/content/docs/apps/oauth/getting-started.mdx
+++ b/content/docs/apps/oauth/getting-started.mdx
@@ -13,14 +13,14 @@ To get started, make sure that you have your Apps' `client_id` and `client_secre
### Step 2: App Permissions Setup
-During the App installation flow, Apps that have `oauth` configured will be redirected to the Oauth App URL from thee App Settings.
+During the App installation flow, Apps that have `oauth` configured will be redirected to the OAuth App URL from the App Settings.
Your app should redirect the user back to the store authorization view configured with the scope permissions your app requires.
-At every stage in the Oauth flow you'll receive a querystring variable `store` with the network domain of the store that is installing the app. **You should use this in your app logic as the unique identifier for the store.**
+At every stage in the OAuth flow you'll receive a querystring variable `store` with the network domain of the store that is installing the app. **You should use this in your app logic as the unique identifier for the store.**
```bash title="Authorization Link Format"
https://{network_domain}/oauth2/authorize/?response_type=code&client_id={client_id}&redirect_uri={redirect_uri}&scope={scopes}
@@ -28,9 +28,9 @@ https://{network_domain}/oauth2/authorize/?response_type=code&client_id={client_
|Parameter|Description|
|-----|-----|
-|`network_domain`| The store network domain that is installing the app. Can be referenced from the `store` url parameter sent to your App Oauth App URL. |
+|`network_domain`| The store network domain that is installing the app. Can be referenced from the `store` url parameter sent to your App OAuth App URL. |
|`response_type`| Must be `code`, which only authorization flow supported at this time. |
-|`client_id`| Your app `client_id` found in in your partner account.|
+|`client_id`| Your app `client_id` found in your partner account.|
|`redirect_uri`|The url you want to receive the Authorization Code in your app. **Must be listed in your app Redirect URLs setting**. |
|`scope`| A space separated list of scopes such as `orders:read orders:write users:read users:write`. [See list of all available scopes](/docs/admin-api/permissions). |
@@ -45,7 +45,7 @@ https://yourapp.com/setup/authorize/?store={network_domain}&code={authorization_
|Parameter|Description|
|-----|-----|
-|`network_domain`| The store network domain that is installing the app. Can be referenced from the `store` url parameter sent to your app Oauth Redirect URL. |
+|`network_domain`| The store network domain that is installing the app. Can be referenced from the `store` url parameter sent to your app OAuth Redirect URL. |
|`authorization_code`| The authorization code used to retrieve the Access Token in the next step. |
### Step 4: Retrieve Access Token
diff --git a/content/docs/apps/oauth/index.mdx b/content/docs/apps/oauth/index.mdx
index e31fba6..82872c9 100644
--- a/content/docs/apps/oauth/index.mdx
+++ b/content/docs/apps/oauth/index.mdx
@@ -8,7 +8,7 @@ This guide introduces OAuth Authentication for Server-side Apps to access the Ad
### Introduction to OAuth
-OAuth 2.0 is the industry standard protocol for authorizing and assigning permissions to 3rd party apps. There are many great guides on the internet regarding OAuth 2.0, such as this [OAuth 2.0 introduction guide from Auth0.com](https://auth0.com/intro-to-iam/what-is-oauth-2/). Your Server-side App's language most likely has pre-built packages to assist with handling Oauth 2.0 Authentication flows.
+OAuth 2.0 is the industry standard protocol for authorizing and assigning permissions to 3rd party apps. There are many great guides on the internet regarding OAuth 2.0, such as this [OAuth 2.0 introduction guide from Auth0.com](https://auth0.com/intro-to-iam/what-is-oauth-2/). Your Server-side App's language most likely has pre-built packages to assist with handling OAuth 2.0 Authentication flows.
### Access Tokens
@@ -38,7 +38,7 @@ sequenceDiagram
##### Authorization Flow Step Detail
1. User initiates the App installation process.
-2. Store redirects to the App URL configured in App Oauth Settings.
+2. Store redirects to the App URL configured in App OAuth Settings.
3. App redirects to the store to load the OAuth Authorization view and requests the merchant to authorize app and permission required scopes, [see authorization link example](/docs/apps/oauth/getting-started#step-2-app-permissions-setup).
4. User authorizes the app and requested permission scopes in the store dashboard.
5. Store redirects to the Redirect URL with an [Authorization Code](https://oauth.net/2/grant-types/authorization-code/), a temporary credential representing the authorization, [see authorization code example](/docs/apps/oauth/getting-started#step-3-confirm-installation).
@@ -47,6 +47,6 @@ sequenceDiagram
8. The app can now access the Admin API using the Access Token, [see Admin API examples](/docs/admin-api).
-### Oauth Guides
+### OAuth Guides
diff --git a/content/docs/apps/oauth/session-auth.mdx b/content/docs/apps/oauth/session-auth.mdx
index c7f405e..a7552a1 100644
--- a/content/docs/apps/oauth/session-auth.mdx
+++ b/content/docs/apps/oauth/session-auth.mdx
@@ -52,7 +52,7 @@ Session tokens are generated from the store dashboard and can be used by your Ap
``` mermaid
sequenceDiagram
autonumber
- Store->>App: Redirects to App Oauth App URL with JWT token.
+ Store->>App: Redirects to App OAuth App URL with JWT token.
App->>User: App decrypt/verify JWT token to authorize request
App->>User: App loads an authenticated view for user.
```
diff --git a/content/docs/storefront/event-tracking.mdx b/content/docs/storefront/event-tracking.mdx
index e45d850..5959036 100644
--- a/content/docs/storefront/event-tracking.mdx
+++ b/content/docs/storefront/event-tracking.mdx
@@ -32,7 +32,7 @@ Event trackers are pure javascript, meaning third-party event tracking scripts s
Below is the equivalent expressed as a javascript function to create and append the script tag to the document head.
-```javascript title="Converetd Javascript Script Tag"
+```javascript title="Converted JavaScript Script Tag"
(function() {
var script = document.createElement('script');
script.async = true;
@@ -227,7 +227,7 @@ All events have `context` of the parent frame to easily access contextual data a
| `navigator` | Data from the top-frame `navigator` object (e.g., userAgent, language). | [Navigator](https://developer.mozilla.org/en-US/docs/Web/API/Navigator) |
| `window` | Data from the top-frame `window` object (e.g., innerWidth, location). | [Window](https://developer.mozilla.org/en-US/docs/Web/API/Window) |
-```json title="Example conext object"
+```json title="Example context object"
{
"context": {
"document": {...}, // frame parent document
@@ -441,7 +441,7 @@ analytics.subscribe("product_viewed", event => {
"date_created": "2024-01-24T02:02:52.811742-05:00",
"date_updated": "2024-10-03T04:32:52.860659-04:00",
"metadata": {
- "excerpt": "Product conent.
",
+ "excerpt": "Product content.
",
"special": "Special Promo",
"external_id": "12345"
}
diff --git a/content/docs/storefront/themes/guides/custom-page-templates.mdx b/content/docs/storefront/themes/guides/custom-page-templates.mdx
index ff6f92d..4f4639c 100644
--- a/content/docs/storefront/themes/guides/custom-page-templates.mdx
+++ b/content/docs/storefront/themes/guides/custom-page-templates.mdx
@@ -54,5 +54,5 @@ On your page of choice, select your newly created template as the **Theme Templa
After uploading and selecting the template, navigate to that page's full storefront URL on the `https://{store}.29next.store` network domain and verify the served HTML, expected assets, and behavior. Do not use a mapped public storefront domain to decide whether the template change landed.
-You are not limited to overriding the existing template blocks in the default page template. You can create and add your own to the default template to overide in your custom template. For example, adding `{% block my_custom_block %}{% endblock %}` to page.html, around any area you wish to customize, will allow you to overide it in the custom template
+You are not limited to overriding the existing template blocks in the default page template. You can create and add your own to the default template to override in your custom template. For example, adding `{% block my_custom_block %}{% endblock %}` to page.html, around any area you wish to customize, will allow you to override it in the custom template
diff --git a/content/docs/storefront/themes/guides/custom-product-templates.mdx b/content/docs/storefront/themes/guides/custom-product-templates.mdx
index b49e3c5..dec400e 100644
--- a/content/docs/storefront/themes/guides/custom-product-templates.mdx
+++ b/content/docs/storefront/themes/guides/custom-product-templates.mdx
@@ -64,5 +64,5 @@ After uploading and selecting the template, navigate to that product's full stor
-You are not limited to overriding the existing template blocks in the default product template. You can create and add your own to the default template to overide in your custom template. For example, adding `{% block my_custom_block %}{% endblock %}` to product.html, around any area you wish to customize, will allow you to overide it in the custom template
+You are not limited to overriding the existing template blocks in the default product template. You can create and add your own to the default template to override in your custom template. For example, adding `{% block my_custom_block %}{% endblock %}` to product.html, around any area you wish to customize, will allow you to override it in the custom template
diff --git a/content/docs/storefront/themes/guides/product-metadata.md b/content/docs/storefront/themes/guides/product-metadata.md
index 3b9379a..00e0476 100644
--- a/content/docs/storefront/themes/guides/product-metadata.md
+++ b/content/docs/storefront/themes/guides/product-metadata.md
@@ -25,7 +25,7 @@ Let's look at an example of adding support for a **Product Tagline** to a produc
**Create Tagline Product Metadata Field**
-In your store Metadata settings, create a new Metadata Definition for your tagline. Set the the **object** to `Product` and **key** to `tagline`.
+In your store Metadata settings, create a new Metadata Definition for your tagline. Set the **object** to `Product` and **key** to `tagline`.
**Add Tagline Attribute Variable to Product Template**
diff --git a/content/docs/storefront/themes/index.mdx b/content/docs/storefront/themes/index.mdx
index 4580115..c45f314 100644
--- a/content/docs/storefront/themes/index.mdx
+++ b/content/docs/storefront/themes/index.mdx
@@ -46,7 +46,7 @@ Never hardcode a CDN asset URL in a template — asset URLs change on every push
The configs directory is used to store your theme settings options and also the settings data as they should be configured with the theme.
- `settings_schema.json` is used to generate the theme settings form
-- `setting_data.json` is used data storage for the the theme settings
+- `setting_data.json` is used as data storage for the theme settings
```shell title="Config Directory"
configs
@@ -130,7 +130,7 @@ templates
### Sass
-The sass directory accepts scss files for use in in a theme. See Theme Kit for more details on local sass compiling.
+The sass directory accepts scss files for use in a theme. See Theme Kit for more details on local sass compiling.
Sass files are not automatically compiled in the platform and must be compiled to css files locally for use in templates from the assets directory.
diff --git a/content/docs/storefront/themes/templates/filters.md b/content/docs/storefront/themes/templates/filters.md
index f2c04fd..0c68b75 100644
--- a/content/docs/storefront/themes/templates/filters.md
+++ b/content/docs/storefront/themes/templates/filters.md
@@ -142,7 +142,7 @@ For example, if value is escaping, the output will be \\u003Cb\\u003Eesca
### json_script
-Safely outputs a variable object as JSON, wrapped in a `