diff --git a/reference/geography.v2.yml b/reference/geography.v2.yml
index 3214a4e7e..64cf350a9 100644
--- a/reference/geography.v2.yml
+++ b/reference/geography.v2.yml
@@ -248,7 +248,7 @@ paths:
       tags:
         - States
       description: Returns a count of all states.
-  '/stores/{store_hash}/v2/countries/states':
+  '/countries/states':
     get:
       operationId: get-all-states
       responses:
diff --git a/reference/orders.v2.oas2.yml b/reference/orders.v2.oas2.yml
index ba0591a5b..22bdc2e3a 100644
--- a/reference/orders.v2.oas2.yml
+++ b/reference/orders.v2.oas2.yml
@@ -6,7 +6,6 @@ info:
     Manage order coupons, messages, products, shipping addresses, statuses, taxes, shipments, and shipping address quotes.
     
     ## Order
-    The Order object contains a record of the purchase agreement between a shopper and a merchant. To learn more about creating orders, see the [Orders Overview](/docs/store-operations/orders).
     
     The Order object contains a record of the purchase agreement between a shopper and a merchant. To learn more about creating orders, see [Orders API Guide](/docs/store-operations/orders).
     
@@ -97,7 +96,6 @@ paths:
         To update a product in an order, include `id` in the body. The body should only contain the fields that need to be updated. Those fields that are omitted will not be changed.
         
         To remove a product from an order, set that product’s `quantity` to `0`.
-        To learn more about creating or updating orders, see the [Orders Overview](/docs/store-operations/orders).
         
         To learn more about creating or updating orders, see [Orders Overview](/docs/store-operations/orders).
       summary: Update an Order
@@ -215,8 +213,6 @@ paths:
         Gets a list of orders using the filter query.
         
         **Notes**
-        * The default sort is by order ID, from lowest to highest.
-        * By default, requests sent without parameters return 50 orders. 
         
         * The default sort is by order id, from lowest to highest.
         * By default, requests sent without parameters will only return 50 orders. 
@@ -3766,7 +3762,7 @@ components:
           type: string
           description: |-
             IPv4 Address of the customer, if known.
-          
+
             Note: You can set either `ip_address` or `ip_address_v6`. Setting the `ip_address` value will reset the `ip_address_v6` value and vice versa.
           example: 12.345.678.910
           maxLength: 30
@@ -3774,7 +3770,7 @@ components:
           type: string
           description: |-
             IPv6 Address of the customer, if known.
-          
+
             Note: You can set either `ip_address` or `ip_address_v6`. Setting the `ip_address_v6` value will reset the `ip_address` value and vice versa.
           example: '2001:db8:3333:4444:5555:6666:7777:8888'
           maxLength: 39
@@ -4111,10 +4107,10 @@ components:
       title: Custom product
       description: |-
         **Usage notes:**
-      
+
         To `add` a custom product to an existing order, don't include `id` in the payload. You must provide a non-empty value for at least one of these fields: `name`, `name_customer`, or `name_merchant`.
         To `update` an order product line, `id` is required. The payload should only contain the fields that need to be updated. You cannot change omitted fields.
-      
+
         Note the following constraints and default field values:
          - Empty strings `''` and `null` are invalid for `xxx`, `xxx_customer`, and `xxx_merchant`.
          - `name` and `name_customer` always hold the same value; updating either `name` or `name_customer` will change the value for both of those fields.
@@ -4163,7 +4159,7 @@ components:
         
          To `add` a product to an existing order, don't include `id` in the payload. When adding a product with variants, `product_options` are required.
          To `update` an order product line, `id` is required. The payload should only contain the fields that need to be updated. The fields that you omit will not be changed.
-         
+
          Note the following constraints and default field values:
          - `xxx` and `xxx_customer` always hold the same value. Updating either `xxx` or `xxx_customer` will change the value of both fields.
          - If both fields `xxx` and `xxx_customer` are present, they must have same value.