VSinerva/freesewing
1
0
Fork 0
Code Activity

chore(markdown): Linter fixes

Browse source
This commit is contained in:
Joost De Cock 2022-02-18 18:33:38 +01:00
parent e146a451da
commit 1d8beedd44
6 changed files with 12 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

1
markdown/dev/guides/best-practices/go-counter-clockwise/en.md
View file

@ -19,7 +19,6 @@ When naming control points for curves, re-use the name of the point they are att
and add `Cp1` to the control point before and `Cp2` to the control point after the point if and add `Cp1` to the control point before and `Cp2` to the control point after the point if
, once again, you'd follow your path counter-clockwise. , once again, you'd follow your path counter-clockwise.
For example: For example:
```js ```js

1
markdown/dev/guides/best-practices/respect-draft-settings/en.md
View file

@ -62,4 +62,3 @@ export default function(part) {
return part return part
} }
``` ```

1
markdown/dev/guides/best-practices/reuse-measurements/en.md
View file

@ -15,4 +15,3 @@ The [measurements reference page](/reference/measurements/)
contains all our standard measurement names. contains all our standard measurement names.
</Tip> </Tip>

1
markdown/dev/guides/best-practices/reuse-options/en.md
View file

@ -9,4 +9,3 @@ While your pattern may require some very specific
options, there's probably a bunch that are similar to other patterns. Re-use those names. options, there's probably a bunch that are similar to other patterns. Re-use those names.
As in, `bicepsEase` exists. So don't go creating an `upperArmEase` option. As in, `bicepsEase` exists. So don't go creating an `upperArmEase` option.

1
markdown/dev/guides/best-practices/use-percentages/en.md
View file

@ -29,4 +29,3 @@ FreeSewing's development environment provides these tests out of the box,
so you can see their results at the click of a button. so you can see their results at the click of a button.
</Tip> </Tip>