Merge pull request #8481 from sukey2008/develop

Fix several minor typos

specs/safe-liveness-checking.md

@@ -25,7 +25,7 @@
 
 ## Liveness checking Mechanism
 
-The Security Security Council uses a specially extended Safe multisig contract to ensure that
+The Security Council uses a specially extended Safe multisig contract to ensure that
 any loss of access to a signer's keys is identified and addressed within a predictable period of
 time.
 
@@ -52,7 +52,7 @@ signer. This time is made publicly available by calling a `lastLive(address)(Tim
 Owners are recorded in this mapping in one of 4 ways:
 
 1. Upon deployment, the guard reads the current set of owners from the Safe contract.
-1. When a new owner is added to the safe. Similarly, when an owner is removed from the Safe, it's
+1. When a new owner is added to the safe. Similarly, when an owner is removed from the Safe, its
    entry is deleted from the mapping.
 1. When a transaction is executed, the signatures on that transaction are passed to the guard and
    used to identify the signers. If more than the required number of signatures is provided, they

specs/withdrawals.md

@@ -48,7 +48,7 @@ finalization.
 - [Security Considerations](#security-considerations)
   - [Key Properties of Withdrawal Verification](#key-properties-of-withdrawal-verification)
   - [Handling Successfully Verified Messages That Fail When Relayed](#handling-successfully-verified-messages-that-fail-when-relayed)
-  - [OptimismPortal can send abitrary messages on L1](#optimismportal-can-send-abitrary-messages-on-l1)
+  - [OptimismPortal can send arbitrary messages on L1](#optimismportal-can-send-arbitrary-messages-on-l1)
 
 <!-- END doctoc generated TOC please keep comment here to allow auto update -->
 
@@ -218,7 +218,7 @@ contracts if desired.
 [`WithdrawalTransaction` type]: https://github.com/ethereum-optimism/optimism/blob/08daf8dbd38c9ffdbd18fc9a211c227606cdb0ad/packages/contracts-bedrock/src/libraries/Types.sol#L62-L69
 [`OutputRootProof` type]: https://github.com/ethereum-optimism/optimism/blob/08daf8dbd38c9ffdbd18fc9a211c227606cdb0ad/packages/contracts-bedrock/src/libraries/Types.sol#L25-L30
 
-### OptimismPortal can send abitrary messages on L1
+### OptimismPortal can send arbitrary messages on L1
 
 The `L2ToL1MessagePasser` contract's `initiateWithdrawal` function accepts a `_target` address and `_data` bytes,
 which is passed to a `CALL` opcode on L1 when `finalizeWithdrawalTransaction` is called after the challenge