You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by wo...@apache.org on 2020/06/08 20:01:57 UTC
[couchdb-documentation] branch master updated: Fix a typo (#559)
This is an automated email from the ASF dual-hosted git repository.
wohali pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/couchdb-documentation.git
The following commit(s) were added to refs/heads/master by this push:
new 2222e16 Fix a typo (#559)
2222e16 is described below
commit 2222e16551723dd38b7c13e6738838bc3e0fa9fd
Author: bn4t <17...@users.noreply.github.com>
AuthorDate: Mon Jun 8 20:01:49 2020 +0000
Fix a typo (#559)
---
src/replication/intro.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/replication/intro.rst b/src/replication/intro.rst
index f5cda1a..9d2e6e6 100644
--- a/src/replication/intro.rst
+++ b/src/replication/intro.rst
@@ -32,7 +32,7 @@ Transient and Persistent Replication
There are two different ways to set up a replication. The first one that was
introduced into CouchDB leads to a replication that could be called `transient`.
Transient means that there are no documents backing up the replication. So after a
-restart of the CouchDB server the replication will disapear. Later, the
+restart of the CouchDB server the replication will disappear. Later, the
:ref:`_replicator <replicator>` database was introduced, which keeps documents
containing your replication parameters. Such a replication can be called `persistent`.
Transient replications were kept for backward compatibility. Both replications can