Apply suggestions

Author: 0xLucca

develop/parachains/customize-parachain/add-smart-contract-functionality.md

@@ -42,7 +42,7 @@ Now that you understand how to enable smart contract functionality in your block
 
     ---
 
-    Learn how developers can build smart contracts on Polkadot by leveraging either Wasm/ink! or EVM contracts across many parachains.
+    Learn how developers can build smart contracts on Polkadot by leveraging the PolkaVM, Wasm/ink! or EVM contracts across many parachains.
 
     [:octicons-arrow-right-24: Reference](/develop/smart-contracts/overview/)
 
@@ -52,14 +52,14 @@ Now that you understand how to enable smart contract functionality in your block
 
     Learn to build Wasm smart contracts with ink!, a Rust-based eDSL. Explore installation, contract structure, and key features.
 
-    [:octicons-arrow-right-24: Reference](/develop/smart-contracts/wasm-ink/)
+    [:octicons-arrow-right-24: Reference](/develop/smart-contracts/overview#wasm-ink)
 
 -   <span class="badge guide">Guide</span> __EVM Contracts__
 
     ---
 
     Learn how Polkadot parachains such as Moonbeam, Astar, Acala, and Manta leverage the Ethereum Virtual Machine (EVM) and integrate it into their parachains.
 
-    [:octicons-arrow-right-24: Reference](/develop/smart-contracts/evm/)
+    [:octicons-arrow-right-24: Reference](/develop/smart-contracts/overview#parachain-contracts)
 
 </div>

develop/parachains/deployment/coretime-renewal.md

@@ -81,7 +81,7 @@ To determine your parachain's sovereign account address, you can:
 
         - For sibling chains - `0x7369626c` (decodes to `b"sibl"`)
 
-    2. Encode your parachain ID as a u32 [SCALE](https://docs.polkadot.com/polkadot-protocol/basics/data-encoding/#data-types){target=\_blank} value:
+    2. Encode your parachain ID as a u32 [SCALE](/polkadot-protocol/parachain-basics/data-encoding#data-types){target=\_blank} value:
 
         - For parachain 2000, this would be `d0070000`
 

develop/parachains/maintenance/unlock-parachain.md

@@ -92,7 +92,7 @@ You can identify your parachain's sovereign account using either of these method
 
         - For parent/child chains use the prefix `0x70617261` (which decodes to `b"para"`)
          
-    2. Encode your parachain ID as a u32 [SCALE](/polkadot-protocol/basics/data-encoding/#data-types){target=\_blank} value:
+    2. Encode your parachain ID as a u32 [SCALE](/polkadot-protocol/parachain-basics/data-encoding#data-types){target=\_blank} value:
 
         - For parachain 2006, this would be `d6070000`
 

develop/smart-contracts/libraries/ethers-js.md

@@ -101,7 +101,7 @@ With the provider set up, you can start querying the blockchain. For instance, t
 
 --8<-- 'text/smart-contracts/code-size.md'
 
-The `revive` compiler transforms Solidity smart contracts into [PolkaVM](/develop/smart-contracts/native-evm-contracts/#polkavm){target=\_blank} bytecode for deployment on Polkadot Hub. Revive's Ethereum RPC interface allows you to use familiar tools like Ethers.js and MetaMask to interact with contracts.
+The `revive` compiler transforms Solidity smart contracts into [PolkaVM](/develop/smart-contracts/overview#native-smart-contracts){target=\_blank} bytecode for deployment on Polkadot Hub. Revive's Ethereum RPC interface allows you to use familiar tools like Ethers.js and MetaMask to interact with contracts.
 
 ### Install the Revive Library
 

polkadot-protocol/architecture/polkadot-chain/pos-consensus.md

@@ -38,7 +38,7 @@ Key features of BABE include:
 
 - **Epochs and slots** - BABE operates in phases called epochs, each of which is divided into slots (around 6 seconds per slot). Validators are assigned slots at the beginning of each epoch based on stake and randomness
 
-- **Randomized block production** - validators enter a lottery to determine which will produce a block in a specific slot. This randomness is sourced from the relay chain's [randomness cycle](/polkadot-protocol/basics/randomness/){target=\_blank}
+- **Randomized block production** - validators enter a lottery to determine which will produce a block in a specific slot. This randomness is sourced from the relay chain's [randomness cycle](/polkadot-protocol/parachain-basics/randomness/){target=\_blank}
 
 - **Multiple block producers per slot** - in some cases, more than one validator might win the lottery for the same slot, resulting in multiple blocks being produced. These blocks are broadcasted, and the network's fork choice rule helps decide which chain to follow
 

polkadot-protocol/parachain-basics/node-and-runtime.md

@@ -74,7 +74,7 @@ The runtime performs several critical functions, such as:
 
 ## Communication Between Node and Runtime
 
-The client and runtime communicate exclusively using [SCALE-encoded](/polkadot-protocol/basics/data-encoding){target=\_blank} communication. This ensures efficient and compact data exchange between the two components.
+The client and runtime communicate exclusively using [SCALE-encoded](/polkadot-protocol/parachain-basics/data-encoding){target=\_blank} communication. This ensures efficient and compact data exchange between the two components.
 
 ### Runtime APIs
 

polkadot-protocol/smart-contract-basics/overview.md

@@ -68,7 +68,7 @@ The Polkadot SDK supports multiple smart contract execution environments:
 
 ### PolkaVM Contracts
 
-A component of the Asset Hub parachain, PolkaVM helps enable the deployment of Solidity-based smart contracts directly on Asset Hub. Learn more about how this cutting edge virtual machine facilitates using familiar EVM contracts and tools with Asset Hub by visiting the [Native EVM Contracts](/develop/smart-contracts/evm/native-evm-contracts/){target=\_blank} guide.
+A component of the Asset Hub parachain, PolkaVM helps enable the deployment of Solidity-based smart contracts directly on Asset Hub. Learn more about how this cutting edge virtual machine facilitates using familiar Ethereum-compatible contracts and tools with Asset Hub by visiting the [Native Smart Contracts](/develop/smart-contracts/overview#native-smart-contracts){target=\_blank} guide.
 
 ### EVM Contracts