diff --git a/services/gateway/README.md b/services/gateway/README.md
index 8d69fa39d7..fb267ad16a 100644
--- a/services/gateway/README.md
+++ b/services/gateway/README.md
@@ -11,4 +11,4 @@ The `gateway` service can use a configured store via `GATEWAY_CACHE_STORE`. Poss
 
 1.  Note that in-memory stores are by nature not reboot persistent.
 2.  Though usually not necessary, a database name and a database table can be configured for event stores if the event store supports this. Generally not applicapable for stores of type `in-memory`. These settings are blank by default which means that the standard settings of the configured store applies.
-3.  The proxy service can be scaled if not using `in-memory` stores and the stores are configured identically over all instances.
+3.  The gateway service can be scaled if not using `in-memory` stores and the stores are configured identically over all instances.
diff --git a/services/graph/README.md b/services/graph/README.md
index 87e623e797..2eb8f188d3 100644
--- a/services/graph/README.md
+++ b/services/graph/README.md
@@ -27,5 +27,5 @@ The `graph` service can use a configured store via `GRAPH_STORE_TYPE`. Possible
 
 1.  Note that in-memory stores are by nature not reboot persistent.
 2.  Though usually not necessary, a database name and a database table can be configured for event stores if the event store supports this. Generally not applicapable for stores of type `in-memory`. These settings are blank by default which means that the standard settings of the configured store applies.
-3.  The proxy service can be scaled if not using `in-memory` stores and the stores are configured identically over all instances.
+3.  The graph service can be scaled if not using `in-memory` stores and the stores are configured identically over all instances.
 4.  When using `redis-sentinel`, the Redis master to use is configured via `GRAPH_CACHE_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.
diff --git a/services/ocs/README.md b/services/ocs/README.md
index 4369c17ef5..81db9da61f 100644
--- a/services/ocs/README.md
+++ b/services/ocs/README.md
@@ -15,5 +15,5 @@ The `ocs` service can use a configured store via `OCS_STORE_TYPE`. Possible stor
 
 1.  Note that in-memory stores are by nature not reboot persistent.
 2.  Though usually not necessary, a database name and a database table can be configured for event stores if the event store supports this. Generally not applicapable for stores of type `in-memory`. These settings are blank by default which means that the standard settings of the configured store applies.
-3.  The proxy service can be scaled if not using `in-memory` stores and the stores are configured identically over all instances.
+3.  The ocs service can be scaled if not using `in-memory` stores and the stores are configured identically over all instances.
 4.  When using `redis-sentinel`, the Redis master to use is configured via `OCS_CACHE_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.