fix(dev): One-liner admonitions

sites/dev/docs/howtos/design/cutlist/readme.mdx

@@ -1,12 +1,20 @@
 ---
-title: "Include Cutting Instructions"
+title: 'Include Cutting Instructions'
 ---
 
 To include cutting instructions with your part, use the [annotations plugin](/reference/plugins/annotations) (included by default via [core-plugins](/reference/plugins/core)) to add the `cutlist.addCut` method to your part's [`store`](/reference/api/store/extend).
 
-:::tipThe [grainline macro](/reference/macros/grainline) and the [cutonfold macro](/reference/macros/cutonfold) will automatically add grain and fold information to the cutting instructions :::
+:::tip
+The [grainline macro](/reference/macros/grainline) and the [cutonfold
+macro](/reference/macros/cutonfold) will automatically add grain and fold
+information to the cutting instructions
+:::
 
-:::tipThese cutting instructions get used by the [title macro](/reference/macros/title), so be sure to add them before adding your part's title. :::
+:::tip
+These cutting instructions get used by the [title
+macro](/reference/macros/title), so be sure to add them before adding your
+part's title.
+:::
 
 :::note
 <details>
@@ -15,18 +23,17 @@ To include cutting instructions with your part, use the [annotations plugin](/re
 Pass an object to the `store.cutlist.addCut` method with any of the following keys; any you don't provide will be filled with the defaults:
 
 | Key          | Type          | Default  | Description                                                                                                                        |
-| :-- | :--- | :------ | :---------- |
+| :----------- | :------------ | :------- | :--------------------------------------------------------------------------------------------------------------------------------- |
 | cut          | Number\|false | 2        | the number of pieces to cut from the specified material. Pass `false` to clear all cutting instructions for the material           |
 | material     | String        | 'fabric' | the translation key of the material to cut from                                                                                    |
 | identical    | Boolean       | false    | should even numbers of pieces be cut in the same direction? false for mirrored                                                     |
 | bias         | Boolean       | false    | should the pieces in these cutting instructions be cut on the bias? 'false' uses grainline instruction or leaves orientation as is |
 | ignoreOnFold | Boolean       | false    | should these cutting instructions ignore any cutOnFold information set by the part                                                 |
 
-
 You can use any `string` you want for your material, but here are some standard ones we have translation for
 
 | Key         | Translation                 |
-|:--|:--|
+| :---------- | :-------------------------- |
 | fabric      | Main Fabric                 |
 | lining      | Lining                      |
 | canvas      | Canvas                      |
@@ -39,8 +46,8 @@ You can use any `string` you want for your material, but here are some standard
 </details>
 :::
 
-
 ## Basic Usage
+
 For simple cutting instructions, you can rely on the default method parameters
 
 ```js
@@ -49,11 +56,12 @@ const part = {
   draft: ({ part, store }) => {
     // add instructions to cut two mirrored from main fabric
     store.cutlist.addCut()
-	}
+  },
 }
 ```
 
 ## Intermediate Usage
+
 For many designs, you'll want more than just "Cut 2 mirrored from Main Fabric"
 
 ### Specifying materials, number of pieces, orientation
@@ -66,11 +74,12 @@ const part = {
   draft: ({ part, store }) => {
     // add instructions to cut three identical from lining
     store.cutlist.addCut({ cut: 3, material: 'lining', identical: true })
-	}
+  },
 }
 ```
 
 ### Instructions for multiple materials
+
 You can add as many sets of instructions as you need
 
 ```js
@@ -81,13 +90,14 @@ const part = {
     store.cutlist.addCut({ cut: 4 })
     // add instructions to cut three identical from lining
     store.cutlist.addCut({ cut: 3, material: 'lining', identical: true })
-	}
+  },
 }
 ```
 
 ## Advanced usage
 
 ### Cut some on the fold, some not
+
 Sometimes you want some pieces cut on the fold and others cut as halves to seam together.
 
 ```js
@@ -105,12 +115,12 @@ const part = {
     store.cutlist.addCut()
     // cut two, not on the fold
     store.cutlist.addCut({ cut: 2, ignoreOnFold: true })
-	}
+  },
 }
 ```
 
-
 ### Cut some on the grain, some on the bias
+
 You set the grainline on a piece, but you also need some to be cut on the bias
 
 ```js
@@ -128,6 +138,6 @@ const part = {
     store.cutlist.addCut()
     // cut two mirrored on the bias
     store.cutlist.addCut({ cut: 2, bias: true })
-	}
+  },
 }
 ```

sites/dev/docs/reference/api/design/readme.mdx

@@ -37,7 +37,9 @@ const Sorcha = new Design({
 })
 ```
 
-:::tipA Design in FreeSewing is little more than a container for various Parts:::
+:::tip
+A Design in FreeSewing is little more than a container for various Parts
+:::
 
 Optionally, you can also pass it a `data` attribute
 to hold any custom data you'd like to add to your Design.
@@ -51,14 +53,13 @@ const Sorcha = new Design({
   data: {
     version: 3,
     price: 12,
-    currency: 'euro'
+    currency: 'euro',
-  }
+  },
 })
 ```
 
 ## Notes
 
-
 The Design constructor is a _super-constructor_.
 It will return a constructor method that will a pattern based on your design.
 
@@ -74,4 +75,3 @@ This holds the design configuration as passed to the Design constructor.
 ### Design.patternConfig
 
 Holds the resolved pattern configuration based on the configuration passed to the Design constructor.
-

sites/dev/docs/reference/api/part/config/hide/readme.mdx

@@ -4,8 +4,13 @@ title: Hiding parts
 
 The `hide` option of a part's configuration controls how to hide it and/or its dependencies.
 
-:::tipA hidden part will not be included in the output when it's rendered:::
+:::tip
-:::tipThe `hide` configuration from parts that you include in your design will always override configuration from inherited parts.:::
+A hidden part will not be included in the output when it's rendered
+:::
+
+:::tip
+The `hide` configuration from parts that you include in your design will always override configuration from inherited parts.
+:::
 
 ## Settings
 
@@ -21,11 +26,10 @@ const part = {
   after: [exampleBase],
   // hide `exampleBase`
   hide: { after: true },
-  draft: ({ part }) => part
+  draft: ({ part }) => part,
 }
 ```
 
-
 ### hide.always
 
 To hide a specific part that would otherwise not be hidden by other configuration, add its name to the `hide.always` array
@@ -38,7 +42,7 @@ const part = {
   after: [exampleBase, exampleBack],
   // hide `exampleBack`
   hide: { always: ['example.back'] },
-  draft: ({ part }) => part
+  draft: ({ part }) => part,
 }
 ```
 
@@ -54,15 +58,22 @@ const part = {
   from: exampleBase,
   // hide exampleBase
   hide: { from: true },
-  draft: ({ part }) => part
+  draft: ({ part }) => part,
 }
 ```
 
 ### hide.inherited
 
-To hide parts that you have not explicitly included in this part that may be pulled in by the explicitly included `from` and `after` parts, set `hide.inherited` to a truthy value.
+To hide parts that you have not explicitly included in this part that may be
+pulled in by the explicitly included `from` and `after` parts, set
+`hide.inherited` to a truthy value.
 
