docs: update language for withdrawals

base-org · Oct 6, 2023 · 0a55a16 · 0a55a16
1 parent 30c76e1
commit 0a55a16
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/site/docs/glossary/types.md b/site/docs/glossary/types.md
@@ -22,9 +22,9 @@ SourceHashDomain specifies whether the deposit transaction is from a deposit on
 
 An [event](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L1/OptimismPortal.sol#L73C1-L73C1) emitted from a [depositTransaction](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L1/OptimismPortal.sol#L377) call to the [OptimismPortal](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L1/OptimismPortal.sol) contract, which is used to create a [DepositTransaction](#deposittransaction) on L2.
 
-## WithdrawTransaction
+## Withdrawal
 
-A withdraw transaction is a special type of transaction format specific to the OP Stack. It is for creating L1 transactions from L2. The withdrawal flow consists of three parts. First, there is the withdraw initiating transaction which the user submits on L2 and emits a [MessagePassedEvent](#messagepassedevent). Second, there is the withdrawal proving transaction which is submitted on L1 by the user to prove legitimacy of the withdrawal. This transaction emits a [WithdrawalProvenEvent](#withdrawalprovenevent). Lastly, there is the withdrawal finalizing transaction which is submitted on L1 by the user after the fault challenge period has passed which emits a [WithdrawalFinalizedEvent](#withdrawalfinalizedevent) and executes the transaction on L1.
+A withdrawal for an OP Stack chain is an L2 to L1 transaction where L2 state is crated and can later be proven on L1. The withdrawal flow consists of three parts. First, there is the withdraw initiating transaction which the user submits on L2 and emits a [MessagePassedEvent](#messagepassedevent). Second, there is the withdrawal proving transaction which is submitted on L1 by the user to prove legitimacy of the withdrawal. This transaction emits a [WithdrawalProvenEvent](#withdrawalprovenevent). Lastly, there is the withdrawal finalizing transaction which is submitted on L1 by the user after the fault challenge period has passed which emits a [WithdrawalFinalizedEvent](#withdrawalfinalizedevent) and executes the transaction on L1.
 
 ## WithdrawalFinalizedEvent