From 64f95561d7cfc8acb1b011ecd09e849a01d69925 Mon Sep 17 00:00:00 2001 From: David Lehuby Date: Fri, 17 May 2024 14:18:16 +1000 Subject: [PATCH] Fix Info boxes --- .../migrating-archive-database-to-berkeley.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/berkeley-upgrade/archive-migration/migrating-archive-database-to-berkeley.mdx b/docs/berkeley-upgrade/archive-migration/migrating-archive-database-to-berkeley.mdx index 7d60aed16..304a0068b 100644 --- a/docs/berkeley-upgrade/archive-migration/migrating-archive-database-to-berkeley.mdx +++ b/docs/berkeley-upgrade/archive-migration/migrating-archive-database-to-berkeley.mdx @@ -386,7 +386,7 @@ You must use `--fork-state-hash` as an additional parameter to the **berkeley-mi :::info The migrated database output from this stage of the final migration is required to initialize your archive nodes on the upgraded network. -:::info +::: #### Phase 1: Berkeley migration app run @@ -423,8 +423,10 @@ where: `--fork-state-hash`: fork state hash -**Info** When you run the **berkeley-migration** app with fork-state-hash, there is no requirement for the fork state block to be canonical. +:::info +When you run the **berkeley-migration** app with fork-state-hash, there is no requirement for the fork state block to be canonical. The tool automatically converts all pending blocks in the subchain, including the fork block, to canonical blocks. +::: #### Phase 2: Replayer in migration mode run