You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by kx...@apache.org on 2014/04/26 21:29:22 UTC
[48/50] documentation commit: updated refs/heads/import-master to
0efce91
minor spelling fixes in docs
Project: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/commit/ec387c2d
Tree: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/tree/ec387c2d
Diff: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/diff/ec387c2d
Branch: refs/heads/import-master
Commit: ec387c2d7cbed957d730f8034c9522fc77e9cc2e
Parents: 9894959
Author: Andy Wenk <an...@apache.org>
Authored: Thu Apr 24 20:37:16 2014 +0200
Committer: Andy Wenk <an...@apache.org>
Committed: Thu Apr 24 21:03:34 2014 +0200
----------------------------------------------------------------------
src/replication/intro.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/couchdb-documentation/blob/ec387c2d/src/replication/intro.rst
----------------------------------------------------------------------
diff --git a/src/replication/intro.rst b/src/replication/intro.rst
index ea4892d..ff002db 100644
--- a/src/replication/intro.rst
+++ b/src/replication/intro.rst
@@ -12,14 +12,14 @@
.. _replication/intro:
-Introduction Into Replications
-==============================
+Introduction to Replication
+===========================
One of CouchDB's strengths is the ability to synchronize two copies of the same
database. This enables users to distribute data across several nodes or
datacenters, but also to move data more closely to clients.
-Replication involves a source and a destination database, which can be one the
+Replication involves a source and a destination database, which can be on the
same or on different CouchDB instances. The aim of the replication is that at
the end of the process, all active documents on the source database are also in
the destination database and all documents that were deleted in the source