diff --git a/develop/smart-contracts/index.md b/develop/smart-contracts/index.md
index 692d1d200..0cb535a78 100644
--- a/develop/smart-contracts/index.md
+++ b/develop/smart-contracts/index.md
@@ -18,7 +18,7 @@ For developers building smart contracts in the Polkadot ecosystem, the choice be
 
 Here are some key considerations:
 
-- [**Wasm (!ink) contracts**](/develop/smart-contracts/wasm-ink/){target=\_blank} - contracts are written in Rust and compiled to Wasm. The advantage of Wasm is that it allows for more flexibility, speed, and potentially lower execution costs compared to EVM, especially in the context of Polkadot's multi-chain architecture
+- [**Wasm (ink!) contracts**](/develop/smart-contracts/wasm-ink/){target=\_blank} - contracts are written in Rust and compiled to Wasm. The advantage of Wasm is that it allows for more flexibility, speed, and potentially lower execution costs compared to EVM, especially in the context of Polkadot's multi-chain architecture
 - [**EVM-compatible contracts**](/develop/smart-contracts/evm/parachain-contracts/){target=\_blank} - contracts are written in languages like Solidity or Vyper and executed by the Ethereum Virtual Machine (EVM). The EVM is widely standardized across blockchains, including Polkadot parachains like Astar, Moonbeam, and Acala. This compatibility allows contracts to be deployed across multiple networks with minimal modifications, benefiting from a well-established, broad development ecosystem
 - [**PolkaVM-compatible contracts**](/develop/smart-contracts/evm/native-evm-contracts/){target=\_blank} - contracts are written in languages like Solidity or Vyper and executed by the PolkaVM. This compatibility provides a seamless transition for developers coming from EVM environments while also enabling interactions with other Polkadot parachains and leveraging Polkadot's interoperability