-:::noteThis setting will hide any part included as `from` or `after` by your explicitly included `from` part or its dependency chain. It will also hide any part included as `from` by your explicitly included `after` part or its dependency chain. It will not hide the `after` parts of `after` parts:::
+:::note
+This setting will hide any part included as `from` or `after` by your
+explicitly included `from` part or its dependency chain. It will also hide any
+part included as `from` by your explicitly included `after` part or its
+dependency chain. It will not hide the `after` parts of `after` parts
+:::
 
 ```js
 // the "after" chain
@@ -109,30 +120,32 @@ const mainBack = {
 }
 
 ```
+
 :::tip
+
 <details>
   <summary>Need more clarity?</summary>
 
-  In the above example, the dependency tree for the part `example.mainBack` resolves to the following, with `from` dependencies in **bold** and `after` dependencies *italicized*.
+In the above example, the dependency tree for the part `example.mainBack` resolves to the following, with `from` dependencies in **bold** and `after` dependencies _italicized_.
-
 
 | Part                          | Dependency Type | Hidden |
-  | :---------- | :---------- | :-----|
+| :---------------------------- | :-------------- | :----- |
 | example.mainBack              | root            | false  |
 | - **other.parent**            | from            | false  |
 | - - **other.grandParent**     | inherited from  | true   |
-  | - - - *other.grandParentBase*   | inherited after  | true   |
+| - - - _other.grandParentBase_ | inherited after | true   |
-  | - *example.mainFront*         | after            | false  |
+| - _example.mainFront_         | after           | false  |
-  | - - *example.mainFrontBase*    | after            | false  |
+| - - _example.mainFrontBase_   | after           | false  |
 | - - **other.mainFront**       | inherited from  | true   |
 
 Dependencies are considered inherited if they have two or more dashes (-) next to them, and are either **bold** themselves, or underneath a **bold** part.
+
 </details>
 :::
 
 ### hide.never
 
-To __not__ hide a specific part that would otherwise be hidden by other configuration, add its name to the `hide.never` array
+To **not** hide a specific part that would otherwise be hidden by other configuration, add its name to the `hide.never` array
 
 ```js
 import { exampleBase } from './base.mjs'
@@ -144,9 +157,9 @@ const part = {
     // hide exampleBase and exampleBack
     after: true,
     // override hiding exampleBack so that it is shown
-    never: ['example.back']
+    never: ['example.back'],
   },
-  draft: ({ part }) => part
+  draft: ({ part }) => part,
 }
 ```
 
@@ -159,17 +172,30 @@ const part = {
   name: 'example.front',
   // hide `example.front`
   hide: { self: true },
-  draft: (({ part }) => part)
+  draft: ({ part }) => part,
 }
 ```
 
 ## Presets
-We provide two presets for common hiding configurations. For convenience, you can pass a preset to the `hide` configuration as a string like `hide: <preset name>`, or you can use `import { hidePresets } from '@freesewing.core` and pass `hide: hidePresets.<preset name>`
 
-:::tip If you don't like to remember strings and you're working in development a environment that has code completion, importing the presets from `@freesewing/core` will help you be sure you're definitely using an available preset :::
+We provide two presets for common hiding configurations. For convenience, you
+can pass a preset to the `hide` configuration as a string like `hide: <preset
+name>`, or you can use `import { hidePresets } from '@freesewing.core` and pass
+`hide: hidePresets.<preset name>`
+
+:::tip
+If you don't like to remember strings and you're working in development a
+environment that has code completion, importing the presets from
+`@freesewing/core` will help you be sure you're definitely using an available
+preset
+:::
 
 ### HIDE_ALL
