Use text from main repo PR

arangodb · Simran-B · Jul 23, 2019 · Jul 18, 2019 · Jul 22, 2019 · Jul 22, 2019
commit 646e4a7907c57ea066c9bfa6c3a2c154a9e3b123
diff --git a/3.5/data-modeling-collections-database-methods.md b/3.5/data-modeling-collections-database-methods.md
@@ -170,22 +170,14 @@ to the [naming conventions](data-modeling-naming-conventions.html).
   dramatically when using joins in AQL at the costs of reduced write
   performance on these collections.
    
-- *minReplicationFactor* (optional, default is 1): in a cluster, this
-  attribute determines how many desired copies of each shard are kept
-  on different DBServers. The value 1 means that only one copy (no
-  synchronous replication) is kept. A value of k means that desired
-  k-1 replicas are kept.
-
-  If in a failover scenario a shard of a collection has less than
-  minReplicationFactor many insync followers it will go into "read-only"
-  mode and will reject writes until enough followers are insync again.
-
-  In more detail:
-  Having `minReplicationFactor == 1` means as soon as a "master-copy" is
-  available of the data writes are allowed.
-
-  Having `minReplicationFactor > 1` requires additional insync copies on
-  follower servers to allow writes.
+- *minReplicationFactor* (optional, default is 1):  in a cluster, this
+  attribute determines how many copies of each shard are required
+  to be in sync on the different DBServers. If we have less then these
+  many copies in the cluster a shard will refuse to write. The
+  minReplicationFactor can not be larger than replicationFactor.
+  Please note: during server failures this might lead to writes
+  not being possible until the failover is sorted out and might cause
+  write slow downs in trade of data durability.
 
 - *distributeShardsLike*: distribute the shards of this collection
   cloning the shard distribution of another. If this value is set,