docs: update override price selection strategy documentation (#5438)

* docs: update override price selection strategy documentation

* fix eslint errors

www/apps/docs/content/development/batch-jobs/index.mdx

@@ -21,7 +21,7 @@ You can also create a custom batch job or overwrite Medusa’s batch jobs.
 
 ### BatchJob Entity Overview
 
-A batch job is stored in the database as a [BatchJob](../../references/entities/classes/BatchJob) entity. Some of its important attributes are:
+A batch job is stored in the database as a [BatchJob](../../references/entities/classes/BatchJob.mdx) entity. Some of its important attributes are:
 
 - `status`: A string that determines the current status of the Batch Job.
 - `context`: An object that can be used to store configurations related to the batch job. For example, you can use it to store listing configurations such as the limit or offset of the list to be retrieved during the processing of the batch job.

www/apps/docs/content/development/events/events-list.md

@@ -1948,7 +1948,7 @@ Triggered when a payment is created.
 </td>
 <td>
 
-The entire payment passed as an object. You can refer to the [Payment entity](../../references/entities/classes/Payment.md) for an idea of what fields to expect.
+The entire payment passed as an object. You can refer to the [Payment entity](../../references/entities/classes/Payment.mdx) for an idea of what fields to expect.
 
 </td>
 </tr>
@@ -1966,7 +1966,7 @@ Triggered when a payment is updated.
 </td>
 <td>
 
-The entire payment passed as an object. You can refer to the [Payment entity](../../references/entities/classes/Payment.md) for an idea of what fields to expect.
+The entire payment passed as an object. You can refer to the [Payment entity](../../references/entities/classes/Payment.mdx) for an idea of what fields to expect.
 
 </td>
 </tr>
@@ -1984,7 +1984,7 @@ Triggered when a payment is captured.
 </td>
 <td>
 
-The entire payment passed as an object. You can refer to the [Payment entity](../../references/entities/classes/Payment.md) for an idea of what fields to expect.
+The entire payment passed as an object. You can refer to the [Payment entity](../../references/entities/classes/Payment.mdx) for an idea of what fields to expect.
 
 </td>
 </tr>
@@ -2002,7 +2002,7 @@ Triggered when the capturing of a payment fails.
 </td>
 <td>
 
-The entire payment passed as an object. You can refer to the [Payment entity](../../references/entities/classes/Payment.md) for an idea of what fields to expect.
+The entire payment passed as an object. You can refer to the [Payment entity](../../references/entities/classes/Payment.mdx) for an idea of what fields to expect.
 
 In addition, an error object is passed within the same object as the Payment Processor:
 
@@ -2034,7 +2034,7 @@ Triggered when a refund of a payment is created.
 </td>
 <td>
 
-The entire refund passed as an object. You can refer to the [Refund entity](../../references/entities/classes/Refund.md) for an idea of what fields to expect.
+The entire refund passed as an object. You can refer to the [Refund entity](../../references/entities/classes/Refund.mdx) for an idea of what fields to expect.
 
 </td>
 </tr>
@@ -2052,7 +2052,7 @@ Triggered when a payment's refund fails.
 </td>
 <td>
 
-The entire payment passed as an object. You can refer to the [Payment entity](../../references/entities/classes/Payment.md) for an idea of what fields to expect.
+The entire payment passed as an object. You can refer to the [Payment entity](../../references/entities/classes/Payment.mdx) for an idea of what fields to expect.
 
 </td>
 </tr>
@@ -2095,7 +2095,7 @@ Triggered when a payment collection is created.
 </td>
 <td>
 
-The entire payment collection passed as an object. You can refer to the [Payment Collection entity](../../references/entities/classes/PaymentCollection.md) for an idea of what fields to expect.
+The entire payment collection passed as an object. You can refer to the [Payment Collection entity](../../references/entities/classes/PaymentCollection.mdx) for an idea of what fields to expect.
 
 </td>
 </tr>
@@ -2113,7 +2113,7 @@ Triggered when a payment collection is update.
 </td>
 <td>
 
-The entire payment collection passed as an object. You can refer to the [Payment Collection entity](../../references/entities/classes/PaymentCollection.md) for an idea of what fields to expect.
+The entire payment collection passed as an object. You can refer to the [Payment Collection entity](../../references/entities/classes/PaymentCollection.mdx) for an idea of what fields to expect.
 
 </td>
 </tr>
@@ -2131,7 +2131,7 @@ Triggered when a payment collection is deleted.
 </td>
 <td>
 
-The entire payment collection passed as an object. You can refer to the [Payment Collection entity](../../references/entities/classes/PaymentCollection.md) for an idea of what fields to expect.
+The entire payment collection passed as an object. You can refer to the [Payment Collection entity](../../references/entities/classes/PaymentCollection.mdx) for an idea of what fields to expect.
 
 </td>
 </tr>
@@ -2149,7 +2149,7 @@ Triggered when a payment collection is either marked authorized or its payment s
 </td>
 <td>
 
-The entire payment collection passed as an object. You can refer to the [Payment Collection entity](../../references/entities/classes/PaymentCollection.md) for an idea of what fields to expect.
+The entire payment collection passed as an object. You can refer to the [Payment Collection entity](../../references/entities/classes/PaymentCollection.mdx) for an idea of what fields to expect.
 
 </td>
 </tr>
@@ -2216,7 +2216,7 @@ Triggered when a product and data associated with it (options, variant orders, e
 </td>
 <td>
 
-The entire product passed as an object. You can refer to the [Product entity](../../references/entities/classes/Product.md) for an idea of what fields to expect.
+The entire product passed as an object. You can refer to the [Product entity](../../references/entities/classes/Product.mdx) for an idea of what fields to expect.
 
 In one case, when the `/admin/products/{id}` API Route is used to update the product, the payload is an object of the following format:
 

www/apps/docs/content/development/notification/overview.mdx

@@ -58,7 +58,7 @@ A Notification also represents a resent notification. So, when a notification is
 
 ### Notification Entity Overview
 
-The two most important properties in the [`Notification`](../../references/entities/classes/Notification.md) entity are the `to` and `data` properties.
+The two most important properties in the [`Notification`](../../references/entities/classes/Notification.mdx) entity are the `to` and `data` properties.
 
 The `to` property is a string that represents the receiver of the Notification. For example, if the Notification was sent to an email address, the `to` property holds the email address the Notification was sent to.
 

www/apps/docs/content/development/strategies/override-strategy.md

@@ -37,7 +37,7 @@ There are other resources that provide steps specific to a strategy type:
 
 - [How to override the Cart Completion Strategy](../../modules/carts-and-checkout/backend/cart-completion-strategy.md)
 - [How to override the Tax Calculation Strategy](../../modules/taxes/backend/tax-calculation-strategy.md)
-- [How to override the Price Selection Strategy](../../modules/price-lists/backend/override-price-selection-strategy.md)
+- [How to override the Price Selection Strategy](../../modules/price-lists/backend/override-price-selection-strategy.mdx)
 - [How to override a Batch Job Strategy](../batch-jobs/customize-import.md)
 
 ---