Open Source Platform for DTC, B2B Commerce, Marketplaces & Omnichannel. REST APIs, TypeScript SDKs, and production-ready Next.js storefront. Self-host it. Own your data. No vendor lock-in. Zero platform fees.
Ruby b2b-commercee-commerceecommerceecommerce-apiecommerce-frameworkecommerce-platformheadlessheadless-commerceheadless-ecommercemarketplacemulti-tenantmulti-vendormulti-vendor-ecommerceopen-sourcespree-commerce
docs: fix spelling, grammar, and formatting errors across MDX docs (#14097)
mintlify[bot]23910cdc4336
diff --git a/docs/developer/admin/authentication.mdx b/docs/developer/admin/authentication.mdxindex a86453ca9b..da3f518cb1 100644--- a/docs/developer/admin/authentication.mdx+++ b/docs/developer/admin/authentication.mdx@@ -21,7 +21,7 @@ This will tell Spree to use your `AdminUser` model for the admin panel. You willinclude Spree::UserMethods```-In your `config/initializers/routes.rb` file, you will need define devise routes for the 2nd model:+In your `config/initializers/routes.rb` file, you will need to define devise routes for the 2nd model:```rubySpree::Core::Engine.routes.prepend_routes dodiff --git a/docs/developer/contributing/creating-an-extension.mdx b/docs/developer/contributing/creating-an-extension.mdxindex 94d3ab8a82..5d2ff63275 100644--- a/docs/developer/contributing/creating-an-extension.mdx+++ b/docs/developer/contributing/creating-an-extension.mdx@@ -72,7 +72,7 @@ Once you have added the gem, it's time to bundle:bundle install```-Finally, let's run the `spree_simple_sales` install generator to copy over the migration we just created answer **yes** if prompted to run migrations:+Finally, let's run the `spree_simple_sales` install generator to copy over the migration we just created. Answer **yes** if prompted to run migrations:```bash# context: Your Spree store's app root (i.e. Rails.root); not the extension's root path.diff --git a/docs/developer/customization/authentication.mdx b/docs/developer/customization/authentication.mdxindex 5cbf3bb25b..aab7ef1119 100644--- a/docs/developer/customization/authentication.mdx+++ b/docs/developer/customization/authentication.mdx@@ -24,7 +24,7 @@ Now, run the generator to set up Spree integration with Devise:bin/rails g spree:authentication:devise```-This will create the a new file in `lib/spree/authentication_helpers.rb` that serves as a bridge between Spree and your existing authentication system routes. You can then use this file to customize the routes to your liking. It should automatically pick up standard Devise routes.+This will create a new file in `lib/spree/authentication_helpers.rb` that serves as a bridge between Spree and your existing authentication system routes. You can then use this file to customize the routes to your liking. It should automatically pick up standard Devise routes.Secondly, this generator will add necessary modules to your `User` model.@@ -68,7 +68,7 @@ Now, run the generator to set up Spree integration with your custom authenticatibin/rails g spree:authentication:custom```-This will create the a new file in `lib/spree/authentication_helpers.rb` that serves as a bridge between Spree and your existing authentication system routes. You will need to customize this file to fit your needs.+This will create a new file in `lib/spree/authentication_helpers.rb` that serves as a bridge between Spree and your existing authentication system routes. You will need to customize this file to fit your needs.Secondly, this generator will add necessary modules to your `User` model.diff --git a/docs/developer/customization/checkout.mdx b/docs/developer/customization/checkout.mdxindex 8324a5b903..89d5dc664e 100644--- a/docs/developer/customization/checkout.mdx+++ b/docs/developer/customization/checkout.mdx@@ -10,7 +10,7 @@ The Spree checkout process has been designed for maximum flexibility. It's been## The Checkout Flow DSL-Spree comes with a new checkout DSL that allows you succinctly define the different steps of your checkout. This new DSL allows you to customize _just_ the checkout flow, while maintaining the unrelated admin states, such as "canceled" and "resumed", that an order can transition to. Ultimately, it provides a shorter syntax compared with overriding the entire state machine for the `Spree::Order` class.+Spree comes with a new checkout DSL that allows you to succinctly define the different steps of your checkout. This new DSL allows you to customize _just_ the checkout flow, while maintaining the unrelated admin states, such as "canceled" and "resumed", that an order can transition to. Ultimately, it provides a shorter syntax compared with overriding the entire state machine for the `Spree::Order` class.The default checkout flow for Spree is defined like this, adequately demonstrating the abilities of this new system:diff --git a/docs/developer/customization/v4/checkout.mdx b/docs/developer/customization/v4/checkout.mdxindex 2f59f87fad..f11b0b1921 100644--- a/docs/developer/customization/v4/checkout.mdx+++ b/docs/developer/customization/v4/checkout.mdx@@ -10,7 +10,7 @@ The Spree checkout process has been designed for maximum flexibility. It's been## The Checkout Flow DSL-Spree comes with a new checkout DSL that allows you succinctly define the different steps of your checkout. This new DSL allows you to customize _just_ the checkout flow, while maintaining the unrelated admin states, such as "canceled" and "resumed", that an order can transition to. Ultimately, it provides a shorter syntax compared with overriding the entire state machine for the `Spree::Order` class.+Spree comes with a new checkout DSL that allows you to succinctly define the different steps of your checkout. This new DSL allows you to customize _just_ the checkout flow, while maintaining the unrelated admin states, such as "canceled" and "resumed", that an order can transition to. Ultimately, it provides a shorter syntax compared with overriding the entire state machine for the `Spree::Order` class.The default checkout flow for Spree is defined like this, adequately demonstrating the abilities of this new system:diff --git a/docs/developer/upgrades/4.1-to-4.2.mdx b/docs/developer/upgrades/4.1-to-4.2.mdxindex f586b298f4..66350ced54 100644--- a/docs/developer/upgrades/4.1-to-4.2.mdx+++ b/docs/developer/upgrades/4.1-to-4.2.mdx@@ -42,7 +42,7 @@ If you used that gem in the past you need to remove it. Multi-Currency is now inAll international configuration is now kept on the `Store` model in the database rather than in initializer files.-If you used `spree_i18n` gem before please remove any `SpreeI18n::Config`references from your `config/initializers/spree.rb` file.+If you used `spree_i18n` gem before please remove any `SpreeI18n::Config` references from your `config/initializers/spree.rb` file.## Optional Add `deface` gemdiff --git a/docs/developer/upgrades/5.2-to-5.3.mdx b/docs/developer/upgrades/5.2-to-5.3.mdxindex d575c741e1..944742dc97 100644--- a/docs/developer/upgrades/5.2-to-5.3.mdx+++ b/docs/developer/upgrades/5.2-to-5.3.mdx@@ -77,9 +77,9 @@ This rake task will enqueue background jobs to populate the product metrics for### Replace `auto_strip_attributes` gem usage-`auto_strip_attributes` gem [was removed from Spree](https://github.com/spree/spree/pull/13462) due to bugs and conflicts with translations feature. Also it's not required anymore as built-in Rails `normalizes` provides the same feature without an additional depepdency.+`auto_strip_attributes` gem [was removed from Spree](https://github.com/spree/spree/pull/13462) due to bugs and conflicts with translations feature. Also it's not required anymore as built-in Rails `normalizes` provides the same feature without an additional dependency.-If you used `auto_stripe_attributes` in your application, you will need to change it to `normalizez`, eg.+If you used `auto_strip_attributes` in your application, you will need to change it to `normalizes`, eg.Replacediff --git a/docs/user/storefront/product-listing-page.mdx b/docs/user/storefront/product-listing-page.mdxindex ba63e2513a..30c6ea48e7 100644--- a/docs/user/storefront/product-listing-page.mdx+++ b/docs/user/storefront/product-listing-page.mdx@@ -13,7 +13,7 @@ Each of these pages includes a product grid section that cannot be removed, ensu## How to Edit Product Listing Pages-To edit a PLP, first go go to **Storefront → Themes** in the admin dashboard.+To edit a PLP, first go to **Storefront → Themes** in the admin dashboard.