-For a shortcut to setting all `boolean` hiding options ([`after`](#hideafter), [`from`](#hidefrom), [`inherited`](#hideinherited), and [`self`](#hideself)) to true, use  `HIDE_ALL`
+
+For a shortcut to setting all `boolean` hiding options ([`after`](#hideafter),
+[`from`](#hidefrom), [`inherited`](#hideinherited), and [`self`](#hideself)) to
+true, use `HIDE_ALL`
+
 :::note
 This is equivalent to using
 
@@ -181,9 +207,11 @@ This is equivalent to using
   inherited: true
 }
 ```
+
 :::
 
 To use it as an imported preset:
+
 ```js
 import { hidePresets } from '@freesewing/core'
 import { exampleBase } from './base.mjs'
@@ -200,8 +228,8 @@ const part = {
 }
 ```
 
-
 To use it as a string
+
 ```js
 import { exampleBase } from './base.mjs'
 import { exampleBack } from './back.mjs'
@@ -213,11 +241,12 @@ const part = {
   // hide `example.front`, `exmpleBase`, and `exampleBack`
   // as well as any inherited parts
   hide: 'HIDE_ALL',
-  draft: ({ part }) => part
+  draft: ({ part }) => part,
 }
 ```
 
 ### HIDE_TREE
+
 For a shortcut to setting [`from: true`](#hidefrom) and [`inherited: true`](#hideinherited), use `HIDE_TREE`
 
 :::note
@@ -228,13 +257,16 @@ This is equivalent to using
   from: true,
   inherited: true
 }
-````
+```
+
 :::
+
 :::note RELATED
 See [`hide.inherited`](#hideinherited) for a full explanation of how that option works
 :::
 
 To use it as an imported preset:
+
 ```js
 import { hidePresets } from '@freesewing/core'
 import { exampleBase } from './base.mjs'
@@ -245,12 +277,12 @@ const part = {
   from: exampleBase,
   // hide `exmpleBase`, and all inherited parts
   hide: hidePresets.HIDE_TREE,
-  draft: ({ part }) => part
+  draft: ({ part }) => part,
 }
 ```
 
-
 To use it as a string
+
 ```js
 import { exampleBase } from './base.mjs'
 import { exampleBack } from './back.mjs'
@@ -260,6 +292,6 @@ const part = {
   from: exampleBase,
   // hide `exmpleBase`, and all inherited parts
   hide: 'HIDE_TREE',
-  draft: ({ part }) => part
+  draft: ({ part }) => part,
 }
 ```

sites/dev/docs/reference/api/part/config/measurements/readme.mdx

@@ -6,7 +6,9 @@ The `measurements` and `optionalMeasurements` properties on the
 part configuration object list the part's required and optional
 measurements respectively.
 
-:::tipYou should only include what's required by the part itself, not its dependencies:::
+:::tip
+You should only include what's required by the part itself, not its dependencies
+:::
 
 ## measurements
 
@@ -17,7 +19,7 @@ that are required to draft the current part.
 const part = {
   name: 'example.front',
   measurements: ['head', 'chest'],
-  draft: ({ part }) => part
+  draft: ({ part }) => part,
 }
 ```
 
@@ -34,6 +36,6 @@ const part = {
   plugins: [pluginBust],
   measurements: ['head', 'chest'],
   optionalMeasurements: ['highBust'],
-  draft: ({ part }) => part
+  draft: ({ part }) => part,
 }
 ```

sites/dev/docs/reference/api/path/_curve/readme.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Path._curve()"
+title: 'Path._curve()'
 ---
 
 The `Path._curve()` method draws a cubic Bézier curve
@@ -13,7 +13,9 @@ so you do not need to provide it.
 Path path._curve(Point cp2, Point to)
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -27,13 +29,14 @@ Path path._curve(Point cp2, Point to)
 
 paths.line = new Path()
 .move(points.from)
-    ._curve(points.cp2, points.to)
+.\_curve(points.cp2, points.to)
-    .setText("Path._curve()", "text-sm center fill-note")
+.setText("Path.\_curve()", "text-sm center fill-note")
 .attr("data-text-dy", -1)
 
 return part
 }
-```
+
+````
 </Example>
 
 
@@ -45,4 +48,4 @@ as the two following calls yield the same result:
 ```js
 path.curve(point1, point1, point2)
 path._curve(point1, point2)
-```
+````

sites/dev/docs/reference/api/path/addclass/readme.mdx

@@ -10,7 +10,9 @@ The `Path.addClass()` method adds a CSS class to the path.
 Path path.addClass(string className)
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -28,7 +30,8 @@ Path path.addClass(string className)
 
 return part
 }
-```
+
+````
 </Example>
 
 ## Notes
@@ -39,4 +42,4 @@ as the two following calls yield the same result:
 ```js
 path.attr('class', 'fabric')
 path.addClass('fabric')
-```
+````

sites/dev/docs/reference/api/path/addtext/readme.mdx

@@ -12,7 +12,9 @@ Path path.addText(string text, string className = '')
 
 The second argument will optionally be used to set the CSS class for the text.
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -29,7 +31,8 @@ The second argument will optionally be used to set the CSS class for the text.
 
 return part
 }
-```
+
+````
 </Example>
 
 ## Notes
@@ -40,7 +43,7 @@ as the two following calls yield the same result:
 ```js
 path.attr('data-text', 'Hello')
 path.addText('Hello')
-```
+````
 
 The difference with [Path.setText()](/reference/api/path/addtext) is that this
 method will add to the existing text whereas `Path.setText()` will overwrite

sites/dev/docs/reference/api/path/attr/readme.mdx

@@ -18,7 +18,9 @@ Path path.attr(
 )
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -39,6 +41,7 @@ Path path.attr(
 
 return part
 }
+
 ```
 </Example>
 
@@ -54,3 +57,4 @@ all call this method under the hood.
 
 See [Using Attributes](/howtos/code/attributes)
 for information about custom Attributes that can be used with Paths.
+```

sites/dev/docs/reference/api/path/circlesegment/readme.mdx

@@ -12,9 +12,11 @@ A negative angle results in a clockwise arc.
 :::tip
 The new endpoint of this path is the same point
 that
+
 ```js
 path.end().rotate(deg, origin)
 ```
+
 would return.
 :::
 
@@ -24,7 +26,9 @@ would return.
 Path path.circleSegment(deg, origin)
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -48,5 +52,7 @@ paths.helper = new Path()
 
 return part
 }
+
 ```
 </Example>
+```

sites/dev/docs/reference/api/path/close/readme.mdx

@@ -10,7 +10,9 @@ The `Path.close()` method closes a path by drawing a straight line from the curr
 Path path.close()
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -24,12 +26,14 @@ Path path.close()
 
 paths.line = new Path()
 .move(points.from)
-    ._curve(points.cp2, points.to)
+.\_curve(points.cp2, points.to)
 .close()
 .reverse() // To keep text from being upside-down
-    .setText('Path._close()', 'text-sm right fill-note')
+.setText('Path.\_close()', 'text-sm right fill-note')
 
 return part
 }
+
 ```
 </Example>
+```

sites/dev/docs/reference/api/path/curve/readme.mdx

@@ -11,7 +11,9 @@ via two control points to a given endpoint.
 Path path.curve(Point cp1, Point cp2, Point to)
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -31,5 +33,7 @@ Path path.curve(Point cp1, Point cp2, Point to)
 
 return part
 }
+
 ```
 </Example>
+```

sites/dev/docs/reference/api/path/curve_/readme.mdx

@@ -12,16 +12,16 @@ identical to the end point.
 Path path.curve_(Point cp1, Point to)
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
-
 <Example caption="Example of the Path.curve\_() method">
 
 ```js
-({ Point, points, Path, paths, part }) => {
+;({ Point, points, Path, paths, part }) => {
-
   points.from = new Point(10, 20)
   points.cp1 = new Point(40, 0)
   points.to = new Point(90, 20)
@@ -29,12 +29,13 @@ Path path.curve_(Point cp1, Point to)
   paths.line = new Path()
     .move(points.from)
     .curve_(points.cp1, points.to)
-    .setText("Path.curve_()", "text-sm center fill-note")
+    .setText('Path.curve_()', 'text-sm center fill-note')
-    .attr("data-text-dy", -1)
+    .attr('data-text-dy', -1)
 
   return part
 }
 ```
+
 </Example>
 
 ## Notes

sites/dev/docs/reference/api/path/end/readme.mdx

@@ -10,7 +10,9 @@ The `Path.end()` method returns the Point object at the end of the path.
 Point path.end()
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -33,5 +35,7 @@ Point path.end()
 
 return part
 }
+
 ```
 </Example>
+```

sites/dev/docs/reference/api/path/hide/readme.mdx

@@ -10,7 +10,9 @@ The `Path.hide()` hides the path so it does not appear in the output.
 Path path.hide()
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -28,5 +30,7 @@ Path path.hide()
 
 return part
 }
+
 ```
 </Example>
+```

sites/dev/docs/reference/api/path/insop/readme.mdx

@@ -11,8 +11,9 @@ operation](/reference/api/path/noop) with id `id`.
 Path path.insop(string id, Path path)
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
-
+This method is chainable as it returns the `Path` object
+:::
 
 <Example caption="Example of the Path.insop() method">
 ```js
@@ -42,9 +43,11 @@ Path path.insop(string id, Path path)
 
 return part
 }
+
 ```
 </Example>
 
 ## Notes
 
 This is often used to insert darts into a path.
+```

sites/dev/docs/reference/api/path/line/readme.mdx

@@ -11,7 +11,9 @@ given point.
 Path path.line(Point to)
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -29,5 +31,7 @@ Path path.line(Point to)
 
 return part
 }
+
 ```
 </Example>
+```

sites/dev/docs/reference/api/path/noop/readme.mdx

@@ -12,7 +12,9 @@ with [`Path.insop()`](/reference/api/path/insop).
 Path path.noop(string id)
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -44,5 +46,7 @@ Path path.noop(string id)
 
 return part
 }
+
 ```
 </Example>
+```

sites/dev/docs/reference/api/path/setclass/readme.mdx

@@ -10,7 +10,9 @@ The `Path.setClass()` method sets the CSS class(es) of the path.
 Path path.setClass(string className)
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -28,7 +30,8 @@ Path path.setClass(string className)
 
 return part
 }
-```
+
+````
 </Example>
 
 ## Notes
@@ -39,4 +42,4 @@ as the two following calls yield the same result:
 ```js
 path.attr('class', 'fabric', true)
 path.setClass('fabric')
-```
+````

sites/dev/docs/reference/api/path/sethidden/readme.mdx

@@ -11,7 +11,9 @@ value you pass it.
 Path path.setHidden(bool hidden = false)
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -29,5 +31,7 @@ Path path.setHidden(bool hidden = false)
 
 return part
 }
+
 ```
 </Example>
