docs: added dividers + see also section (#2899)

docs/content/advanced/backend/upgrade-guides/1-3-0.md

@@ -20,6 +20,8 @@ TYPEORM_MIGRATIONS=./node_modules/@medusajs/medusa/dist/migrations/*.js
 
 These environment variables are used in the data migration scripts in this upgrade. Make sure to replace `<DATABASE_URL>` with your PostgreSQL database URL.
 
+---
+
 ## Environment Variables
 
 In previous versions of Medusa, The server automatically loads all environment variables in the `.env` file at the root of the Medusa server.
@@ -58,6 +60,8 @@ const dotenv = require('dotenv')
  }
 ```
 
+---
+
 ## Line Item Adjustments
 
 This new version of Medusa allows store operators to adjust line items in an order or a swap which provides more customization capabilities.
@@ -76,6 +80,8 @@ For that reason, it’s essential to run the data migration script after upgradi
 node ./node_modules/@medusajs/medusa/dist/scripts/line-item-adjustment-migration.js
 ```
 
+---
+
 ## Advanced Discount Conditions
 
 This new version of Medusa holds advanced promotions functionalities to provide store operators with even more customization capabilities when creating discounts. You can now add even more conditions to your discounts to make them specific for a set of products, collections, customer groups, and more.

docs/content/advanced/backend/upgrade-guides/1-3-6.md

@@ -26,6 +26,8 @@ TYPEORM_MIGRATIONS=./node_modules/@medusajs/medusa/dist/migrations/*.js
 
 These environment variables are used in the data migration scripts in this upgrade. Make sure to replace `<DATABASE_URL>` with your PostgreSQL database URL.
 
+---
+
 ## Sales Channels
 
 Sales Channels were introduced in v1.3.5 guarded by a [feature flag](../feature-flags/toggle.md). By enabling Sales Channels, developers and users can associate products and other entities with a specific Sales Channel.

docs/content/advanced/backend/upgrade-guides/1-3-8.md

@@ -10,6 +10,8 @@ Updating your medusa server to version `1.3.8` may cause issues when using NPM.
 
 It's highly recommended to use [yarn](https://yarnpkg.com/) when working with Medusa. Updating with yarn should resolve any issues you might run into during the update.
 
+---
+
 ## Resolving Update Issues with NPM
 
 ### Update All Medusa Dependencies

docs/content/advanced/backend/upgrade-guides/1-6-1.md

@@ -12,6 +12,8 @@ As the new version `1.6.1` make changes to the database schema, it is required t
 
 Without running the migrations, you might have trouble accessing and using the Medusa admin.
 
+---
+
 ## Actions Required
 
 After updating your server, run migrations with the following command:

docs/content/advanced/backend/upgrade-guides/1-7-0.md

@@ -12,6 +12,8 @@ In this new version, the method [`retrieveByEmail` in the Customer Service](../.
 
 In addition, after introducing the Claim Order feature, this version of Medusa introduces changes in the database that allows two customers having the same email based on the value of the `has_account` field. This change requires running migrations after the update.
 
+---
+
 ## Actions Required
 
 ### Run Migrations

docs/content/advanced/backend/upgrade-guides/1-7-1.md

@@ -14,6 +14,8 @@ With this introduction, the previous use of `EventBus` to create a cron job has
 
 In addition, this version features some fixes to gift cards that requires running migrations, and changes to how payment providers are implemented.
 
+---
+
 ## Actions Required
 
 ### Run Migrations

docs/content/advanced/backend/upgrade-guides/admin/admin-vite.md

@@ -12,6 +12,8 @@ Medusa Admin previously was built using Gatsby. As of a recent update, the Admin
 
 This introduced breaking changes related to environment variables used and the published directory. Read below for actions required following this update.
 
+---
+
 ## Required Node.js Version
 
 <!-- vale docs.Numbers = NO -->
@@ -20,6 +22,8 @@ Following the change to Vite 3, the required Node.js version for the Admin has c
 
 <!-- vale docs.Numbers = YES -->
 
+---
+
 ## Changed Environment Variables
 
 Previously, the Medusa Admin used the environment variables `GATSBY_MEDUSA_BACKEND_URL` or `GATSBY_STORE_URL` to store the Medusa server’s URL.
@@ -36,6 +40,8 @@ Change your `GATSBY_MEDUSA_BACKEND_URL` or `GATSBY_STORE_URL` environment variab
 MEDUSA_BACKEND_URL=<YOUR_MEDUSA_SERVER_URL>
 ```
 
+---
+
 ## Changed Publish Directory
 
 Previously, the build output of the Medusa Admin was placed in the `dist` directory. After this update, the build output is placed in the `public` directory.