Modify scenario 9 readme
@@ -171,7 +171,7 @@ Hence, in this swagger definition endpoint has been referred in resource level.
```
- Invoking reviews endpoint
```
- curl -X GET "https://<external IP of LB service>:9095/store/v1.0.0/review/151" -H "accept: application/json" -H "Authorization:Bearer $TOKEN" -k
+ curl -X GET "https://<external IP of LB service>:9095/storetep/v1.0.0/review/151" -H "accept: application/json" -H "Authorization:Bearer $TOKEN" -k
```
- Once you execute the above command, it will call to the managed API (online-store-api), which then call its endpoint("review-ep" service) available in the cluster. If the request is success, you would be able to see the response as below.
```
@@ -180,7 +180,7 @@ Hence, in this swagger definition endpoint has been referred in resource level.
- Invoking inventory endpoint
```
- curl -X GET "https://<external IP of LB service>:9095/store/v1.0.0/inventory/151" -H "accept: application/json" -H "Authorization:Bearer $TOKEN" -k
+ curl -X GET "https://<external IP of LB service>:9095/storetep/v1.0.0/inventory/151" -H "accept: application/json" -H "Authorization:Bearer $TOKEN" -k
```
- Once you execute the above command, it will call to the managed API (online-store-api), which then call its endpoint("inventory-ep" service) available in the cluster. If the request is success, you would be able to see the response as below.
```
