Skip to content

Fix link and spelling issues #28

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nnsW3 wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Fix link and spelling issues #28

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
491faa8
remove article 3-bridge-between-morph-and-ethereum.md
nnsW3 Jul 19, 2024
8b0523d
fix agreement mistake 4-understand-transaction-cost-on-morph.md
nnsW3 Jul 19, 2024
aa3ce8c
fix link 5-verify-your-smart-contracts.md
nnsW3 Jul 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/build-on-morph/build-on-morph/3-bridge-between-morph-and-ethereum.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ All Gateway contracts will form the message and send it to the `L1CrossDomainMes

This means they can execute any function on L2 from a transaction made on L1 via the bridge. Although an application could directly pass messages to existing token contracts, the Gateway abstracts the specifics and simplifies making transfers and calls.

When a new block gets created on L1, the Sequencer will detect the message on the `L1MessageQueue`, and submit the transaction to the L2 via the its L2 node. Finally, the L2 node will pass the transaction to the `L2CrossDomainMessenger` contract for execution on L2.
When a new block gets created on L1, the Sequencer will detect the message on the `L1MessageQueue`, and submit the transaction to the L2 via its L2 node. Finally, the L2 node will pass the transaction to the `L2CrossDomainMessenger` contract for execution on L2.

## Withdraw ETH and ERC20 tokens from L2

Expand Down
4 changes: 2 additions & 2 deletions docs/build-on-morph/build-on-morph/4-understand-transaction-cost-on-morph.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ The formula is straightforward:


<!--
We support [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559) as a way to process L2 transaction fee.
We support [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559) as a way to process L2 transaction fees.

In EIP-1559, the cost of a unit of gas is composed of two components:

Expand Down Expand Up @@ -172,4 +172,4 @@ See the section on [Responding to gas price updates](#responding-to-gas-price-up

This is a custom RPC error that Morph returns when a transaction is rejected because the gas price is too high.
We include this as a safety measure to prevent users from accidentally sending a transaction with an extremely high L2 gas price.
See the section on [Responding to gas price updates](#responding-to-gas-price-updates) for more information.
See the section on [Responding to gas price updates](#responding-to-gas-price-updates) for more information.
2 changes: 1 addition & 1 deletion docs/build-on-morph/build-on-morph/5-verify-your-smart-contracts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Most smart contract tools have plugins for verifying contracts on Etherscan. Blo
We provide a comprehensive example of deploying contracts on Morph using Hardhat and Foundry, which includes the verification process.


Check [Deploy Conrtacts on Morph](../code-examples/1-deploy-contract-on-morph.md) for examples.
Check [Deploy Contracts on Morph](../code-examples/1-deploy-contract-on-morph.md) for examples.

## Vefiry with Morph explorer

Expand Down