[skip ci] A few more details about the local lookup

Author: Chris Wiechmann

README.md

@@ -494,15 +494,15 @@ This way the Admin-Node-Manager will only select data from these regional indexe
 
 Starting with version 2.0.0 of the solution, it is optionally possible to use local configuration files for the API lookup in addition to the API Manager. This makes it possible to:
 1. Enrich native APIs 
-  - APIs that have been exposed natively through the API-Gateway policies
-  - you can configure all information that would normally come from the API manager via the lookup file
+  - APIs that have been exposed natively through the API-Gateway policies not having a context
+  - you can configure all information that would normally be retrieved from the API-Manager via this lookup file
     - Organization, API-Name, API-Method-Name, Custom-Properties, ...
   - for example display a `/healthcheck` as `Healthcheck API` in Kibana dashboards
 2. Ignore events  
-  - You can ignore OpenTraffc events so that they are not indexed or stored in Elasticsearch.   
+  - Additionall you can ignore OpenTraffc events so that they are not indexed or stored in Elasticsearch.   
   - For example, the path: `/favicon.ico`, as this event does not add value.   
 
-Please note that the local configuration file is used before the API manager lookup. If there is a match, no lookup to the API Manager is performed.  
+Please note that the local configuration file is used before the API-Manager lookup. If there is a match, no lookup to the API-Manager is performed.  
 
 To enable the local lookup, you must perform the following steps:
 
@@ -536,7 +536,7 @@ Error reading API-Lookup file: './config/api-lookup.json'
 #### Ignore APIs/Events
 
 At this point, we intentionally refer to events and not APIs, because different events (TransactionSummy, CircuitPath, TransactionElement) are created in the OpenTraffic log for each API call. Each is processed separately by Logstash and stored using an upsert in Elasticsearch with the same Correlation-ID. Most of these events contain the path of the called API, but unfortunately not all.  
-This is especially important when ignoring events so that they are not stored in Elasticsearch. Since all events are processed individually, it must also be decided individually to ignore an event.
+This is especially important when ignoring events so that they are not stored in Elasticsearch entirely. Since all events are processed individually, it must also be decided individually to ignore an event.
 Therefore, to ignore for example the Healthcheck API entirely, the following must be configured in the lookup file:
 ```json
 {
@@ -551,7 +551,7 @@ Therefore, to ignore for example the Healthcheck API entirely, the following mus
 }
 ```
 This will ignore events based on the path (TransactionSummary & TransactionElement) and the policy name (CircuitPath). 
-You can see the result in the API builder log with the following lines:  
+You can see the result in the API-Builder log on level INFO with the following lines:  
 `Return API with apiPath: '/healthcheck', policyName: '' as to be ignored: true`   
 or:  
 `Return API with apiPath: '', policyName: 'Health Check' as to be ignored: true`