couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rnew...@apache.org
Subject [46/50] documentation commit: updated refs/heads/import-master to fe7f7bf
Date Thu, 10 Jul 2014 09:47:45 GMT
Use "single-master" technical term which inspired by RFC 3384

COUCHDB-2248


Project: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/commit/679af60c
Tree: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/tree/679af60c
Diff: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/diff/679af60c

Branch: refs/heads/import-master
Commit: 679af60c7abbac03fd223738407e485611cb2275
Parents: c0f6b01
Author: Alexander Shorin <kxepal@apache.org>
Authored: Thu May 29 01:28:18 2014 +0400
Committer: Alexander Shorin <kxepal@apache.org>
Committed: Thu May 29 01:28:18 2014 +0400

----------------------------------------------------------------------
 src/intro/consistency.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/couchdb-documentation/blob/679af60c/src/intro/consistency.rst
----------------------------------------------------------------------
diff --git a/src/intro/consistency.rst b/src/intro/consistency.rst
index 96519c3..c104ded 100644
--- a/src/intro/consistency.rst
+++ b/src/intro/consistency.rst
@@ -280,7 +280,7 @@ consistency between multiple database servers. If a client makes a write
 operation on server `A`, how do we make sure that this is consistent with
 server `B`, or `C`, or `D`? For relational databases, this is a very complex
 problem with entire books devoted to its solution. You could use
-multi-master, master/slave, partitioning, sharding, write-through caches,
+multi-master, single-master, partitioning, sharding, write-through caches,
 and all sorts of other complex techniques.
 
 


Mime
View raw message