diff --git a/content/00.build/65.developer-reference/30.ethereum-differences/60.contract-deployment.md b/content/00.build/65.developer-reference/30.ethereum-differences/60.contract-deployment.md
index 4804627a..8088da3e 100644
--- a/content/00.build/65.developer-reference/30.ethereum-differences/60.contract-deployment.md
+++ b/content/00.build/65.developer-reference/30.ethereum-differences/60.contract-deployment.md
@@ -22,9 +22,9 @@ through EIP712 transactions, with the `factory_deps` field containing the byteco
 
 **How deploying contracts works on Ethereum.**
 
-To deploy a contract on Ethereum, a user sends a transaction to the zero address
-(`0x000...000`) with the `data` field of the transaction equal to the contract
-bytecode concatenated with the constructor parameters.
+To deploy a contract on Ethereum, a user sends a transaction with the empty `to` field
+and with the `data` field of the transaction equal to the contract creation bytecode
+concatenated with the constructor parameters.
 
 **How deploying contracts works on ZKsync.**