Fix the maximum number of primaries (#2995) (#3001)

Author: NataliaIvakina

modules/ROOT/pages/clustering/introduction.adoc

@@ -90,7 +90,7 @@ This is enough for most deployments.
 
 If you want to retain write availability with the failure of two primary members, you need <<five-primaries, five primaries>>.
 
-The maximum number of primaries you can have is *nine*, but it is not recommended having that many primaries.
+The maximum number of primaries you can have is *11*, but it is not recommended having that many primaries.
 Because the more primaries you have, the more servers you have to contact for each write operation, which can increase the latency of writes.
 
 
@@ -138,7 +138,7 @@ Use the following guidelines when deciding how many primary and secondary `syste
 * Ephemeral or frequently changing servers are good candidates to host a `system` secondary, as they may be added or removed more often.
 * A single `system` primary provides no fault tolerance for writes to the `system` database.
 Therefore, in a typical cluster deployment, it is best to start with three `system` primaries to ensure write availability.
-* Although the write volume for the `system` database is low and it can tolerate higher write latency, allowing to have more than nine `system` primaries, doing so is generally not recommended.
+* Although the write volume for the `system` database is low and it can tolerate higher write latency, allowing to have more than 11 `system` primaries, doing so is generally not recommended.
 
 
 [[database-topologies-examples]]