+```

sites/dev/docs/reference/api/path/settext/readme.mdx

@@ -12,7 +12,9 @@ Path path.setText(string text, string className = '')
 
 The second argument will optionally be used to set the CSS class for the text.
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -29,7 +31,8 @@ The second argument will optionally be used to set the CSS class for the text.
 
 return part
 }
-```
+
+````
 </Example>
 
 ## Notes
@@ -40,7 +43,7 @@ as the two following calls yield the same result:
 ```js
 path.attr('data-text', 'Hello')
 path.setText('Hello')
-```
+````
 
 The difference with [Path.addText()](/reference/api/path/addtext) is that this
 method will overwrite existing text on the path, whereas `Path.addText()` will

sites/dev/docs/reference/api/path/smurve/readme.mdx

@@ -11,7 +11,9 @@ A smooth curve means it will use the reflection of the end control point of the
 Path path.smurve(Point cp2, Point end)
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -36,5 +38,7 @@ Path path.smurve(Point cp2, Point end)
 
 return part
 }
+
 ```
 </Example>
+```

sites/dev/docs/reference/api/path/smurve_/readme.mdx

@@ -13,7 +13,9 @@ A smooth curve means it will use the reflection of the end control point of the
 Path path.smurve_(Point cp2, Point end)
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -31,11 +33,13 @@ Path path.smurve_(Point cp2, Point end)
 paths.smurve = new Path()
 .move(points.aFrom)
 .curve(points.aCp1, points.aCp2,points.aTo)
-    .smurve_(points.bTo)
+.smurve\_(points.bTo)
 .reverse() // Puts text at the end
 .setText('Path.smurve()')
 
 return part
 }
+
 ```
 </Example>
+```

sites/dev/docs/reference/api/path/start/readme.mdx

@@ -10,7 +10,9 @@ The `Path.start()` method returns the Point object at the start of the path.
 Point path.start()
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -33,5 +35,7 @@ Point path.start()
 
 return part
 }
+
 ```
 </Example>
+```

sites/dev/docs/reference/api/path/unhide/readme.mdx

@@ -12,7 +12,9 @@ hidden via `Path.hide()`.
 Path path.unhide()
 ```
 
-:::tipThis method is chainable as it returns the `Path` object:::
+:::tip
+This method is chainable as it returns the `Path` object
+:::
 
 ## Example
 
@@ -30,5 +32,7 @@ Path path.unhide()
 
 return part
 }
+
 ```
 </Example>
+```

sites/dev/docs/reference/api/pattern/addpart/readme.mdx

@@ -5,7 +5,9 @@ title: Pattern.addPart()
 The `Pattern.addPart()` method allows you to add a part to a pattern.
 It has the same effect as passing a part to the Design constructor.
 
-:::noteThis method is chainable as it returns the Pattern object:::
+:::note
+This method is chainable as it returns the Pattern object
+:::
 
 ## Pattern.addPart() signature
 
@@ -16,13 +18,12 @@ Pattern pattern.addPart(object part)
 ## Pattern.addPart() example
 
 ```js
-import { Aaron } from "@freesewing/aaron"
+import { Aaron } from '@freesewing/aaron'
 
 const extra = {
   name: 'aaron.extra',
   draft: ({ points, Point, paths, Path, part }) => {
-    points.msg = new Point(50,15)
+    points.msg = new Point(50, 15).attr('data-text', 'I am an extra part')
-      .attr('data-text', "I am an extra part")
     paths.box = new Path()
       .move(new Point(0, 0))
       .line(new Point(0, 30))
@@ -32,14 +33,12 @@ const extra = {
       .addClass('note')
 
     return part
-  }
+  },
 }
 
 // Load some public test measurements from the FreeSewing backend
 const measurements = (
-  await (
+  await (await fetch('https://backend3.freesewing.org/curated-sets/1.json')).json()
-    await fetch("https://backend3.freesewing.org/curated-sets/1.json")
-  ).json()
 ).measurements
 
 const pattern = new Aaron({ measurements }).addPart(extra)

sites/dev/docs/reference/api/pattern/draft/readme.mdx

@@ -7,7 +7,9 @@ making sure to do so in the right order, handle dependencies, resolve
 options to their absolute values and a number of other housekeeping things
 that are required for the pattern to be drafted.
 
-:::noteThis method is chainable as it returns the Pattern object:::
+:::note
+This method is chainable as it returns the Pattern object
+:::
 
 ## Pattern.draft() signature
 
@@ -18,13 +20,11 @@ Pattern pattern.draft()
 ## Pattern.draft() example
 
 ```js
-import { Aaron } from "@freesewing/aaron"
+import { Aaron } from '@freesewing/aaron'
 
 // Load some public test measurements from the FreeSewing backend
 const measurements = (
-  await (
+  await (await fetch('https://backend3.freesewing.org/curated-sets/1.json')).json()
-    await fetch("https://backend3.freesewing.org/curated-sets/1.json")
-  ).json()
 ).measurements
 
 const pattern = new Aaron({ measurements })

sites/dev/docs/reference/api/pattern/draftpartforset/readme.mdx

@@ -5,7 +5,9 @@ title: Pattern.draftPartForSet()
 A pattern's `draftPartForSet()` method will draft a part using a
 given set of settings.
 
-:::noteThis method is chainable as it returns the Pattern object:::
+:::note
+This method is chainable as it returns the Pattern object
+:::
 
 ## Pattern.draftPartForSet() signature
 
@@ -16,14 +18,10 @@ Pattern pattern.draftPartForSet(part, set)
 ## Pattern.draftPartForSet() example
 
 ```js
-import { Aaron } from "@freesewing/aaron"
+import { Aaron } from '@freesewing/aaron'
 
 // Load a public test settings set from the FreeSewing backend
-const set = (
+const set = await (await fetch('https://backend3.freesewing.org/curated-sets/1.json')).json()
-  await (
-    await fetch("https://backend3.freesewing.org/curated-sets/1.json")
-  ).json()
-)
 
 const pattern = new Aaron()
 

sites/dev/docs/reference/api/pattern/on/readme.mdx

@@ -7,7 +7,9 @@ pattern's [lifecycle hooks](/reference/hooks/). It takes the
 lifecycle hook's name as the first argument and the function as the second.
 This method will then be triggered by the lifecycle hook.
 
-:::noteThis method is chainable as it returns the Pattern object:::
+:::note
+This method is chainable as it returns the Pattern object
+:::
 
 ## Pattern.on() signature
 
@@ -27,7 +29,7 @@ should pass it.
 
 ```js
 pattern.on('preRender', function (svg) {
-  svg.style += "svg { background: yellow;}";
+  svg.style += 'svg { background: yellow;}'
 })
 ```
 

sites/dev/docs/reference/api/pattern/sample/readme.mdx

@@ -6,7 +6,9 @@ The `Pattern.sample()` method will _sample_ the pattern which means
 to draft multiple variants of the same pattern, and stack them on
 top of each other.
 
