Skip to content

Commit 8faa325

Browse files
authored
Update verbiage (#788)
1 parent 56fc140 commit 8faa325

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/concepts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ each other so that it does not matter which one of your 1000 things of Part you
2323
A part entity has many fields, which can be used to describe it better. Most of the fields are optional:
2424

2525
* **Name** (Required): The name of the part or how you want to call it. This could be a manufacturer-provided name, or a
26-
name you thought of yourself. The name have to be unique in a single category.
26+
name you thought of yourself. Each name needs to be unique and must exist in a single category.
2727
* **Description**: A short (single-line) description of what this part is/does. For longer information, you should use
2828
the comment field or the specifications
2929
* **Category** (Required): The category (see there) to which this part belongs to.
@@ -239,4 +239,4 @@ replaced with data for the actual thing.
239239

240240
You do not have to define a label profile to generate labels (you can just set the settings on the fly in the label
241241
dialog), however, if you want to generate many labels, it is recommended to save the settings as a label profile, to save
242-
it for later usage. This ensures that all generated labels look the same.
242+
it for later usage. This ensures that all generated labels look the same.

0 commit comments

Comments
 (0)