fix links

versioned_docs/version-3.x/developer/products/overview.mdx

@@ -16,7 +16,7 @@ Products are the essential components of an order, and at least one product must
 
 ## Product and variants
 
-Variants are designed to provide variations of the product, such as size, material, color, or any other dimension that can be user-defined; if the product doesn’t have variations, you will need to create a product with a single variant because prices and stock can only be assigned at a variant level.
+Variants are designed to provide variations of the product, such as size, material, color, or any other dimension that can be user-defined; if the product has no variants, you will need to create a product with a single variant because prices and stock can only be assigned at a variant level.
 
 It might seem like it is overhead to configure twice the availability of variant and product (especially when there is only one variant), but it has an intentional purpose. First, it gives more degree of freedom per variant, and second, it is convenient when you have many variants and need to disable one all at once in a single channel.
 
@@ -36,7 +36,7 @@ Variants give level of control of
 
 ## Product types
 
-Product type is a collection of [attributes](developer/attributes/overivew.mdx) which different types of fields. For example a _Product Type_ **T-shirt** will have **Size**, **Material** and **Length** attributes.
+Product type is a collection of [attributes](developer/attributes/overview.mdx) which different types of fields. For example a _Product Type_ **T-shirt** will have **Size**, **Material** and **Length** attributes.
 
 **Material:** can be _Cotton_ or _Polyester_ and would represent a dropdown attribute, that is assigned to a product type.