From 045b04383ce4c7f1a7d9a5a945f7ac0d2c1d3c7a Mon Sep 17 00:00:00 2001 From: "j.goderbauer" <j.goderbauer@adito.de> Date: Wed, 1 Apr 2020 15:22:32 +0200 Subject: [PATCH] KeywordEntry: minor documentation improvements --- entity/KeywordEntry_entity/documentation.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/entity/KeywordEntry_entity/documentation.adoc b/entity/KeywordEntry_entity/documentation.adoc index aef0ab515a..17d50062e3 100644 --- a/entity/KeywordEntry_entity/documentation.adoc +++ b/entity/KeywordEntry_entity/documentation.adoc @@ -96,10 +96,10 @@ You've got a Keyword-container for Types of Communication with basically the fol If you want to add a general type of information like "PHONE", "MAIL", "WEB" you've to add a keyword-attribute to the keyword-entry where you can store that information. -=== Complex Keyword as own entity === +=== Complex Keyword as separate entity === Sometimes you've a special case where the keyword entity cannot provide all the functionality. -In that case you can always define your own entity and create your own database structure to represent all the information and provide all the functions you need. +In that case you can always define your separate entity and create your separate database structure to represent all the information and provide all the functions you need. -As an example, this could be the `Country_Entity` \ No newline at end of file +As an example, this could be the `Countries_Entity` \ No newline at end of file -- GitLab