adjust docs

ARCHITECTURE.md

@@ -15,13 +15,9 @@ Example usage:
 ssh -p 5222 <machine-ID>@<mgmt-host>
 ```
 
-First, it fetches the corresponding IPMI data and SSH public key(s) from `metal-api` for the requested machine as well as the address of the management service that is responsible for all machines of the requested machines partition. It then opens a connection to that management service and copies all stdin, stdout and stderr traffic to both directions.
+First, it fetches the corresponding IPMI data and SSH public key(s) from `metal-api` for the requested machine as well as the address of the management servers that are responsible for all machines of the requested machines partition. It then opens a connection to one of these management servers and copies all stdin, stdout and stderr traffic into both directions.
 
-The second component type is the management service mentioned above. There is one management service per partition running on the metal-control-plane (ReplicaSet), which is connected (and load-balances) to all management servers within that partition.
-It therefore forwards the `metal-console` traffic to one of its management servers by connecting to the third component, the `bmc-reverse-proxy`, which is running on each management server.
-
-The `bmc-reverse-proxy` is a simple Nginx server that provides a secured (client certificate) pipe to the last component, the `bmc-proxy`,
-which finally opens a connection to the requested machine.
+The connection is accepted by a the third component, the `bmc-reverse-proxy`, which is a simple Nginx running on each management server. It provides a secured (client certificate) pipe to the last component, the `bmc-proxy`, which finally opens a connection to the requested machine.
 
 ## Traffic sequence