Update arbitrum-docs/launch-orbit-chain/02-configure-your-chain/commo…

…n-configurations/02-customizable-challenge-period.mdx Co-authored-by: José FP <[email protected]>
OffchainLabs · Feb 6, 2025 · 410650f · 410650f
1 parent 368a9e7
commit 410650f
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/...configure-your-chain/common-configurations/02-customizable-challenge-period.mdx b/...configure-your-chain/common-configurations/02-customizable-challenge-period.mdx
@@ -44,7 +44,7 @@ By default, the extra challenge period is set to **200 blocks**, providing a sho
 Like the main challenge period, this parameter is customizable in two ways:
 
 1. **During deployment**: The value can be set in the `extraChallengeTimeBlocks` field of the RollupCreator configuration.
-2. **Post-deployment**: The chain owner can dynamically adjust the parameter using the `Rollup.setExtraChallengeTimeBlocks(newExtraTimeBlocks)` function. For example:
+2. **Post-deployment**: The chain owner can dynamically adjust the parameter using the `Rollup.setExtraChallengeTimeBlocks(newExtraTimeBlocks)` function.
 
 For example, the following command can update the extra challenge period to 300 blocks based on the parent chain’s notion of block progression: