fix: links in components

Author: ericnordelo

content/contracts-cairo/components.mdx

@@ -131,9 +131,9 @@ By adding the embed attribute, `is_initialized` becomes a contract entrypoint fo
 
 
 Embeddable implementations, when available in this library’s components, are segregated from the internal component implementation which makes it easier to safely expose.
-Components also separate granular implementations from [mixin](/components#mixins) implementations.
+Components also separate granular implementations from [mixin](/contracts-cairo/components#mixins) implementations.
 The API documentation design reflects these groupings.
-See [ERC20Component](/api/erc20#ERC20Component) as an example which includes:
+See [ERC20Component](/contracts-cairo/api/erc20#erc20component) as an example which includes:
 
 * **Embeddable Mixin Implementation**
 * **Embeddable Implementations**
@@ -238,7 +238,7 @@ Always read the API documentation for each integrated component.
 Some components require some sort of setup upon construction.
 Usually, this would be a job for a constructor; however, components themselves cannot implement constructors.
 Components instead offer ``initializer``s within their `InternalImpl` to call from the contract’s constructor.
-Let’s look at how a contract would integrate [OwnableComponent](/api/access#OwnableComponent):
+Let’s look at how a contract would integrate [OwnableComponent](/contracts-cairo/api/access#ownablecomponent):
 
 ```rust
 #[starknet::contract]
@@ -283,7 +283,7 @@ constants declared in the component, customizing its functionality.
 The Immutable Component Config standard is defined in the SRC-107.
 </Callout>
 
-Here’s an example of how to use the Immutable Component Config pattern with the [ERC2981Component](/api/token_common#ERC2981Component):
+Here’s an example of how to use the Immutable Component Config pattern with the [ERC2981Component](/contracts-cairo/api/token_common#erc2981component):
 
 ```rust
 #[starknet::contract]
@@ -391,7 +391,7 @@ on how to use this function, refer to the [validate section of the SRC-107](http
 
 Some components include dependencies of other components.
 Contracts that integrate components with dependencies must also include the component dependency.
-For instance, [AccessControlComponent](/api/access#AccessControlComponent) depends on [SRC5Component](/api/introspection#SRC5Component).
+For instance, [AccessControlComponent](/contracts-cairo/api/access#accesscontrolcomponent) depends on [SRC5Component](/contracts-cairo/api/introspection#src5component).
 Creating a contract with `AccessControlComponent` should look like this:
 
 ```rust
@@ -563,7 +563,7 @@ mod ERC20Pausable {
 The first thing to notice is that the contract imports the interfaces of the implementations that will be customized.
 These will be used in the next code example.
 
-Next, the contract includes the [ERC20Component](/api/erc20#ERC20Component) implementations; however, `ERC20Impl` and `ERC20CamelOnlyImpl` are **not** embedded.
+Next, the contract includes the [ERC20Component](/contracts-cairo/api/erc20#erc20component) implementations; however, `ERC20Impl` and `ERC20CamelOnlyImpl` are **not** embedded.
 Instead, we want to expose our custom implementation of an interface.
 The following example shows the pausable logic integrated into the ERC20 implementations: