diff --git a/rfcs/0043-rfcsc-rotation.md b/rfcs/0043-rfcsc-rotation.md
index 52efa9310..36229f2d8 100644
--- a/rfcs/0043-rfcsc-rotation.md
+++ b/rfcs/0043-rfcsc-rotation.md
@@ -11,7 +11,8 @@ related-issues: 36
 Each RFC Steering Committee (RFCSC) unanimously elects the succeeding one at
 their first meeting in December from an open list of nominees.
 
-# Motivation [motivation]: #motivation
+# Motivation
+[motivation]: #motivation
 
 With the implementation of [RFC
 36](https://github.com/NixOS/rfcs/blob/master/rfcs/0036-rfc-process-team-amendment.md)
@@ -23,16 +24,18 @@ mandate for life, allowing a healthy rotation of members, and offering several
 procedures to always keep the Steering Committee capable of making decisions
 such that the RFC process can keep running smoothly at all times.
 
-# Detailed design [design]: #detailed-design
+# Detailed design
+[design]: #detailed-design
 
 The RFC Steering Committee shall always have five members. If membership drops
 below five members (for example by abdication of a member as detailed below), a
 new member shall directly be elected after a nomination period of at least two
-weeks (see below for nomination and selection process). If number of members of
-the RFCSC drops below 4 people it cannot proceed with shepherd team selections
-until new members have been selected.
+weeks (see below for nomination and selection process). If the number of
+members of the RFCSC drops below 4 people, it cannot proceed with shepherd team
+selections until new members have been selected.
 
-## Ending membership A member can end their membership in the Steering
+## Ending membership
+A member can end their membership in the Steering
 Committee by either of the following three mechanisms, ordered from most
 frequent to least:
 
@@ -46,7 +49,8 @@ A member can abdicate from the RFC Steering Committee at any time and for any
 reason. A member planning to abdicate should inform the rest of the RFC
 Steering Committee of their intention at their earliest convenience.
 
-## Becoming a member The members chosen through the original implementation as
+## Becoming a member
+The members chosen through the original implementation as
 specified in RFC 36 are regular members as specified in this RFC. They will
 stay on as members until replaced by new members as outlined below.
 
@@ -69,23 +73,27 @@ Additionally to RFC 36 a new restriction formally comes into effect. In order
 to avoid conflict of interest there is an upper cap of 2 members working for a
 single employer.
 
-# Drawbacks [drawbacks]: #drawbacks
+# Drawbacks
+[drawbacks]: #drawbacks
 
 The RFCSC basically elects their own successors, but this minimises the
 complexity of having to hold elections, including defining who is eligible to
 vote and how to hold them.
 
-# Alternatives [alternatives]: #alternatives
+# Alternatives
+[alternatives]: #alternatives
 
 Do nothing: then the current members of the RFC Steering Committee as defined
 in RFC 36 could stay on the Committee indefinitely or at least until that part
 of RFC 36 is overridden by a newly accepted RFC.
 
-# Unresolved questions [unresolved]: #unresolved-questions
+# Unresolved questions
+[unresolved]: #unresolved-questions
 
 As of now, none.
 
-# Future work [future]: #future-work
+# Future work
+[future]: #future-work
 
 As this process is to be implemented over a fairly long time frame (a year for
 each iteration), this framework might have to be revised at a later date,