1
0
Fork 0

fix(docs): Correct small typos

This commit is contained in:
Benjamin F 2022-12-14 12:52:37 -08:00
parent 265833d419
commit fea16617d4
31 changed files with 36 additions and 36 deletions

View file

@ -2,7 +2,7 @@
title: Setting a value in millimeter as a percentage option
---
Percentage options are great for parametric desing, but not always
Percentage options are great for parametric design, but not always
very intuitive for the user. For example: A user may desire 13
centimeters (5 inches) of chest ease. But what percentage should
they set the `chestEase` option to to accomplish this?

View file

@ -22,10 +22,10 @@ Your snapped percentage option should be a plain object with these properties:
##### Values for snapped percentage options are available through `absoluteOptions`
Your draft method can not only destructure the `options` property to get access to options,
it can also desctructure the `absoluteOptions` property to get access to the values
it can also destructure the `absoluteOptions` property to get access to the values
for those options with snaps configured.
See [the part `draft()` method](/reference/api/part/draft) for mor details.
See [the part `draft()` method](/reference/api/part/draft) for more details.
</Tip>
@ -179,7 +179,7 @@ under the hood, let's first agree on terminology:
Its value always represents a percentage. For example `0.5` for 50%.
- The **millimeter value** is the result of feeding the **percentage value** to
the `toAbs()` method. Its value always represents millimeters. For example `12mm`.
- The **snap values** are the values provided by the snap confguration.
- The **snap values** are the values provided by the snap configuration.
Each of the values always represents millimeters (even for imperial users).
Under the hood, and snapped percentage option will:

View file

@ -2,7 +2,7 @@
title: Reporting a percentage option value in millimeter
---
Percentage options are great for parametric desing, but not always
Percentage options are great for parametric design, but not always
very intuitive for the user. For example: Setting the `chestEase`
option to `9%` is not very meaningful unless you happen to know
what that percentage is based on.