feat: more fixes

Author: ericnordelo

content/contracts-cairo/components.mdx

@@ -8,8 +8,11 @@ Starknet components are separate modules that contain storage, events, and imple
 Components themselves cannot be declared or deployed.
 Another way to think of components is that they are abstract modules that must be instantiated.
 
+[shamans_post]: https://community.starknet.io/t/cairo-components/101136#components-1
+[cairo_book]: https://book.cairo-lang.org/ch103-02-00-composability-and-components.html
+
 <Callout>
-For more information on the construction and design of Starknet components, see the [Starknet Shamans post](https://community.starknet.io/t/cairo-components/101136#components-1) and the [Cairo book](https://book.cairo-lang.org/ch103-02-00-composability-and-components.html).
+For more information on the construction and design of Starknet components, see the [Starknet Shamans post][shamans_post] and the [Cairo book][cairo_book].
 </Callout>
 
 ## Building a contract
@@ -29,7 +32,7 @@ mod MyContract {
 }
 ```
 
-The `path` argument should be the imported component itself (in this case, [InitializableComponent](/security#initializable)).
+The `path` argument should be the imported component itself (in this case, [InitializableComponent](/contracts-cairo/security#initializable)).
 The `storage` and `event` arguments are the variable names that will be set in the `Storage` struct and `Event` enum, respectively.
 Note that even if the component doesn’t define any events, the compiler will still create an empty event enum inside the component module.
 
@@ -57,7 +60,7 @@ mod MyContract {
 
 The `#[substorage(v0)]` attribute must be included for each component in the `Storage` trait.
 This allows the contract to have indirect access to the component’s storage.
-See [Accessing component storage](#accessing_component_storage) for more on this.
+See [Accessing component storage](#accessing-component-storage) for more on this.
 
 The `#[flat]` attribute for events in the `Event` enum, however, is not required.
 For component events, the first key in the event log is the component ID.
@@ -445,7 +448,7 @@ Customizing implementations and accessing component storage can potentially corr
 
 Hooks are entrypoints to the business logic of a token component that are accessible at the contract level.
 This allows contracts to insert additional behaviors before and/or after token transfers (including mints and burns).
-Prior to hooks, extending functionality required contracts to create [custom implementations](#custom_implementations).
+Prior to hooks, extending functionality required contracts to create [custom implementations](#custom-implementations).
 
 All token components include a generic hooks trait that include empty default functions.
 When creating a token contract, the using contract must create an implementation of the hooks trait.

content/contracts-cairo/index.mdx

@@ -8,8 +8,8 @@ title: Contracts for Cairo
 
 
 **A library for secure smart contract development** written in Cairo for [Starknet][starknet]. This library consists of a set of
-[reusable components](/cairo-contracts/components) to build custom smart contracts, as well as ready-to-deploy [presets](/cairo-contracts/presets). You can also
-find other [utilities](/cairo-contracts/api/utilities) including [interfaces and dispatchers](/cairo-contracts/interfaces) and [test utilities](/cairo-contracts/api/testing)
+[reusable components](/contracts-cairo/components) to build custom smart contracts, as well as ready-to-deploy [presets](/contracts-cairo/presets). You can also
+find other [utilities](/contracts-cairo/api/utilities) including [interfaces and dispatchers](/contracts-cairo/interfaces) and [test utilities](/contracts-cairo/api/testing)
 that facilitate testing with Starknet Foundry.
 
 <Callout>
@@ -59,7 +59,7 @@ The `openzeppelin` package is an umbrella (meta) package that aggregates all lib
 versioned in lockstep—their versions always matched. Starting with v3.x, following the introduction of `openzeppelin_interfaces`, the umbrella is
 versioned independently from some of the subpackages.
 
-See the [Versioning of the sub-packages](/cairo-contracts#versioning-of-the-sub-packages) section for more information.
+See the [Versioning of the sub-packages](/contracts-cairo#versioning-of-the-sub-packages) section for more information.
 
 </Callout>
 
@@ -104,7 +104,7 @@ openzeppelin_utils = "{{openzeppelin_utils_version}}"
 
 ## Basic usage
 
-This is how it looks to build an ERC20 contract using the [ERC20 component](erc20).
+This is how it looks to build an ERC20 contract using the [ERC20 component](/contracts-cairo/erc20).
 Copy the code into `src/lib.cairo`.
 
 ```rust