docs(edits): up-to-date + remove legacy docs (#4513)

Author: Ciejo

docs/docs/concepts/definitions.md

@@ -3,9 +3,6 @@
 ### Actively Validated Services (AVSes) 
 A project or protocol that needs distributed validation and acquires said validation via restaking. Examples of AVSes are middleware services, layer 2 networks, bridges, data layers, and dApps.
 
-### Composable Virtual Machine (CVM) 
-An orchestration language and execution runtime for cross-chain program execution and intents settlement that operates, specifically over IBC.
-
 ### Cross-Domain Maximal Extractible Value (MEV) 
 The maximum value that can be captured from arbitrage transactions executed in a specified order across multiple domains. See: Maximal Extractible Value.
 
@@ -24,7 +21,7 @@ Lightweight, trustless mechanisms for verifying the state of the counterparty bl
 ### Maximal Extractible Value (MEV)
 The maximal value extractable between one or more blocks, given any arbitrary re-ordering, insertion or censorship of pending or existing transactions (as defined by Obadia et al., 2021).
 
-### Multichain-Agnostic Normalized Trust-Minimized Intent Settlement (MANTIS) 
+### Multichain-Agnostic Normalized Trust-Minimized Intent Settlement ([Mantis](https://mantis.app/)) 
 A vertically integrated, optimized intents settlement framework with expression, execution, and settlement. 
 
 ### Operators 

docs/docs/concepts/ibc.md

@@ -98,7 +98,7 @@ The IBC protocol is maintained by the [Interchain Foundation](https://interchain
 
 Introduced in 2019, IBC was integrated into the Cosmos SDK in 2021. Presently, over 107 chains are interconnected, with IBC facilitating a volume of more than 5 billion USD as of December 2023, and [over 5 million token](https://mapofzones.com/home?columnKey=ibcVolume&period=24h) transfers between IBC-connected chains. These statistics underscore IBC's resilience over time and its ability to evolve its protocol to meet the needs of users and app-chains. Its widespread adoption and continued relevance within the Cosmos ecosystem have also garnered attention in the broader crypto community. 
 
-The requirements of implementing IBC are not restrictive in terms of the type of consensus algorithm, allowing it to connect various types of blockchains, such as those based on Cosmos typically powered by Tendermint/CometBFT, Ethereum-like networks, and Solana as well. Picasso's innovation is not limited to Cosmos but rather actively leveraging and extending the IBC protocol beyond Cosmos, pushing its boundaries beyond its original scope. **Picasso's approach involves establishing the IBC framework as the industry standard for cross-ecosystem communication.**
+The requirements of implementing IBC are not restrictive in terms of the type of consensus algorithm, allowing it to connect various types of blockchains, such as those based on Cosmos typically powered by Tendermint/CometBFT, Ethereum-like networks, and Solana as well. Picasso's innovation is not limited to Cosmos but rather actively leveraging and extending the IBC protocol beyond Cosmos, pushing its boundaries beyond its original scope. **Picasso's approach involves [establishing the IBC framework as the industry standard](https://medium.com/@Picasso_Network/ibc-as-the-end-game-of-bridging-a-comparison-analysis-on-trust-dcc01e0d9377) for cross-ecosystem communication.**
 
 IBC supports asset transfers (fungible tokens, non-fungible tokens), generic message passing, cross-chain contract calls, cross-chain fee payments, interchain collateralization and more in a trust-minimized manner. The trust-minimized condition of IBC is due to the fact it is:
 

docs/docs/develop/codespaces.md

@@ -16,5 +16,3 @@ This gives us the following advantages:
   uses the same dependencies that have been defined in code, and are identical to the ones used in our CI pipelines.
 - If you come up with an improvement to our development experience, you can open a PR for it and then the entire team 
 - can take advantage of it.
-
-Let's [get started with Codespaces!](./codespaces/getting-started.md)

docs/docs/develop/collator-guide.md

@@ -87,11 +87,7 @@ To see logs, run:
 sudo docker logs -f $(sudo docker ps |grep composable|awk '{print $1}')
 ```
 
-The latest version of the application can be found at [Docker hub] or [Composable releases].
-
-[Docker hub]: https://hub.docker.com/r/composablefi/composable/tags
-
-[Composable releases]: (https://github.com/ComposableFi/composable/releases/)
+The latest version of the application can be found at [Docker hub](https://hub.docker.com/r/composablefi/composable/tags) or [Composable releases](https://github.com/ComposableFi/composable/releases/).
 
 This configuration will pass the key into the Composable application at startup. Verify that it is being used by checking the log for:
 

docs/docs/develop/cosmwasm-cli.md

@@ -3,7 +3,7 @@
 Composable Cosmwasm CLI is a CLI tool to quickly get started with the ecosystem and interact with a chain that runs `pallet-cosmwasm`. In this guide, we will show you how to run the CLI on a local Picasso network and Picasso Rococo. 
 
 :::info 
-Picasso Rococo is a testnet (test network) for [Picasso](../networks/picasso-parachain-overview.md). It allows developers to experiment, test runtime module deployment, and refine their applications to ensure the stability and compatibility of new features before deploying on Picasso mainnet by interacting with the [Rococo Relay Chain](https://polkadot.network/blog/rococo-revamp-becoming-a-community-parachain-testbed/).
+Picasso Rococo is a testnet (test network) for Picasso. It allows developers to experiment, test runtime module deployment, and refine their applications to ensure the stability and compatibility of new features before deploying on Picasso mainnet by interacting with the [Rococo Relay Chain](https://polkadot.network/blog/rococo-revamp-becoming-a-community-parachain-testbed/).
 :::
 
 ## Setting up the development environemnt