-:::noteThis method is chainable as it returns the Pattern object:::
+:::note
+This method is chainable as it returns the Pattern object
+:::
 
 Under the hood, this method will call one of
 [Pattern.sampleOption()](/reference/api/pattern/sampleoption),
@@ -34,19 +36,17 @@ Pattern pattern.sample()
 ## Pattern.sample() example
 
 ```js
-import { Aaron } from "@freesewing/aaron"
+import { Aaron } from '@freesewing/aaron'
 
 // Load some public test measurements from the FreeSewing backend
 const measurements = (
-  await (
+  await (await fetch('https://backend3.freesewing.org/curated-sets/1.json')).json()
-    await fetch("https://backend3.freesewing.org/curated-sets/1.json")
-  ).json()
 ).measurements
 
 const pattern = new Aaron({
   sample: {
-    models: measurements
+    models: measurements,
-  }
+  },
 })
 
 const svg = pattern.sample().render()

sites/dev/docs/reference/api/pattern/samplemeasurement/readme.mdx

@@ -13,7 +13,9 @@ the measurement of your choice between 90% and 110% if the value in the settings
 The goal of measurement sampling is to understand the impact of a given measurement on a pattern.
 :::
 
-:::noteThis method is chainable as it returns the Pattern object:::
+:::note
+This method is chainable as it returns the Pattern object
+:::
 
 ## Pattern.sampleMeasurement() signature
 
@@ -24,13 +26,11 @@ Pattern pattern.sampleMeasurement(string measurement)
 ## Pattern.sampleMeasurement() example
 
 ```js
-import { Aaron } from "@freesewing/aaron"
+import { Aaron } from '@freesewing/aaron'
 
 // Load some public test measurements from the FreeSewing backend
 const measurements = (
-  await (
+  await (await fetch('https://backend3.freesewing.org/curated-sets/1.json')).json()
-    await fetch("https://backend3.freesewing.org/curated-sets/1.json")
-  ).json()
 ).measurements
 
 const pattern = new Aaron({ measurements })

sites/dev/docs/reference/api/pattern/samplemodels/readme.mdx

@@ -12,7 +12,9 @@ In this particular case, it will draft a variants for each of the models you pas
 The goal of model sampling is to verify that a pattern grades correctly up and down as sizes change.
 :::
 
-:::noteThis method is chainable as it returns the Pattern object:::
+:::note
+This method is chainable as it returns the Pattern object
+:::
 
 ## Pattern.sampleModels() signature
 
@@ -52,16 +54,14 @@ identifying your model in the models object.
 ## Pattern.sampleModels() example
 
 ```js
-import { Aaron } from "@freesewing/aaron"
+import { Aaron } from '@freesewing/aaron'
 
 const Aaron = new Aaron()
 
 // Load some public test measurements from the FreeSewing backend
 const measurements = (
-  await (
+  await (await fetch('https://backend3.freesewing.org/curated-sets/1.json')).json()
-    await fetch("https://backend3.freesewing.org/curated-sets/1.json")
-  ).json()
 ).measurements
 
-const svg = aaron.sampleModels(measurements, "34").render()
+const svg = aaron.sampleModels(measurements, '34').render()
 ```

sites/dev/docs/reference/api/pattern/sampleoption/readme.mdx

@@ -20,7 +20,9 @@ The goal of option sampling is to verify the impact of an option on the pattern,
 its min and max boundaries are correct and its default value is sensible.
 :::
 
-:::noteThis method is chainable as it returns the Pattern object:::
+:::note
+This method is chainable as it returns the Pattern object
+:::
 
 ## Pattern.sampleOption() signature
 
@@ -31,13 +33,11 @@ Pattern pattern.sampleOption(string option)
 ## Pattern.sampleOption() example
 
 ```js
-import { Aaron } from "@freesewing/aaron"
+import { Aaron } from '@freesewing/aaron'
 
 // Load some public test measurements from the FreeSewing backend
 const measurements = (
-  await (
+  await (await fetch('https://backend3.freesewing.org/curated-sets/1.json')).json()
-    await fetch("https://backend3.freesewing.org/curated-sets/1.json")
-  ).json()
 ).measurements
 
 const pattern = new Aaron({ measurements })

sites/dev/docs/reference/api/pattern/use/readme.mdx

@@ -6,7 +6,9 @@ The `Pattern.use()` method will load a FreeSewing plugin.
 Plugins are a way to extend a pattern's functionality.
 For more details, refer to [the plugin guide](/guides/plugins/).
 
-:::noteThis method is chainable as it returns the Pattern object:::
+:::note
+This method is chainable as it returns the Pattern object
+:::
 
 ## Pattern.use() signature
 
@@ -22,14 +24,12 @@ you plugin object.
 ## Pattern.use() example
 
 ```js
-import { Aaron } from "@freesewing/aaron"
+import { Aaron } from '@freesewing/aaron'
-import { pluginTheme } from "@freesewing/plugin-theme"
+import { pluginTheme } from '@freesewing/plugin-theme'
 
 // Load some public test measurements from the FreeSewing backend
 const measurements = (
-  await (
+  await (await fetch('https://backend3.freesewing.org/curated-sets/1.json')).json()
-    await fetch("https://backend3.freesewing.org/curated-sets/1.json")
-  ).json()
 ).measurements
 
 const pattern = new Aaron({ measurements }).use(pluginTheme)

sites/dev/docs/reference/api/point/addcircle/readme.mdx

@@ -15,7 +15,9 @@ Point point.addCircle(
 )
 ```
 
-:::tipThis method is chainable as it returns the `Point` object:::
+:::tip
+This method is chainable as it returns the `Point` object
+:::
 
 ## Example
 
@@ -39,5 +41,7 @@ Point point.addCircle(
 
 return part
 }
+
 ```
 </Example>
+```

sites/dev/docs/reference/api/point/addtext/readme.mdx

@@ -15,7 +15,9 @@ Point point.addText(
 )
 ```
 
-:::tipThis method is chainable as it returns the `Point` object:::
+:::tip
+This method is chainable as it returns the `Point` object
+:::
 
 ## Example
 
@@ -32,12 +34,13 @@ Point point.addText(
 .line(points.anchor.shift(0, 80))
 .addClass('hidden')
 
-
 return part
 }
+
 ```
 </Example>
 
 ## Notes
 
 Remember to [use translation keys, not text](/guides/best-practices#use-translation-keys)
+```

sites/dev/docs/reference/api/point/attr/readme.mdx

