From c2c9a7dbc2073991b98eb7f44edf7862000ea8a8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20B=C3=B6hmer?= Date: Tue, 20 Dec 2022 15:08:18 +0100 Subject: [PATCH] Updated Concepts (markdown) --- Concepts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Concepts.md b/Concepts.md index e58ab26..62d9b38 100644 --- a/Concepts.md +++ b/Concepts.md @@ -4,7 +4,7 @@ This page explains the different concepts of Part-DB and what their intended use ## Part managment ### Part -A part is the central concept of Part-DB. A part represents a single kind (or type) of a thing, like an electronic component, an device, an book or similar (depending on what you use Part-DB for). A part entity just represents a certain type of a thing, so if you have 1000 times an BC547 transistor you would create ONE part with the name BC547 and set its quantity to 1000. +A part is the central concept of Part-DB. A part represents a single kind (or type) of a thing, like an electronic component, an device, an book or similar (depending on what you use Part-DB for). A part entity just represents a certain type of a thing, so if you have 1000 times an BC547 transistor you would create ONE part with the name BC547 and set its quantity to 1000. The individual quantities (so a single BC547 transistor) of a part, should be indistinguishable from each other, so that it does not matter which one of your 1000 things of Part you use. ## User System ### User