chore: Merged in left behind PRs from markdown repo

markdown/dev/howtos/code/accessing-measurements/en.md

@@ -7,7 +7,7 @@ about: Shows you how to access user measurements from inside your pattern
 Measurements are stored in `pattern.settings.measurements`.
 
 You can pull them out of there with 
-the [shorthand](/howtos/core/shorthand/) call:
+the [shorthand](/howtos/code/shorthand/) call:
 
 
 ```js

markdown/dev/howtos/code/accessing-options/en.md

@@ -7,7 +7,7 @@ about: Shows you how to access user options from inside your pattern
 Options are stored in `pattern.settings.options`.
 
 You can pull them out of there with 
-the [shorthand](/howtos/core/shorthand/) call:
+the [shorthand](/howtos/code/shorthand/) call:
 
 
 ```js

markdown/dev/howtos/code/adding-paths/en.md

@@ -5,7 +5,7 @@ icon: pattern
 about: Shows you how to add paths to your pattern
 ---
 
-After using the [shorthand](/howtos/core/shorthand/) call, 
+After using the [shorthand](/howtos/code/shorthand/) call, 
 `Path` contains the path constructor, while `paths` is a reference to `part.paths`,
 which is where you should store your paths.
 

markdown/dev/howtos/code/adding-points/en.md

@@ -4,7 +4,7 @@ for: developers
 about: Shows you how to add points to your pattern
 ---
 
-After using the [shorthand](/howtos/core/shorthand/) call, 
+After using the [shorthand](/howtos/code/shorthand/) call, 
 `Point` contains the point constructor, while `points` is a reference to `part.points`,
 which is where you should store your points.
 

markdown/dev/howtos/code/adding-snippets/en.md

@@ -4,7 +4,7 @@ for: developers
 about: Shows you how to add snippets to your pattern
 ---
 
-After using the [shorthand](/howtos/core/shorthand/) call, 
+After using the [shorthand](/howtos/code/shorthand/) call, 
 `Snippet` contains the path constructor, while `snippets` is a reference to `part.snippets`,
 which is where you should store your paths.
 
@@ -21,7 +21,7 @@ You can scale and rotate a snippet by setting the `data-scale` and `data-rotate`
 
 <Tip>
 
-See [Using attributes](/howtos/core/attributes/) for details on how to set attributes.
+See [Using attributes](/howtos/code/attributes/) for details on how to set attributes.
 
 </Tip>
 

markdown/dev/howtos/code/dependencies/en.md

@@ -4,7 +4,7 @@ for: developers
 about: Shows you how to create dependencies between pattern parts
 ---
 
-Part dependencies are set in the [pattern configuration](/config), and
+Part dependencies are set in the [pattern configuration](/reference/config), and
 control the order in which parts are drawn. FreeSewing will make sure
 that before drafting a part, it will first draft all its dependencies.
 
@@ -21,7 +21,7 @@ dependencies: {
 This could be from a T-shirt pattern where the `front` and `back` patterns are very similar, 
 so they both are inheriting a `base` part.
 In addition, the `sleeve` part needs to be drafted after the `front` and `back` part because
-in `front` and `back` we store the length of the armhole seam in the [store](/api/store) and
+in `front` and `back` we store the length of the armhole seam in the [store](/reference/api/store) and
 we need that info to fit the sleevecap to the armhole.
 
 Now if a user requests to draft only the `sleeve` part, FreeSewing will still draft:
@@ -34,6 +34,6 @@ but it will only render the `sleeve` part, as that's the only thing the user req
 
 <Note>
 
-For inheriting parts, please refer to [part inheritance](/howtos/core/inject/).
+For inheriting parts, please refer to [part inheritance](/howtos/code/inject/).
 
 </Note>

markdown/dev/howtos/code/store/en.md

@@ -9,7 +9,7 @@ For example, you may store the length of the armhole in your front and back part
 and then read that value when drafting the sleeve so you can verify the sleeve fits the armhole.
 
 For this, you should use the [Store](/reference/api/store/), which is available via 
-the [shorthand](/howtos/core/shorthand/) call:
+the [shorthand](/howtos/code/shorthand/) call:
 
 ```js
 export default function(part) {