From a972a5460422d7d901445c00eba44c10ce3586c7 Mon Sep 17 00:00:00 2001 From: blimpa <72349134+blimpa@users.noreply.github.com> Date: Thu, 2 May 2024 17:00:26 -0300 Subject: [PATCH] Update mip16.md Testing possible rendering issue --- MIP16/mip16.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/MIP16/mip16.md b/MIP16/mip16.md index a1d272bad..5e8cefeb3 100644 --- a/MIP16/mip16.md +++ b/MIP16/mip16.md @@ -74,12 +74,12 @@ It is important to note that due to the frequency of such changes, the Weekly Cy #### Overview of the Weekly Governance Cycle -The weekdays displayed in the image are recommended but may vary based on the decisions made by the Governance Facilitators and the Governance Security Engineering team, with the exception of the days designated for the weekly poll. - | ![image](https://github.com/makerdao/mips/blob/master/MIP16/weekly_governance_cycle.png)) | |--| | Weekly Governance Cycle | +_The weekdays displayed in the image are recommended but may vary based on the decisions made by the Governance Facilitators and the Governance Security Engineering team, with the exception of the days designated for the weekly poll._ + **Important Notes:** - As the Weekly Governance Cycle runs from Monday until the following Wednesday, there will in effect be two concurrent Weekly Governance Cycles from Monday to Wednesday each week. @@ -95,4 +95,4 @@ With the acceptance of this MIP, non-emergency governance of the Maker Protocol In addition, the use of the Weekly Cycle as defined in this MIP should only occur where there is a specific need to use the Weekly Cycle as opposed to the Monthly Cycle. Consensus among the Governance Facilitators is required in order to make use of the Weekly Cycle as opposed to the Monthly Cycle. -Emergency governance actions are explicitly allowed outside of MIP-defined governance processes due to the time-sensitive nature of emergency responses and the permissionless nature of on-chain proposals and voting. \ No newline at end of file +Emergency governance actions are explicitly allowed outside of MIP-defined governance processes due to the time-sensitive nature of emergency responses and the permissionless nature of on-chain proposals and voting.