## Scopes and Atlas Regex Regular expression: - (\d+(?:\.\d+){2,}): - $1\n\n ## Notes on Improvement ### General - Indenting should be improved to extend to everything below a given header up until the next higher-level header comes along - We should use Oxford commas: "x, y, and z" - Replace numbers < 10 with their alphabetic form: "six, eight, nine, 10". (Excluding articles, amounts of money, etc) - Capitalize ALL words on titles / subtitles? - Only when titles are not self-standing sentences, probably. So, if "Facilitators should not neglect their duties or whatever because I say so", I'd say no - However, it'd be even better to turn these titles into non-sentences, e.g., "Facilitator Duties" - In fact, my general suggestion would be to come up with new non-sentence titles to replace sentence titles, and have the sentence titles be part of the content of the relevant article - I don't like the agency that is bestowed upon Scopes, e.g., "can become recognized as Active AVCs by the Governance Scope". Scopes are defined as broad areas of work; they cannot "recognize" anything in any obvious sense - It's not clear where we are using acronyms and where we are not - References to other articles in bold? or only active elements *10.1.1* - First articles like ## 1: XX , ## 2: XX could be replaced by ## 1. XX, ## 2. XX - In cases like this: ![](https://hackmd.io/_uploads/SJ6StZzKh.png) - The subelements like "2.7.4.1.2.1" should look smaller - Probably get rid of horizontal rules - Rules around when to write the acronyms - Some documents still refer to the previous Endgame MIP Set (Physical Resilience, etc). We need to update those - MIP106, 10.5.1.1: Language: "The Policyholder Definition" > "Policyholder Definition" - Rune doesn't like hyphens. We need to fill out those omissions ("long term", etc) - MIP113, 5.2.4.7.1A: The header for each AVC is a link to the forum. That's all fine and dandy, but there's no indication where these links are linking to --- they're just clickable names. We should probably make it explicit that those are links to the inaugural forum posts for the AVCs ### Atlas - Aligned Conservers are never "ACs". Not sure why this is - 2.4.2 - "Alignment Conservers Eligibility Requirements" > "Alignment Conservers[:?] Duties [Obligations?]" - 2.5.2.1.1 - "on the Hawk, Dove, Balanced spectrum" > "on the Hawk/Dove spectrum" - 2.5.3.1 - Language: "an Alignment Conserver must *verify* as an unaffiliated Alignment Voter Committee Member" - 2.5.5.1 - More readable as a table, I think - 2.5.6 - "With this risk" is clumsy referent-wise - 2.5.10.1.1 - Not sure why this (and .2 and .3) is an article. They would probably be better as list items - 2.6.3.1 - Language: "... PD slots and the number of RD slots. There is always an *equivalent* amount of both" - 2.7.4.1.1 (and therearound) - "x tokens *is* distributed". This error recurs - 2.7.6.2.2.0 - Language: "To prevent the damage possible for malicious or negligent abuse of the derecognition powers" - ![](https://hackmd.io/_uploads/S18JFYY_2.png) - 3.3.5 - "best practice" > "best practices" ### MIP106 - 1.1.2.3 - Remove the last sentence. Same information constitutes article 1.1.2.5 - 3: DAO Toolkit Core Development - This has same title as 3.1 - Should it be: "DAO Toolkit" - 4: Governance Artificial Intelligence Tools (GAIT) - All subtitles (4.1, 4.1.1) have Governance Artificial Intelligence Tools (GAIT) + other words. - Write only GAIT - 4.0 --> switch to ## 4.1 and edit subsequent numbers. - 5.1: General Guidelines on Milestones and Results Reporting of Projects Funded by the Maker Protocol - title too long - change for "Milestones and Results Reporting Guidelines" - 10.1.1: The Resilience Fund - "[...]The conditions of use are defined in “Resilience Claims Process” (10.4)." - replace by "[...]The conditions of use are defined in article 10.4: Resilience Claims Process." - 10.1: Physical Resilience Facilitator - named a few times - 10.3.1 - It seems adecuate to turn all subelements in a list (10.3.1.1/2/3) - Same with 10.3.2, 10.4.1 - 10.3.3 - Lawyer Registry is abbreviated to LR. The acronym shouldn't be used OR it should be introduced somewhere as "Lawyer Registry (LR)". ### MIP107 - 2.1 look numeration ### MIP108 - 8.1.1.1, etc --> better as list