correct documentation property

entity/360Degree_entity/documentation.adoc

 = 360Degree_entity
 
-The 360Degree_entity shows the Connection between datenmodells.
-The entity has two providers for persons and organisations.
+The 360Degree_entity shows the Connection between data models.
+The entity has two providers for persons and organizations.
 
 The 360Degree_entity shows direct connections, don´t be confused with the ObjectRelation_entity.
 

entity/ActivityLink_entity/documentation.adoc

 = ActivityLink_entity
 
-Displays the connection between Activity and another module (for example Person).
\ No newline at end of file
+Displays the connection between an Activity and another module (for example Person).
\ No newline at end of file

entity/AddressType_entity/documentation.adoc

@@ -3,5 +3,5 @@
 Displays the AdressType Keyword ($KeywordRegistry.addressType()).
 In the condition of the recordcontainer the entity differs between organisation and contact.
 
-You need a own entty for this case because the KeywordEntry_entity 
+You need an own entity for this case because the KeywordEntry_entity 
 provides all information without checking conditions for KeywordAttribute.
\ No newline at end of file

entity/Address_entity/documentation.adoc

 = Address_entity
 
 ----
-an entity for logic behind a postal address
+an entity for the logic behind a postal address
 ----
 
 The entity manages storing postal addresses and provides features like validation.
 
-Every `CONTACT` has one standard address value that is used by default for some actions. Keep in mind that this standard address has a special status and therefore may cannot be deleted.
+Every `CONTACT` has one standard address value that is used by default for some actions. Keep in mind that this standard address has a special status and therefore cannot be deleted.
 
 Webservice Validation: See WsValidation_lib
 To enable the nominatim webservice: go to Preferences -> _____PREFERENCES_PROJECT -> _____PREFERENCES_PROJECT

entity/AdminViewRow_entity/documentation.adoc

 = AdminViewRow_entity
 
-Displays the rows of administrative information of a entity.
-The entity "DefaultAdminView_entity" uses the data for display the rows (for example Person-ID, Contact-ID)
\ No newline at end of file
+Displays the rows of administrative information of an entity.
+The entity "DefaultAdminView_entity" uses the data for displaying the rows (for example Person-ID, Contact-ID)
\ No newline at end of file

entity/Analyses_entity/documentation.adoc

 = Analyses_entity
 
-Logic and information for the ScoreCard displays openTasks, apointments, ... for the logged in user
\ No newline at end of file
+Logic and information for the ScoreCard displays open tasks, appointments, etc. for the logged in user
\ No newline at end of file

entity/AnyContact_entity/documentation.adoc

 = AnyContact_entity
 
-Displays both a contact and organisation in one entity with the common denominator
\ No newline at end of file
+Displays both a contact and an organisation in one entity with the common denominator
\ No newline at end of file

entity/AttributeUsage_entity/documentation.adoc

 = AttributeUsage_entity
 
 ----
-an entity for defining in what contexts an attribute can be used
+an entity for defining in which contexts an attribute can be used
 ----
\ No newline at end of file

entity/BulkMailAddRecipients_entity/documentation.adoc

 = BulkMailAddRecipients_entity
 
-This entity handling the serial action to add more than one organisation / person to a bulkmail.
+This entity handles the serial action to add more than one organisation / person to a bulkmail.
 This action can´t be done with the BulkMailRecipient_entity, because a entity displays always one dataset.
\ No newline at end of file

entity/BulkMailTesting_entity/documentation.adoc

 = BulkMailStatusChart_entity
 
-This entity handling the testing of an bulk mail (test sending to a contact)
\ No newline at end of file
+This entity is responsible for the testing of a bulk mail (test sending to a contact)
\ No newline at end of file

entity/CampaignCost_entity/documentation.adoc

 = CampaignCost_entity
 
-Calculates all the information for the costs of an campaign.
-There is also a entity "CampaignCostChart_entity" to display this information via charts.
+Calculates all the information for the costs of a campaign.
+There is also an entity "CampaignCostChart_entity" to display this information via charts.
 
 There are different providers for costs of the campaign itself and for costs of campaignsteps.
\ No newline at end of file

entity/Campaign_entity/documentation.adoc

 = Campaign_entity
 
 Provides the main-function for working with campaigns.
-The campaign itself consumes other entitys for participants, costs an the standard entities like activity, task, ...
\ No newline at end of file
+The campaign itself consumes other entities for participants, costs and the standard entities like activity, task, ...
\ No newline at end of file

entity/KeywordAttribute_entity/documentation.adoc

@@ -22,5 +22,5 @@ You might ask:
 
 > Why are there no essential Keyword-Attributes?
 
-The reason therefore is: Currently the Keyword-Attributes can only be used by a developer within JDito-Code.
+The reason for this is that currently the Keyword-Attributes can only be used by a developer within JDito-Code.
 So there is no need to add, modify, etc. the Keyword-Attributes for an administrator/power-user.
\ No newline at end of file

entity/KeywordEntry_entity/documentation.adoc

@@ -82,7 +82,7 @@ And, to clarify an example:
 
 === Extended Key-Value lists with special Attributes ===
 
-Basically this is a extension of the <<Simple Key-Value lists>>.
+Basically this is an extension of the <<Simple Key-Value lists>>.
 Sometimes it's necessary to have some more properties within a keyword-entry.
 Example:
 
@@ -100,6 +100,6 @@ If you want to add a general type of information like "PHONE", "MAIL", "WEB" you
 
 Sometimes you've a special case where the keyword entity cannot provide all the functionality. 
 
-In that case you can always define you 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 own entity and create your own 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

entity/Role_entity/documentation.adoc

 = Role_entity
 
-Link the roles to the users. Also used in the authorization concept
\ No newline at end of file
+Links the roles to the users. Also used in the authorization concept
\ No newline at end of file

entity/TurnoverTree_entity/documentation.adoc

@@ -2,4 +2,4 @@
 
 For technical docu see the contentProcess of the jdito-record container of this entity
 
-This entity provides information to display the Turnover via tree.
\ No newline at end of file
+This entity provides information to display the turnover via tree.
\ No newline at end of file

entity/UnlinkedMail_entity/documentation.adoc

 = UnlinkedMail_entity
 
-Entity for displaying and managing unlinked mails. This is also provided as Dashlet
\ No newline at end of file
+Entity for displaying and managing unlinked mails. This is also provided as a Dashlet
\ No newline at end of file

language/_____LANGUAGE_de/_____LANGUAGE_de.aod

@@ -3752,7 +3752,7 @@
       <value>Verband</value>
     </entry>
     <entry>
-      <key>ankle of</key>
+      <key>grandchild of</key>
     </entry>
     <entry>
       <key>solicits</key>