Fix inconsistent naming in RFCs and update the status of some RFCs
This PR unifies the naming conventions across multiple RFCs, ensuring consistency in RFCs. Additionally, it updates the status of several RFCs to reflect their latest status.
In older documents or other sources, some references still use outdated naming conventions. Can we provide a mapping table, such as:
Edition CKB2023 → CKB Edition Meepo (on 2024/??)
In older documents or other sources, some references still use outdated naming conventions. Can we provide a mapping table, such as:
Edition CKB2023 → CKB Edition Meepo (on 2024/??)
https://github.com/nervosnetwork/rfcs/blob/5a0e339bcbd88f6ca283cd57a13b1c808503313f/rfcs/0053-ckb-hardfork/0053-ckb-hardfork.md#historical-editions @XuJiandong
Just being curious: why do we name it as CKB Edition Meepo, I feel that CKB Meepo Edition is more like proper English grammar