diff --git a/guides/source/developers/events/overview.html.md b/guides/source/developers/events/overview.html.md
index f9d301099ec..3f83d36bc17 100644
--- a/guides/source/developers/events/overview.html.md
+++ b/guides/source/developers/events/overview.html.md
@@ -20,7 +20,7 @@ Currently, the events fired by default in Solidus are:
 
 Events make extending Solidus with custom behavior easy. For example,
 if besides the standard email you also want to send a SMS text message to
-the customer when a order is finalized, this pseudo-code may do the trick:
+the customer when an order is completed, this pseudo-code may do the trick:
 
 ```ruby
 Spree::Event.subscribe 'order_finalized' do |event|
@@ -31,7 +31,7 @@ end
 
 ## Changing the adapter
 
-The adapter can be changed using this code, for example in a initializer:
+The adapter can be changed using this code, for example in an initializer:
 
 ```ruby
 Spree::Config.events.adapter = "Spree::EventBus.new"
@@ -39,7 +39,7 @@ Spree::Config.events.adapter = "Spree::EventBus.new"
 
 ## Subscribing to events
 
-`Spree::Event.subscribe` allows to subscribe to a certain event. The event
+`Spree::Event.subscribe` allows you to subscribe to a certain event. The event
 name is mandatory, the optional block will be executed every time the event
 is fired:
 
diff --git a/guides/source/developers/preferences/add-model-preferences.html.md b/guides/source/developers/preferences/add-model-preferences.html.md
index 371c249d08c..b538356ada0 100644
--- a/guides/source/developers/preferences/add-model-preferences.html.md
+++ b/guides/source/developers/preferences/add-model-preferences.html.md
@@ -45,7 +45,7 @@ the preferences attribute gets serialized into a Hash and merged with the defaul
   kind of object would a store want multiple custom preferences on?
 -->
 
-## Supported type for preferences
+## Supported types for preferences
 
 For each preference you define, a data type should be provided. The available
 types are:
@@ -98,7 +98,7 @@ class AddPreferencesToSubscriptionRules < ActiveRecord::Migration[5.0]
 end
 ```
 
-Your new `preferences` column should be the type `text`.
+Your new `preferences` column should have the type `text`.
 
 Then, you can run the migration:
 
diff --git a/guides/source/developers/preferences/class-extension-points.html.md b/guides/source/developers/preferences/class-extension-points.html.md
index 89b82d8a2a1..ed0c7ae301a 100644
--- a/guides/source/developers/preferences/class-extension-points.html.md
+++ b/guides/source/developers/preferences/class-extension-points.html.md
@@ -72,7 +72,7 @@ Spree.config do |config|
 end
 ```
 
-Now, when search is built it uses your extended `MyStore::ProductSearch`
+Now, when the search is built it uses your extended `MyStore::ProductSearch`
 functionality instead of the default functionality.
 
 [search-base]: https://github.com/solidusio/solidus/blob/v2.4/core/lib/spree/core/search/base.rb
diff --git a/guides/source/developers/returns/return-items.html.md b/guides/source/developers/returns/return-items.html.md
index 80a730a7f4b..60cd3fd39ad 100644
--- a/guides/source/developers/returns/return-items.html.md
+++ b/guides/source/developers/returns/return-items.html.md
@@ -30,7 +30,7 @@ A `Spree::ReturnItem` has the following attributes:
 - `exchange_inventory_unit_id`: If the `Spree::ReimbursementType` is an
   exchange, this attribute's value is the ID of the `Spree::InventoryUnit` that
   that is going to be exchanged.
-- `acceptance_status_errors`: A hash that lists reasons why the return item does
+- `acceptance_status_errors`: A hash that lists reasons why the return item
   is not acceptable.
 - `preferred_reimbursement_type_id`: The ID for the reimbursement type that was
   originally set for the return item.
diff --git a/guides/source/users/settings/stores.html.md b/guides/source/users/settings/stores.html.md
index fd7df3a84e1..f2f0a238bff 100644
--- a/guides/source/users/settings/stores.html.md
+++ b/guides/source/users/settings/stores.html.md
@@ -4,7 +4,7 @@ The **Settings > Stores** page allows you to manage some of the global settings
 across all of your stores. These settings are useful if you manage multiple
 stores and need distinct settings for some of your stores.
 
-The following settings are available for each for your stores:
+The following settings are available for each of your stores:
 
 - **Site Name**: The customer-facing name of the current store.
 - **Code**: An identifier for your store. Developers may need it if you operate
@@ -12,7 +12,7 @@ The following settings are available for each for your stores:
   your store's developers.
 - **SEO Title**: The content for the homepage's HTML `<title>` tag, which is
   used by search engines.
-- **Meta Keywords**: A list of keywords that should be added to this product's
+- **Meta Keywords**: A list of keywords that should be added to this store's
   metadata. These meta keywords are used by search engines.[^meta-keywords]
 - **Meta Description**: The summary text that accompanies your homepage in
   search engine results.[^meta-descriptions]
diff --git a/guides/source/users/settings/zones.html.md b/guides/source/users/settings/zones.html.md
index 58181e6f81b..7d5c11ac805 100644
--- a/guides/source/users/settings/zones.html.md
+++ b/guides/source/users/settings/zones.html.md
@@ -26,7 +26,7 @@ that only consists of the United States) or many members (a zone that consists
 of all of the non-contiguous United States: Hawaii and Alaska).
 
 Zones allow you to set shipping rules and tax rates for specific places. They
-also allow you group states or countries in a non-geographic way: for example,
+also allow you to group states or countries in a non-geographic way: for example,
 if you ship to all of the United States but use different carriers when shipping
 to Alaska and Hawaii.
 
diff --git a/guides/source/users/stock/overview.html.md b/guides/source/users/stock/overview.html.md
index 5634a5d9a3e..aecc1585a4b 100644
--- a/guides/source/users/stock/overview.html.md
+++ b/guides/source/users/stock/overview.html.md
@@ -12,6 +12,7 @@ Note that you can also [view stock in a product context][product-stock].
 <!-- TODO: Add screenshot of the stock UI, emphasizing the edit buttons -->
 
 [product-stock]: ../products/product-stock.html
+[products]: ../products.html
 
 ## Stock information
 
@@ -30,6 +31,8 @@ items:
 - **Count On Hand**: The number of items that a stock location has of the
     current item. See [Count on hand](#count-on-hand) for more information.
 
+[variants]: ../products/variants.html
+
 ## Filter and search
 
 You can search for specific stock items. This makes locating stock information
@@ -44,10 +47,12 @@ following values:
     "Yellow" to find all of the variants with a "Yellow" option value.
 
 Note that the **Variant** filter searches for option **Name** values
-as well as their **Presentation** values. For example, you may an option value
+as well as their **Presentation** values. For example, you may have an option value
 with the name "Extra Large" that is presented as "XL" on your storefront. This
 means that you can search for either term and find the same results.
 
+[option-values]: ../products/option-types.html
+
 ## Stock locations
 
 Stock locations represent a location where your inventory is shipped from. For