diff --git a/fep/a4ed/fep-a4ed.md b/fep/a4ed/fep-a4ed.md
index 80243e5..08b3a7c 100644
--- a/fep/a4ed/fep-a4ed.md
+++ b/fep/a4ed/fep-a4ed.md
@@ -125,10 +125,14 @@ A list of editors is maintained in the `EDITORS.md` file at the root of the FEP
 
 A list of methods in which a proposal may be submitted is maintained in the `SUBMISSION.md` file at the root of the FEP repository.
 
-### FEP-a4ed
+### FEP Process Governance
 
 FEP-a4ed (The Fediverse Enhancement Proposal Process) is a living document and can be updated despite having the `FINAL` status.
 
+Anyone can propose a change to FEP-a4ed (or other documents related to the FEP process) using any method listed in `SUBMISSION.md` file. The change must be approved by at least two editors (one of them could be the submitter). For any part of the FEP process, there must be a sufficient number of editors who agreed to do the maintenance work. Changes should not be accepted before at least 1 month passes after the last update, to give editors and the community time to review them and provide feedback.
+
+Minor changes (i.e. a correction of a typo or of a broken link) can be accepted immediately after getting two approvals from editors.
+
 ## History
 
 The process and format described in this proposal is influenced by other community driven documentation efforts such as the BitTorrent Enhancement Proposal Process [BEP-1], Scheme Request for Implementation [SRFI] and the IETF RFC Series [RFC-8729].