@@ -18,8 +18,9 @@ Point point.attr(
 
 If the third parameter is set to `true` it will call [`this.attributes.set()`](/reference/api/attributes/set/) instead, thereby overwriting the value of the attribute.
 
-
+:::tip
-:::tipThis method is chainable as it returns the `Point` object:::
+This method is chainable as it returns the `Point` object
+:::
 
 ## Example
 
@@ -39,6 +40,7 @@ If the third parameter is set to `true` it will call [`this.attributes.set()`](/
 
 return part
 }
+
 ```
 </Example>
 
@@ -46,3 +48,4 @@ If the third parameter is set to `true` it will call [`this.attributes.set()`](/
 
 See [Using Attributes](/howtos/code/attributes)
 for information about custom Attributes that can be used with Points.
+```

sites/dev/docs/reference/api/point/clone/readme.mdx

@@ -11,7 +11,9 @@ attributes as the original point.
 Point point.clone()
 ```
 
-:::tipThis method is chainable as it returns the `Point` object:::
+:::tip
+This method is chainable as it returns the `Point` object
+:::
 
 ## Example
 
@@ -34,6 +36,7 @@ Point point.clone()
 
 return part
 }
+
 ```
 </Example>
 
@@ -43,3 +46,4 @@ Point point.clone()
 The [`Point.copy()`](/reference/api/point/copy/) method will only copy the
 point's coordinates, whereas this `Point.clone()` method will also copy its
 attributes.
+```

sites/dev/docs/reference/api/point/setcircle/readme.mdx

@@ -21,7 +21,9 @@ Point point.setCircle(
 )
 ```
 
-:::tipThis method is chainable as it returns the `Point` object:::
+:::tip
+This method is chainable as it returns the `Point` object
+:::
 
 ## Example
 
@@ -46,5 +48,7 @@ Point point.setCircle(
 
 return part
 }
+
 ```
 </Example>
+```

sites/dev/docs/reference/api/point/settext/readme.mdx

@@ -15,7 +15,9 @@ Point point.setText(
 )
 ```
 
-:::tipThis method is chainable as it returns the `Point` object:::
+:::tip
+This method is chainable as it returns the `Point` object
+:::
 
 ## Example
 
@@ -35,9 +37,11 @@ Point point.setText(
 
 return part
 }
+
 ```
 </Example>
 
 ## Notes
 
 Remember to [use translation keys, not text](/guides/best-practices#use-translation-keys)
+```

sites/dev/docs/reference/api/snippet/attr/readme.mdx

@@ -19,7 +19,9 @@ Snippet snippet.attr(
 )
 ```
 
-:::tipThis method is chainable as it returns the `Snippet` object:::
+:::tip
+This method is chainable as it returns the `Snippet` object
+:::
 
 ## Example
 
@@ -38,6 +40,7 @@ Snippet snippet.attr(
 
 return part
 }
+
 ```
 </Example>
 
@@ -45,3 +48,4 @@ Snippet snippet.attr(
 See [Using Attributes](/howtos/code/attributes)
 for information about what Attributes can be used with Snippets.
 :::
+```

sites/dev/docs/reference/api/snippet/rotate/readme.mdx

@@ -11,7 +11,9 @@ sets the `data-rotate` property.
 Snippet snippet.rotate(rotation, overwrite=true)
 ```
 
-:::tipThis method is chainable as it returns the `Snippet` object:::
+:::tip
+This method is chainable as it returns the `Snippet` object
+:::
 
 ## Example
 
@@ -33,6 +35,8 @@ Snippet snippet.rotate(rotation, overwrite=true)
 
 return part
 }
+
 ```
 </Example>
 
+```

sites/dev/docs/reference/api/snippet/scale/readme.mdx

@@ -11,7 +11,9 @@ sets the `data-scale` property.
 Snippet snippet.scale(scale, overwrite=true)
 ```
 
-:::tipThis method is chainable as it returns the `Snippet` object:::
+:::tip
+This method is chainable as it returns the `Snippet` object
+:::
 
 ## Example
 
@@ -22,7 +24,7 @@ Snippet snippet.scale(scale, overwrite=true)
 for (const i of [1,2,3,4,5,6]) {
 snippets[`demo${i}`] = new Snippet(
 "logo",
-      new Point(30*i, 0)
+new Point(30\*i, 0)
 ).scale(i/10)
 }
 
@@ -33,6 +35,8 @@ Snippet snippet.scale(scale, overwrite=true)
 
 return part
 }
+
 ```
 </Example>
 
+```

sites/dev/docs/reference/api/stack/addpart/readme.mdx

@@ -11,4 +11,6 @@ original stack.
 Stack stack.addPart(Part part)
 ```
 
-:::noteThis method is chainable as it returns the Stack object:::
+:::note
+This method is chainable as it returns the Stack object
+:::

sites/dev/docs/reference/api/stack/attr/readme.mdx

@@ -20,4 +20,6 @@ If the third parameter is set to `true` it will call
 `this.attributes.set()` instead,
 thereby overwriting the value of the attribute.
 
-:::noteThis method is chainable as it returns the Stack object:::
+:::note
+This method is chainable as it returns the Stack object
+:::

sites/dev/docs/reference/api/stack/generatetransform/readme.mdx

@@ -5,7 +5,6 @@ title: Stack.generateTransform()
 The `Stack.generateTransform()` method generates SVG transforms for the stack,
 sets them as attributes, and returns the original stack.
 
-
 ## Stack.generateTransform() signature
 
 ```js
@@ -17,10 +16,12 @@ an object with the following properties containing the transforms
 to apply:
 
 | Property | Type    | Description                                                                   |
-|----------|------|------------|
+| -------- | ------- | ----------------------------------------------------------------------------- |
-| `move`   | Object | `move.x` and `move.y` are coordinates to which the stack should be translated
+| `move`   | Object  | `move.x` and `move.y` are coordinates to which the stack should be translated |
 | `rotate` | Number  | The number of degrees to rate the stack around its center                     |
 | `flipX`  | Boolean | Whether to flip the stack along the X axis                                    |
 | `flipY`  | Boolean | Whether to flip the stack along the Y axis                                    |
 
-:::noteThis method is chainable as it returns the Stack object:::
+:::note
+This method is chainable as it returns the Stack object
+:::

sites/dev/docs/reference/api/stack/home/readme.mdx

@@ -11,7 +11,10 @@ and returns the original stack.
 ```js
 Stack stack.home()
 ```
-:::noteThis method is chainable as it returns the Stack object:::
+
+:::note
+This method is chainable as it returns the Stack object
+:::
 
 ## Notes
 

sites/dev/docs/reference/api/store/extend/readme.mdx

@@ -13,7 +13,9 @@ rather through a plugin.
 Store Store.extend(Array methods=[])
 ```
 
-:::tipThis method is chainable as it returns the `Store` object:::
+:::tip
+This method is chainable as it returns the `Store` object
+:::
 
 The single argument should be an Array of methods to add to the
 store. Each entry in the array should be an array itself holding a path in
@@ -26,9 +28,7 @@ function myCustomMethod(store, ...otherArguments) {
   // Do something clever
 }
 
-const store = new Store([
+const store = new Store([['path.to.the.method', myCustomMethod]])
-  ["path.to.the.method", myCustomMethod ]
-])
 ```
 
 With the configuration above, you can call `store.path.to.the.method()` and it
@@ -46,5 +46,3 @@ The Store will not allow you to extend any of the following keys:
 - `unset`
 - `get`
 - `extend`
-
-

sites/dev/docs/reference/api/store/push/readme.mdx

@@ -12,18 +12,18 @@ If `key` does not hold and Array, the Store will log a warning, but nothing will
 Store store.push(mixed value1, mixed value2, ...)
 ```
 
-:::noteThis method is [variadic](https://en.wikipedia.org/wiki/Variadic_function):::
+:::note
+This method is [variadic](https://en.wikipedia.org/wiki/Variadic_function)
+:::
 
-:::tipThis method is chainable as it returns the `Store` object:::
+:::tip
+This method is chainable as it returns the `Store` object
+:::
 
 ## Example
 
 ```js
 const store = new Store()
 store.set('example', ['Hi there'])
-store.push(
+store.push('How are you doing', 'How are YOU doing')
- 'How are you doing',
- 'How are YOU doing'
-)
 ```
-

sites/dev/docs/reference/api/store/set/readme.mdx

@@ -11,7 +11,9 @@ The `Store.set()` method stores the value of `value` in the store under key
 Store store.set(mixed key, mixed value)
 ```
 
-:::tipThis method is chainable as it returns the `Store` object:::
+:::tip
+This method is chainable as it returns the `Store` object
+:::
 
 ## Example
 
@@ -42,4 +44,3 @@ value = store.get(['my', 'other', 'nested', 'example']) // works
 value = store.my.nested.example // Also works
 value = store.my.other.nested.example // Also works
 ```
-

sites/dev/docs/reference/api/store/setifunset/readme.mdx

@@ -11,7 +11,9 @@ The `Store.set()` method stores the value of `value` in the store under key
 Store store.set(mixed key, mixed value)
 ```
 
-:::tipThis method is chainable as it returns the `Store` object:::
+:::tip
+This method is chainable as it returns the `Store` object
+:::
 
 ## Example
 
@@ -20,4 +22,3 @@ const store = new Store()
 store.set('example', 'Hi there')
 store.setIfUnset('example', 'Hi again') // This has no effect
 ```
-

sites/dev/docs/reference/api/store/unset/readme.mdx

@@ -10,12 +10,12 @@ The `Store.unset()` value removes a `key` from the store.
 Store store.unset(string key)
 ```
 
-:::tipThis method is chainable as it returns the `Store` object:::
+:::tip
+This method is chainable as it returns the `Store` object
+:::
 
 ## Example
 
 ```js
-const store = new Store()
+const store = new Store().set('example', 'I will be gone before you know it').unset('example')
-  .set('example', 'I will be gone before you know it')
-  .unset('example')
 ```

sites/dev/docs/tutorials/getting-started-linux/dev-setup/readme.mdx

@@ -36,6 +36,7 @@ git clone https://github.com/your-username/freesewing
 cd freesewing
 yarn kickstart
 ```
+
 :::
 
 This sets up the monorepo. If you would like to create a new design, run the
@@ -141,7 +142,9 @@ environment inside.
 Now you're ready to [start the development
 environment](/tutorials/getting-started-linux/dev-start).
 
-:::tipThe folder will have the name you chose above.:::
+:::tip
+The folder will have the name you chose above.
+:::
 
 :::note
 

sites/dev/docs/tutorials/getting-started-linux/readme.mdx

@@ -10,4 +10,6 @@ We'll cover the following steps:
 
 <ReadMore />
 
-:::tipThese instructions are also valid for BSD or other Unix systems:::
+:::tip
+These instructions are also valid for BSD or other Unix systems
+:::

sites/dev/docs/tutorials/getting-started-mac/dev-setup/readme.mdx

@@ -36,6 +36,7 @@ git clone https://github.com/your-username/freesewing
 cd freesewing
 yarn kickstart
 ```
+
 :::
 
 This sets up the monorepo. If you would like to create a new design, run the
@@ -126,7 +127,9 @@ environment inside.
 Now you're ready to [start the development
 environment](/tutorials/getting-started-linux/dev-start).
 
