DOCS Fine-tune architecture text for DCE (#2117)

* DOCS Update architecture for DCE

* DOCS wording change

diff --git a/server/sonar-docs/src/pages/architecture/architecture-integration.md b/server/sonar-docs/src/pages/architecture/architecture-integration.md
index 60e11c1efc99d6b09ace535afd7c013b2c2c882d..1527174ee1f00eabb14d3af401ff909c9487b0c5 100644 (file)
--- a/server/sonar-docs/src/pages/architecture/architecture-integration.md
+++ b/server/sonar-docs/src/pages/architecture/architecture-integration.md
@@ -31,8 +31,8 @@ Ops use APIs to automate configuration and extract data from SonarQube.
 Ops use JMX to monitor SonarQube Server.
 
 ## About Machines and Locations
-* The SonarQube Platform cannot have more than one SonarQube Server and one SonarQube Database.
-* For optimal performance, each component (server, database, scanners) should be installed on a separate machine, and the server machine should be dedicated.
+* The SonarQube Platform cannot have more than one SonarQube Server (although the Server can be installed [as a cluster](/setup/install-cluster/)) and one SonarQube Database.
+* For optimal performance, each component (server, database, scanners) should be installed on a separate machine, and the server machine(s) should be dedicated.
 * SonarScanners scale by adding machines.
 * All machines must be time synchronized.
 * The SonarQube Server and the SonarQube Database must be located in the same network