chore: More linting

@nicholasdower is smarter than me. What's missing was the
`listItemIndent` setting

markdown/dev/guides/plugins/conditionally-loading-build-time-plugins/en.md

@@ -51,10 +51,10 @@ const Pattern = new freesewing.Design(
 
 Our condition method will return `true` only if the following conditions are met:
 
--   A `settings` object is passed into the method
--   `settings.options` is _truthy_
--   `settings.options.draftForHighBust` is _truthy_
--   `settings.options.measurements.highBust` is _truthy_
+- A `settings` object is passed into the method
+- `settings.options` is _truthy_
+- `settings.options.draftForHighBust` is _truthy_
+- `settings.options.measurements.highBust` is _truthy_
 
 This is a real-world example from our Teagan pattern. A t-shirt pattern that can be
 drafted to the high bust (rather than the full chest circumference) if the user

markdown/dev/guides/plugins/hooks/en.md

@@ -5,16 +5,16 @@ order: 60
 
 A **hook** is a lifecycle event. The available hooks are:
 
--   [preRender](/reference/hooks/prerender/): Called at the start of [`Pattern.render()`](/reference/api/pattern#render)
--   [postRender](/reference/hooks/postrender/): Called at the end of [`Pattern.render()`](/reference/api/pattern#render)
--   [insertText](/reference/hooks/inserttext/): Called when inserting text
--   [preDraft](/reference/hooks/predraft/): Called at the start of [`Pattern.draft()`](/reference/api/pattern#draft)
--   [postDraft](/reference/hooks/postdraft/): Called at the end of [`Pattern.draft()`](/reference/api/pattern#draft)
--   [preSample](/reference/hooks/presample/): Called at the start of [`Pattern.sample()`](/reference/api/pattern#sample)
--   [postSample](/reference/hooks/postsample/): Called at the end of [`Pattern.sample()`](/reference/api/pattern#sample)
+- [preRender](/reference/hooks/prerender/): Called at the start of [`Pattern.render()`](/reference/api/pattern#render)
+- [postRender](/reference/hooks/postrender/): Called at the end of [`Pattern.render()`](/reference/api/pattern#render)
+- [insertText](/reference/hooks/inserttext/): Called when inserting text
+- [preDraft](/reference/hooks/predraft/): Called at the start of [`Pattern.draft()`](/reference/api/pattern#draft)
+- [postDraft](/reference/hooks/postdraft/): Called at the end of [`Pattern.draft()`](/reference/api/pattern#draft)
+- [preSample](/reference/hooks/presample/): Called at the start of [`Pattern.sample()`](/reference/api/pattern#sample)
+- [postSample](/reference/hooks/postsample/): Called at the end of [`Pattern.sample()`](/reference/api/pattern#sample)
 
 You can register a method for a hook. When the hook is triggered, your method will be
 called. It will receive two parameters:
 
--   An object relevant to the hook. See the [hooks API reference](/reference/hooks/) for details.
--   Data passed when the hook was registered (optional)
+- An object relevant to the hook. See the [hooks API reference](/reference/hooks/) for details.
+- Data passed when the hook was registered (optional)

markdown/dev/guides/plugins/macros/en.md

@@ -5,8 +5,8 @@ order: 90
 
 Plugin structure for macros is similar, with a few changes:
 
--   Rather than the hook name, you provide the macro name (that you choose yourself)
--   The context (`this`) of a macro method is **always** a [Part](/reference/api/part) object.
+- Rather than the hook name, you provide the macro name (that you choose yourself)
+- The context (`this`) of a macro method is **always** a [Part](/reference/api/part) object.
 
 Apart from these, the structure is very similar:
 

markdown/dev/guides/plugins/plugin-structure/en.md

@@ -5,8 +5,8 @@ order: 50
 
 Plugins can do two things:
 
--   They can use hooks
--   They can provide macros
+- They can use hooks
+- They can provide macros
 
 Your plugin should export an object with the following structure:
 

markdown/dev/guides/plugins/types-of-plugins/en.md

@@ -5,8 +5,8 @@ order: 10
 
 Plugins come in two flavours:
 
--   [Build-time plugins](#build-time-plugins)
--   [Run-time plugins](#run-time-plugins)
+- [Build-time plugins](#build-time-plugins)
+- [Run-time plugins](#run-time-plugins)
 
 When writing a plugin, ask yourself whether it's a run-time or a build-time plugin.
 And if the answer is both, please split them into two plugins.

markdown/dev/guides/plugins/using-hooks/en.md

@@ -9,8 +9,8 @@ that as the second object.
 
 Remember that:
 
--   The `insertText` hook will receive a locale and string and you should return a string.
--   All other hooks receive an object. You don't need to return anything, but rather modify the object you receive.
+- The `insertText` hook will receive a locale and string and you should return a string.
+- All other hooks receive an object. You don't need to return anything, but rather modify the object you receive.
 
 Let's look at an example:
 
@@ -39,8 +39,8 @@ export default {
 
 This is a complete plugin, ready to be published on NPM. It uses two hooks:
 
--   `preRender` : We add some style and defs to our SVG
--   `insertText` : We transfer all text to UPPERCASE
+- `preRender` : We add some style and defs to our SVG
+- `insertText` : We transfer all text to UPPERCASE
 
 <Note>