ibm-wm-transition · ThorstenFiebig-SAG · Mar 16, 2021 · Mar 15, 2021 · Mar 15, 2021 · Mar 15, 2021
diff --git a/README.md b/README.md
@@ -7,7 +7,7 @@ webMethods Microgateway is a lightweight distributed proxy that gives control ov
 
 The above diagram shows microservices implementing the booking related API of the imaginary company NodeTours. The shown microservice mesh or microservice landscape consists of three services. Consumer applications access the APIs via a central API Gateway that performs the enforcement of policies. The problem here is that each microservice exposes an endpoint where no policy enforcement is done.  Moreover, considering the microservices are interacting with each other all this traffic needs to be routed through the single API Gateway. This leads to additional network latency and the API Gateway potentially becomes a bottleneck. The diagram below shows a deployment where the API Gateway is replaced with a set of Microgateways that are added to the microservices themselves. Such a "sidecar" deployment does not leave any gaps and avoids bottlenecks in the policy enforcement. 
 
-![](attachments/Microgateway_Int0.png)
+![](attachments/Microgateway_Int.png)
 
 API Gateway Integration
 ----------------------------
@@ -59,7 +59,7 @@ Microgateway supports a comprehensive collection of policies you can configure i
 	* Monitor Service Level Agreement - This policy monitors a set of run-time performance conditions like availability, average response time, fault count, maximum response time, success count and total request count for one or more specified applications. This policy can be used to configure SLAs for each API or application or combination of both. If there is a breach in any of the parameters, an event notification (Monitor event) is sent to the configured destination. In a single policy, multiple action configurations behave as AND condition. The OR condition can be achieved by configuring multiple policies. Microgateway supports API Gateway and Elasticsearch as destinations. This policy action monitors run-time performance conditions within a single Microgateway instance. 
 	* Monitor Service Performance - This policy is like the Monitor Service Level Agreement policy but enforces the run-time performance conditions at the API level. Parameters like success count, fault count, and total request count are immediate monitoring parameters and are evaluated as soon as the limit is breached. For the rest of the aggregated monitoring parameters, the evaluation happens after the configured interval. If there is a breach in any of the parameters, an event notification (Monitor event) is sent to the configured destination. Destinations supported are API Gateway and Elasticsearch. In a single policy, multiple action configurations behave as AND condition. The OR condition can be achieved by configuring multiple policies. This policy only monitors run-time performance conditions within a single Microgateway instance. 
 	* Throttling Traffic Optimization - This policy limits the number of API invocations during a specific time interval. This policy only limits the number of API invocations within a single Microgateway instance. For destinations API Gateway and Elasticsearch is supported.
-* Response Processing - Microgateway supports all the response processing policies except Invoke webMethods IS. Below policies are supported, 
+* Response Processing - Microgateway supports the below response processing policies: 
 	* Response Transformation - Microgateway supports the following parameter types for the response transformation policy. response.payload, response.headers, response.statusCode and response.statusMessage
 	* Validate API Specification - This policy validates outgoing response against schema, content-types, and HTTP headers.
 	* CORS - The Cross-Origin Resource Sharing (CORS) mechanism is used to secure cross-domain requests and data transfers between browsers and web servers. The CORS standard works by adding new HTTP headers that allow servers to describe the set of origins that are permitted to read that information. The CORS response specifications that are supported by Microgateway are Allow Origins, Max age, Allowed Methods, Allow Headers, Allow Credentials and Expose Headers. 
@@ -79,7 +79,7 @@ https://tech.forums.softwareag.com/t/microgateway-configuration/239202
 https://tech.forums.softwareag.com/t/managing-microgateways/239203
 https://tech.forums.softwareag.com/t/microgateway-integration-with-service-registry-and-api-portal/237259
 
-Please also make sure to also check out our API Gateway and have a look at the [API Gateway GitHub repository](https://github.com/SoftwareAG/webmethods-api-gateway).
+Please also make sure to check out our API Gateway and have a look at the [API Gateway GitHub repository](https://github.com/SoftwareAG/webmethods-api-gateway).
 
 -------------------------------------------
 These tools are provided as-is and without warranty or support. They do not constitute part of the Software AG product suite. Users are free to use, fork and modify them, subject to the license agreement. While Software AG welcomes contributions, we cannot guarantee to include every contribution in the master project.