Fix references to 'Design guide'
This commit is contained in:
parent
f6f42cced4
commit
6701b61f86
2 changed files with 4 additions and 4 deletions
|
@ -157,7 +157,7 @@ paths.quarterNeck = new Path()
|
|||
- We're following up with a `Path.move()` call that takes one Point as argument
|
||||
- Then, there's a `Path.curve()` call that takes 3 points as arguments
|
||||
|
||||
If you've read through the high-level [Pattern guide](/guides/patterns) you
|
||||
If you've read through the high-level [Design guide](/guides/designs) you
|
||||
will have learned that paths always start with a `move()` operation. In this
|
||||
case, we moved to our `right` points.
|
||||
|
||||
|
|
|
@ -8,12 +8,12 @@ rather simple, we have learned a bunch of things along the way.
|
|||
|
||||
## More reading material
|
||||
|
||||
- If you haven't done so already, read through [the pattern
|
||||
guide](/guides/patterns/) which provides a good overview of how patterns work
|
||||
- If you haven't done so already, read through [the design
|
||||
guide](/guides/designs/) which provides a good overview of how designs work
|
||||
under the hood
|
||||
- Bookmark [the FreeSewing API docs](/reference/api/), they are your reference
|
||||
every time you're not entirely certain how something works
|
||||
- Have a look at [the design guide](/guides/best-practices/) for best practices
|
||||
- Have a look at [the pattern design best practices](/guides/best-practices/) for best practices
|
||||
that will help you make the best possible patterns
|
||||
|
||||
## What to do next
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue