From ad4e40e08be2ad7285144aa685f9b2d7c28e4fad Mon Sep 17 00:00:00 2001 From: Xiliang Chen Date: Fri, 28 Jul 2023 13:55:30 +1200 Subject: [PATCH] Update text/0014-improve-locking-mechanism-for-parachains.md Co-authored-by: asynchronous rob --- text/0014-improve-locking-mechanism-for-parachains.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/0014-improve-locking-mechanism-for-parachains.md b/text/0014-improve-locking-mechanism-for-parachains.md index c319452..1fb85ff 100644 --- a/text/0014-improve-locking-mechanism-for-parachains.md +++ b/text/0014-improve-locking-mechanism-for-parachains.md @@ -8,7 +8,7 @@ ## Summary -The manager of a parachain have the permission to manage the parachain when the parachain is unlocked. Parachain is by default locked when onboarded on a slot. This requires the parachain wasm/genesis must be valid otherwise a root track governance action on relaychain is required to update the parachain. +The manager of a parachain has permission to manage the parachain when the parachain is unlocked. Parachains are by default locked when onboarded to a slot. This requires the parachain wasm/genesis must be valid, otherwise a root track governance action on relaychain is required to update the parachain. This RFC proposes a mechanism to allow a parachain manager to self-service the parachain without root track governance action.