fix: interfaces and dispatchers

Author: ericnordelo

content/contracts-cairo/guides/interfaces-and-dispatchers.mdx

@@ -8,8 +8,8 @@ Interfaces can be found in the `openzeppelin_interfaces` package modules, such a
 
 <Callout>
 Starting from version `3.x.x`, OpenZeppelin Contracts for Cairo interfaces have been separated from their implementation modules into a dedicated package.
+This architectural change brings several important benefits. Check the [Interfaces module](../interfaces) section for more information.
 </Callout>
-This architectural change brings several important benefits. Check the [Interfaces](interfaces) section for more information.
 
 For example:
 
@@ -57,8 +57,9 @@ the ERC20 preset that includes functions from different standards such as `IERC2
 
 <Callout>
 The library offers an ABI trait for most components, providing all external function signatures
+even when most of the time all of them don’t need to be implemented at the same time. This can be helpful when interacting with
+a contract implementing the component, instead of defining a new dispatcher.
 </Callout>
-even when most of the time all of them don’t need to be implemented at the same time. This can be helpful when interacting with a contract implementing the component, instead of defining a new dispatcher.
 
 ```rust
 #[starknet::interface]
@@ -100,16 +101,16 @@ Other types of dispatchers are also auto-generated from the annotated trait. See
 
 <Callout>
 In the example, the `IERC20Dispatcher` is the one used to interact with contracts, but the
-</Callout>
 `IERC20DispatcherTrait` needs to be in scope for the functions to be available.
+</Callout>
 
 ## Dual interfaces
 
 <Callout type='warn'>
-`camelCase` functions are deprecated and maintained only for Backwards Compatibility.
-</Callout>
+The `camelCase` functions are deprecated and maintained only for backwards compatibility.
 It’s recommended to only use `snake_case` interfaces with contracts and components. The `camelCase` functions will be removed in
 future versions.
+</Callout>
 
 Following the [Great Interface Migration](https://community.starknet.io/t/the-great-interface-migration/92107) plan, we added `snake_case` functions to all of our preexisting `camelCase` contracts with the goal of eventually dropping support for the latter.