Linting fixes

Author: adamblanchard

contributing/meetings/2025 27th April.md

@@ -13,21 +13,21 @@ Mega thanks to Rachel for setting _so_ much good stuff in the new repo, linting,
 Also mega thanks to Natlia for putting together the proposal for splitting js/node - the biggest remaining puzzle piece in the curriculum.
 
 ### 2. Reflection
-#### Things that didn't work so well:
+#### Things that didn't work so well
 - Review requires on PRs to 1? Yes.
 - Bit unclear where to have discussions (some slack, pr, issue). Finding it is hard. Keep slack discussions linked/sumarised into PRs.
 - Tasks were quite broad at this point, difficult to estimate, hard to take a task because of this
 - Some felt like they couldn't contribute much recently. **Important note:** Being engaged, following conversations, replying with feedback, is all really helpful too and super appreciated, even if you're week is too busy to take a task on your own.
 
-#### Things working good:
+#### Things working good
 - Monorepo is going well! consistency across content, finding everything in one place.
 - Biweekly/weekly catch up sessions work well, both online and offline makes a nice balance. Summary of notes afterwards, with clear goals/next steps for the next "two weeks" is good.
 - Github kanban board for managing issues, priority, visibility etc. is nice
 
-#### Other things to note:
+#### Other things to note
 - Feel free to work on this project at HYF on Sundays, if you'd like to meet up. If you want a meeting room at any point, get in touch with Saloumeh a couple of days in advance.
 
-#### Actions:
+#### Actions
 1. Switch to one required reviewer (update contributing readme, share in slack. note that more reviewers should often be requested when necessray (give examples) it's just not enforced in github). Reminder that all staff can merge stuff, if it's fully approved, ping anyone if something is blocked.
 2. Keep meeting agendas/notes in github, link to them from other places (invites, slack reminders).
 3. Continue to consider how to best keep conversations in the right/organised places, it feels disjointed right now.
@@ -41,10 +41,10 @@ Also mega thanks to Natlia for putting together the proposal for splitting js/no
 3. Start splitting tasks up already...
 
 **Next steps:**
-* Our plan should be to start getting content into the courses, small PRs, and easily to iterate later.
-* So, create course outlines in the readmes, link to legacy content, make notes of new stuff to be added as stubs, etc.
-* Create tickets for additional changes (e.g. final projects, or smaller stuff like "change exercises in module x)
-* **Note: Legacy modules should not be modified.** Linking is fine for now, but we need to copy them over at some point, and if/when we want to modify the content, it's a good time to do that!
+- Our plan should be to start getting content into the courses, small PRs, and easily to iterate later.
+- So, create course outlines in the readmes, link to legacy content, make notes of new stuff to be added as stubs, etc.
+- Create tickets for additional changes (e.g. final projects, or smaller stuff like "change exercises in module x)
+- **Note: Legacy modules should not be modified.** Linking is fine for now, but we need to copy them over at some point, and if/when we want to modify the content, it's a good time to do that!
 
 ## Goals for next time (2 weeks)
 1. Foundation learning goal outline (according to the "next steps" just above)