Updated agent names in Readme

Signed-off-by: selbin <[email protected]>

README.md

@@ -5,23 +5,23 @@ You can always change this to your ledger of choice by updating *GENESIS_URL* en
 1. Clone repository
 2. Create a docker network `docker network create aries-playground-nw` (If not already created)
 3. Run `docker-compose up`, it will serve:
-    * agent1.localhost (Agent1 service endpoint)
-    * agent1.swagger.localhost (Administration API(s) with swagger UI)
-    * agent2.localhost (Agent2 service endpoint)
-    * agent2.swagger.localhost (Administration API(s) with swagger UI)
-    * agent3.localhost (Agent3 service endpoint)
-    * agent3.swagger.localhost (Administration API(s) with swagger UI)
-    * agent1.webhook (For capturing webhook events)
-    * agent2.webhook (For capturing webhook events)
-    * agent3.webhook (For capturing webhook events)
+    * test-center.localhost (Agent1 service endpoint)
+    * test-center.swagger.localhost (Administration API(s) with swagger UI)
+    * data4life-user.localhost (Agent2 service endpoint)
+    * data4life-user.swagger.localhost (Administration API(s) with swagger UI)
+    * travel-company.localhost (Agent3 service endpoint)
+    * travel-company.swagger.localhost (Administration API(s) with swagger UI)
+    * test-center.webhook (For capturing webhook events)
+    * data4life-user.webhook (For capturing webhook events)
+    * travel-company.webhook (For capturing webhook events)
 
 #### Webhooks
 
 A webhook interceptor is provided to debug the webhook events. It can be accessed by tailing demo.log file.
 
-1. `docker exec -it agent1.webhook tail -f demo.log` - For viewing webhook events for agent1
-2. `docker exec -it agent2.webhook tail -f demo.log` - For viewing webhook events for agent2
-3. `docker exec -it agent3.webhook tail -f demo.log` - For viewing webhook events for agent3
+1. `docker exec -it test-center.webhook tail -f demo.log` - For viewing webhook events for agent1
+2. `docker exec -it data4life-user.webhook tail -f demo.log` - For viewing webhook events for agent2
+3. `docker exec -it travel-company.webhook tail -f demo.log` - For viewing webhook events for agent3
 
 Please refer the [user guide executing on the credential issue and verification](https://github.com/decentralised-dataexchange/aries-playground/blob/master/credential-issue-and-verification-api-user-guide.md) for the above reference system.