From bd26ec6e09bd12107403db07410d1da9503dcaca Mon Sep 17 00:00:00 2001 From: bernd-m <43466467+bermuell@users.noreply.github.com> Date: Tue, 13 Aug 2024 17:07:07 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: insumity --- UPGRADING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/UPGRADING.md b/UPGRADING.md index a8d0ff1bcc..a3f2d5e84d 100644 --- a/UPGRADING.md +++ b/UPGRADING.md @@ -29,13 +29,13 @@ func InitializeMaxProviderConsensusParam(ctx sdk.Context, providerKeeper provide ### Governance Proposals -Legacy proposals are not supported anymore by the current version of the provider. Legacy proposals which are still active (voting period or deposit period) and contains one of the following messages need to be migrated as described below: +Legacy proposals are not supported anymore by the current version of the provider. Legacy proposals which are still active (voting period or deposit period) and contain one of the following messages that need to be migrated as described below: - `ConsumerAdditionProposal` needs to be converted to `MsgConsumerAddition` - `ConsumerModificationProposal` needs to be converted to `MsgConsumerModification` - `ConsumerRemovalProposal` needs to be converted to `MsgConsumerRemoval` - `ChangeRewardDenomsProposal` needs to be converted to `MsgChangeRewardDenoms` -The following shows an example how to migrate a proposal containing a legacy consumer addition proposal message. +The following shows an example on how to migrate a proposal containing a legacy consumer addition proposal message. Migration for the other messages aobve follows the same pattern. The resulting migration code has to be added to the upgrade handler of the provider chain. #### Migrate Legacy Proposal Content