-:::tipThe folder will have the name you chose above.:::
+:::tip
+The folder will have the name you chose above.
+:::
 
 :::note
 

sites/dev/docs/tutorials/getting-started-windows/readme.mdx

@@ -35,11 +35,13 @@ FreeSewing project.
 
 ### Install WSL
 
-:::warning This guide uses WSL version 2, which requires installing the Hyper-V
+:::warning
+This guide uses WSL version 2, which requires installing the Hyper-V
 virtualisation system. If you have another virtualisation system installed (such
 as VirtualBox or VMWare) you may run into conflicts which require either
 updating that system to a version which can use the HyperV backend or porting
-your existing machines to use HyperV.  :::
+your existing machines to use HyperV.
+:::
 
 Follow the [Windows Subsystem for Linux Installation Guide for Windows
 10](https://docs.microsoft.com/en-gb/windows/wsl/install-win10) (requires a
@@ -63,10 +65,12 @@ then activate using `nvm use <version>`. You can determine what version the
 FreeSewing project uses by checking
 [freesewing/freesewing/.nvmrc](https://github.com/freesewing/freesewing/blob/develop/.nvmrc).
 
-:::warning At the time this guide was written the latest version of Node.js/npm has
+:::warning
+At the time this guide was written the latest version of Node.js/npm has
 a bug in the dependency resolution process which causes the freesewing project
 to fail to build. Use the latest LTS version (currently 18.17.0) or the specific
-version used by the main project to avoid this issue.  :::
+version used by the main project to avoid this issue.
+:::
 
 Node.js comes with the Node Package Manager (npm) by default which can be used to
 set up the project. The default package manager uses a fairly simplistic approach
@@ -122,7 +126,6 @@ this guide you have already done steps 1 and 2, you will only need to install
 the [remote development
 extension](https://aka.ms/vscode-remote/download/extension))
 
-
 ## Setting up a development environment in Windows.
 
 ### Install NVM
@@ -165,9 +168,12 @@ In VSCode or in a terminal, navigate to the folder you wish to contain your new
 After you've answered [some questions](#questions), it will take a while to set everything up.
 When it's done, you will have a new folder with the development environment inside.
 
-:::tipThe folder will have the name you chose above.:::
+:::tip
+The folder will have the name you chose above.
+:::
 
 :::note
+
 ### Questions
 
 #### What template to use

sites/dev/docs/tutorials/pattern-design/part2/creating-the-closure/readme.mdx

@@ -17,7 +17,9 @@ tedious. There are macros to add titles to our pattern, or grainline
 indicators, a scalebox, and there's a macro to round corners. The `round`
 macro.
 
-:::note You can find more information on the `round` macro in [the macros docs](/reference/macros/round/).:::
+:::note
+You can find more information on the `round` macro in [the macros docs](/reference/macros/round/).
+:::
 
 We need a half circle here, but the `round` macro works on 90° angles, so
 we'll use it twice. As such, we'll add some points to guide the macro, and
@@ -41,22 +43,24 @@ function draftBib({
   part,
 }) {
 
-  /*
+/\*
-   * Construct the quarter neck opening
+
-   */
+- Construct the quarter neck opening
+  _/
   let tweak = 1
-  let target = (measurements.head * options.neckRatio) /4
+  let target = (measurements.head _ options.neckRatio) /4
   let delta
   do {
   points.right = new Point(
-      tweak * measurements.head / 10, 
+  tweak _ measurements.head / 10,
   0
   )
   points.bottom = new Point(
   0,
-      tweak * measurements.head / 12
+  tweak _ measurements.head / 12
   )
 
+
     points.rightCp1 = points.right.shift(
       90,
       points.bottom.dy(points.right) / 2
@@ -78,11 +82,13 @@ function draftBib({
     delta = paths.quarterNeck.length() - target
     if (delta > 0) tweak = tweak * 0.99
     else tweak = tweak * 1.02
+
 } while (Math.abs(delta) > 1)
 
-  /*
+/\*
-   * Construct the complete neck opening
+
-   */
+- Construct the complete neck opening
+  \*/
   points.rightCp2 = points.rightCp1.flipY()
   points.bottomCp1 = points.bottomCp2.flipX()
   points.left = points.right.flipX()
@@ -101,11 +107,12 @@ function draftBib({
 .close()
 .addClass('fabric')
 
-  /*
+/\*
-   * Drawing the bib outline
+
-   */
+- Drawing the bib outline
-  const width = measurements.head * options.widthRatio
+  _/
-  const length = measurements.head * options.lengthRatio
+  const width = measurements.head _ options.widthRatio
+  const length = measurements.head \* options.lengthRatio
 
 points.topLeft = new Point(
 width / -2,
@@ -115,9 +122,10 @@ function draftBib({
 points.bottomLeft = points.topLeft.shift(-90, length)
 points.bottomRight = points.topRight.shift(-90, length)
 
-  /*
+/\*
-   * Shape the straps
+
-   */
+- Shape the straps
+  \*/
   points.edgeLeft = new Point(points.topLeft.x, points.left.y)
   points.edgeRight = new Point(points.topRight.x, points.right.y)
   points.edgeTop = new Point(0, points.topLeft.y)
@@ -155,8 +163,9 @@ function draftBib({
 // highlight-end
 
     /*
-   * Now, adapt our `rect` path so it's no longer a rectangle:
+
-   */
+- Now, adapt our `rect` path so it's no longer a rectangle:
+  \*/
   paths.rect = new Path()
   .move(points.edgeTop)
   .curve(points.edgeTopLeftCp, points.edgeLeftCp, points.edgeLeft)
@@ -168,7 +177,9 @@ function draftBib({
 
 return part
 }
+
 ```
 </Example>
 
 Notice that we always draw our path at the end after we've manipulated our points.
+```

sites/dev/docs/tutorials/pattern-design/part2/draft-method/readme.mdx

@@ -19,12 +19,12 @@ does.
 ## Destructuring the function parameter
 
 If you're not familiar with the `({ part })` syntax you see above, this is a
-technique called *parameter destructuring* or more generally, [object
+technique called _parameter destructuring_ or more generally, [object
 destructuring](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment).
 
 The draft method receives only 1 parameter: An object that holds everything we
-need to draft our method.  Destructuring is a way to *pull things out of the
+need to draft our method. Destructuring is a way to _pull things out of the
-object into their own variable*. It saves us a bunch of typing as these two are
+object into their own variable_. It saves us a bunch of typing as these two are
 equivalent:
 
 <Tabs>
@@ -53,7 +53,7 @@ function draftBib({ part }) {
 
 As we'll make our way through this tutorial, we'll need more and more stuff, so
 we'll be pulling it out of the object passed to the draft method via
-*destructuring*.
+_destructuring_.
 
 :::note
 
@@ -92,7 +92,9 @@ Here's a brief summary of the things we've added above:
 - `points`: A container object to hold the part's points
 - `paths`: A container object to hold the part's paths
 
-:::tipRemember: Constructors start with a **C**apital letter:::
+:::tip
+Remember: Constructors start with a **C**apital letter
+:::
 
 Long story short: These will make it possible for us to draw points and paths easily.
 

sites/dev/docs/tutorials/pattern-design/part3/i18n/readme.mdx

@@ -3,5 +3,6 @@ title: Supporting translation
 order: 80
 ---
 
-:::note [FIXME]Write this section for v3:::
+:::note [FIXME]
-
+Write this section for v3
+:::

sites/dev/docs/tutorials/pattern-design/part3/menu/readme.mdx

@@ -42,6 +42,7 @@ If you set a `menu` property on your option, the FreeSewing frontend will use
 this to organize your various options in a menu structure.
 
 ### Sub menus
+
 You can a nested menu structure with dot-notation. So `style.pockets` will
 create a `pockets` submenu under the `style` menu and put your option there.
 
@@ -65,4 +66,6 @@ function(
 
 This is typically used to hide options conditionally.
 
-:::note [FIXME]Include example:::
+:::note [FIXME]
+Include example
+:::

sites/dev/docs/tutorials/pattern-design/part3/tests/readme.mdx

@@ -3,13 +3,13 @@ title: Testing your designs
 order: 70
 ---
 
-:::note [FIXME] Update this for v3 :::
-
 With the basic outline of our pattern ready, now would be a good time
 to test it to see how well it adapts to different measurements,
 and the range of options we provided.
 
 :::note [FIXME]
+Update this for v3
+
 This page needs to be updated with screenshots from the v3 development
 environment
 :::
@@ -54,7 +54,9 @@ that it only influences the length:
 ![This is what it should look like when we test the `lengthRatio`
 option](test-option-lengthratio.png)
 
-:::note [FIXME]Update screenshot for v3:::
+:::note [FIXME]
+Update screenshot for v3
+:::
 
 ### neckRatio
 
@@ -68,7 +70,9 @@ smaller, we will rotate the straps further out of the way to avoid overlap:
 ![This is what it should look like when we test the `neckRatio`
 option](test-option-neckratio.png)
 
-:::note [FIXME]Update screenshot for v3:::
+:::note [FIXME]
+Update screenshot for v3
+:::
 
 ### widthRatio
 
@@ -84,7 +88,9 @@ bib shorter when it's worn.
 ![This is what it should look like when we test the `widthRatio`
 option](test-option-widthratio.png)
 
-:::note [FIXME]Update screenshot for v3:::
+:::note [FIXME]
+Update screenshot for v3
+:::
 
 :::note
 
@@ -106,7 +112,9 @@ measurement is influencing the pattern.
 
 For our bib, we only use one measurement, so it influences the entire pattern.
 
-:::note [FIXME]Add screenshot:::
+:::note [FIXME]
+Add screenshot
+:::
 
 ## Testing measurments sets
 
@@ -121,7 +129,9 @@ ends up being the same as testing a complete set of measurements.
 But most patterns use multiple measurements, and we'll find this test gives
 us insight into how our pattern will adapt to differently sized bodies.
 
-:::note [FIXME]Add screenshot:::
+:::note [FIXME]
+Add screenshot
+:::
 
 ## The antperson test
 
@@ -130,7 +140,7 @@ our pattern with a set of _typical_ measurements , and then drafts it again
 with measurements that are 1/10th of those _typical_ measurements.
 
 It is named after [the cartoon
-character](https://en.wikipedia.org/wiki/Ant-Man_\(film\)) who can shrink, yet
+character](<https://en.wikipedia.org/wiki/Ant-Man_(film)>) who can shrink, yet
 somehow his suit still fits.
 
 The purpose of the antperson test is to bring out areas in our pattern where
@@ -141,7 +151,9 @@ instructions don't scale, and we should avoid them.
 The best patterns will pass the antperson test with 2 patterns exactly the
 same, where one will simply be 1/10th the scale of the other.
 
-:::note [FIXME]Add screenshot:::
+:::note [FIXME]
+Add screenshot
+:::
 
 When we're happy with how our pattern passes these tests, it's time to
 complete our design.