Update README.md

Author: Chris Wiechmann

README.md

@@ -15,8 +15,8 @@ One option is to use the existing API-Gateway Traffic-Monitor. That means, you u
 The glue between Elasticsearch and the API-Gateway Traffic-Monitor is an API-Builder project, that is exposing the same Traffic-Monitor API, but it is implemented using Elasticsearch instead of the OPSDB. The API-Builder is available as a ready to use Docker-Image and preconfigured in the docker-compose file.  
 Finally, the Admin-Node-Manager has to be configured to use the API-Builder API instead of the internal implementation.
 
-API-Builder status:  
-![Test Traffic-Monitor API](https://github.com/cwiechmann/apigateway-openlogging-elk/workflows/Test%20Traffic-Monitor%20API/badge.svg)
+API-Builder exposing Traffic-Monitor API:  
+![Traffic-Monitor API](https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/workflows/Test%20Traffic-Monitor%20API/badge.svg)
 
 ## Option 2 - Loginspector
 The Loginspector is a new separated user-interface with very basic set of functionilties. As part of the project the Loginspector is activated by default when using `docker-compose up -d`. If you don't wanna use it, it can be disabled by commenting out the following lines in the docker-compose.yml file: