DEVDOCS-6658 Fix issues in b2b-edition and start docs

docs/b2b-edition/authentication/hosted-auth.mdx

@@ -58,7 +58,7 @@ User-specific tokens can be generated by the **deprecated** [Get a Server to Ser
 
 Server to server tokens can be configured to expire using this endpoint to set a fixed validity period using the `endAt` field in the request. For more information, see [Server-to-Server Authentication](/b2b-edition/apis/rest-management/authentication).
 
-<Callout type= "warning">
+<Callout type="warning">
    This endpoint generates an `authToken`, which is deprecated. In addition, it does not support users with custom system user roles, even if those roles have API account creation permissions.
 </Callout> 
 

docs/b2b-edition/docs/buyer-portal/overview.mdx

@@ -13,8 +13,8 @@ Whether you use BigCommerce’s Stencil theme engine, the Catalyst storefront ex
 
 
 ## Supported storefront models
-- **Stencil:** Embed and control the Buyer Portal via header/footer scripts and theme hooks. See the [Stencil guide](/b2b-edition/docs/buyer-portal/stencil).
-- **Headless (self-hosted):** Run and deploy the open-source Buyer Portal next to your headless storefront. See the [Headless guide](/b2b-edition/docs/buyer-portal//headless).
+- **Stencil:** Embed and control the Buyer Portal via header/footer scripts and theme hooks. See the [Stencil guide](/docs/b2b-edition/docs/buyer-portal/stencil).
+- **Headless (self-hosted):** Run and deploy the open-source Buyer Portal next to your headless storefront. See the [Headless guide](/docs/b2b-edition/docs/buyer-portal/headless).
 - **Catalyst:** Render the Buyer Portal on top of Catalyst and wire authentication. See the [Catalyst guide](/docs/storefront/catalyst/experiments/b2b).
 
 ## Prerequisites

docs/start/authentication/customer-login.mdx

@@ -161,8 +161,8 @@ const jwt = require('jsonwebtoken');
 const {v4: uuidv4} = require('uuid');
 
 function getLoginUrl(customerId, storeHash, storeUrl, clientId, clientSecret) {
-   const dateCreated = Math. round((new Date()). getTime() / 1000);
-   const  payload = {
+   const dateCreated = Math.round((new Date()).getTime() / 1000);
+   const payload = {
        "iss": clientId,
        "iat": dateCreated,
        "jti": uuidv4(),

docs/start/best-practices/integration-design.mdx

@@ -12,7 +12,7 @@ To maintain service quality at scale, BigCommerce observes API traffic. We reser
 
 **Make as few calls as possible; request only information that your app requires to function.**
 
-When interacting with a resource on a store, consider how many calls it takes to accomplish the goal. When you fetch information, investigate whether you can use a bulk endpoint instead of retrieving resources one by one. If possible, use the bulk endpoint and filter the data to retrieve only what you need. For example, the [REST Catalog API](/docs/rest-catalog/products) contains both [Get a product](/docs/rest-catalog/products#get-a-product) and [Get all products](/docs/rest-content/pages#get-pages). If your app or storefront requests one or more products, you can use [Get all products](/docs/rest-content/pages#get-pages) and filter which products you'd like to retrieve using the `id:in` query parameter.
+When interacting with a resource on a store, consider how many calls it takes to accomplish the goal. When you fetch information, investigate whether you can use a bulk endpoint instead of retrieving resources one by one. If possible, use the bulk endpoint and filter the data to retrieve only what you need. For example, the [REST Catalog API](/docs/rest-catalog/products) contains both [Get a product](/docs/rest-catalog/products#get-a-product) and [Get all products](/docs/rest-catalog/products#get-all-products). If your app or storefront requests one or more products, you can use [Get all products](/docs/rest-catalog/products#get-all-products) and filter which products you'd like to retrieve using the `id:in` query parameter.
 
 The same principle applies to bulk endpoints. The base number of resources returned from a bulk request is 50. If you need to retrieve 5,000 products, the default response pagination limit requires you to make 100 API calls to the bulk endpoint. Instead, you can use query parameters to set the response limit to 250 and request the same information in 20 calls.
 
@@ -79,7 +79,7 @@ To handle 503 statuses and cases when multiple URIs return 500 statuses, conside
 * [Retry headers](/docs/start/about#bigcommerce-specific-response-headers)
 * [REST Catalog API](/docs/rest-catalog/products)
   * [Get a product](/docs/rest-catalog/products#get-a-product)
-  * [Get all products](/docs/rest-content/pages#get-pages)
+  * [Get all products](/docs/rest-catalog/products#get-all-products)
 * [Webhooks](/docs/webhooks)
 
 ### External resources

docs/start/migration/orders/migration-phase.mdx

@@ -5,7 +5,7 @@ keywords: order migration, migration phase, testing, delta migration, BigCommerc
 ---
 # Migration Phase
 
-Just as with products, your order migration should include at minimum: testing, initial migration, delta migration. The initial testing process and delta migration will look very similar to those steps in the products migration process, so you can refer back to them as needed. (Load Complete Data)[/docs/start/migration/products/complete-migration] and (Go Live and Delta Migration)[/docs/start/migration/products/delta-migration].
+Just as with products, your order migration should include at minimum: testing, initial migration, delta migration. The initial testing process and delta migration will look very similar to those steps in the products migration process, so you can refer back to them as needed. [Load Complete Data](/docs/start/migration/products/complete-migration) and [Go Live and Delta Migration](/docs/start/migration/products/delta-migration).
 
 There are some callouts specific to the order migration process, which will be addressed here, but otherwise, use your best judgement when considering how to manage your own work.