Update arbitrum-docs/launch-orbit-chain/concepts/chain-ownership.md

OffchainLabs · Oct 16, 2023 · 0969a91 · 0969a91
1 parent 5d928dd
commit 0969a91
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/arbitrum-docs/launch-orbit-chain/concepts/chain-ownership.md b/arbitrum-docs/launch-orbit-chain/concepts/chain-ownership.md
@@ -40,7 +40,7 @@ Upgrades occur via a chain owner initiating a call to an Upgrade Executor, which
 
 Chain owners can either call [UpgradeExecutor.executeCall](https://github.com/OffchainLabs/upgrade-executor/blob/a8d3020c2771d164ebd323b1d99249049fe749f9/src/UpgradeExecutor.sol#L73), which will in turn call the target contract directly, or [UpgradeExecutor.execute](https://github.com/OffchainLabs/upgrade-executor/blob/a8d3020c2771d164ebd323b1d99249049fe749f9/src/UpgradeExecutor.sol#L57), which will delegate-call to an "action contract" and use its code to call the target contract.
 
-### Ownership Flexibility
+### Ownership flexibility
 
 A chain owner is simply an address; it is set by the Orbit chain's deployer and can represent any sort of governance scheme. I.e., it could be an EOA (as is set via the [Orbit Quickstart](../orbit-quickstart.md)), a Multisig, a governance token system, etc.