diff --git a/docs/build/getting-started/networks-endpoints.md b/docs/build/getting-started/networks-endpoints.md
index 3e24cc25382..c12e3cacdde 100644
--- a/docs/build/getting-started/networks-endpoints.md
+++ b/docs/build/getting-started/networks-endpoints.md
@@ -138,7 +138,7 @@ layer 1.
1072 |
https://evm-faucet.testnet.shimmer.network |
- https://explorer.evm.testnet.shimmer.network |
+ https://explorer.evm.testnet.shimmer.network |
diff --git a/docs/build/wasp-evm/0.7.0/docs/getting-started/compatibility.md b/docs/build/wasp-evm/0.7.0/docs/getting-started/compatibility.md
index 41256c0039a..ccc1451d661 100644
--- a/docs/build/wasp-evm/0.7.0/docs/getting-started/compatibility.md
+++ b/docs/build/wasp-evm/0.7.0/docs/getting-started/compatibility.md
@@ -30,9 +30,11 @@ Ethereum tools think they are interfacing with an actual Ethereum node, but some
## Properties and Limitations
:::warning
+
There is a difference in the decimal precision of ether (18 decimal places) to MIOTA/SMR(6 decimal places). Because of this, when sending native tokens in the EVM, which are expressed in wei (ether = 1018wei), the last 12 decimal places will be ignored.
-example: 1,999,999,999,999,999,999 wei = 1.999,999 SMR/MIOTA
+Example: 1,999,999,999,999,999,999 wei = 1.999,999 SMR/MIOTA
+
:::
Here are some of the most important properties and limitations of EVM support in IOTA Smart Contracts: