This is an automated email from the ASF dual-hosted git repository.
vatamane pushed a commit to branch fairshare-docs-3x
in repository https://gitbox.apache.org/repos/asf/couchdb-documentation.git
The following commit(s) were added to refs/heads/fairshare-docs-3x by this push:
new 2867ebc [fixup] fix a few issues found during the review
2867ebc is described below
commit 2867ebcbb6c29d704564dfd25eae949101e43cf8
Author: Nick Vatamaniuc <[email protected]>
AuthorDate: Wed Mar 17 11:00:11 2021 -0400
[fixup] fix a few issues found during the review
---
src/config/replicator.rst | 2 +-
src/replication/replicator.rst | 8 ++++----
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/src/config/replicator.rst b/src/config/replicator.rst
index 42fed1d..9e46026 100644
--- a/src/config/replicator.rst
+++ b/src/config/replicator.rst
@@ -293,7 +293,7 @@ Fair Share Replicator Share Allocation
Fair share configuration section. More shares result in a
higher chance that jobs from that db get to run. The default
value is 100, minimum is 1 and maximum is 1000. The
- configuration may be set even if the database does not exit::
+ configuration may be set even if the database does not exist::
[replicator.shares]
_replicator_db = 100
diff --git a/src/replication/replicator.rst b/src/replication/replicator.rst
index 4df9b09..05a55e6 100644
--- a/src/replication/replicator.rst
+++ b/src/replication/replicator.rst
@@ -21,10 +21,10 @@ Replicator Database
anymore. There are new replication job states and new API endpoints
``_scheduler/jobs`` and ``_scheduler/docs``.
-.. versionchanged:: 3.2.0 Fair share scheduling was
- introduced. Multiple ``_replicator`` databases get an equal chance
- (configurable) of running their jobs. Previously replication jobs
- were scheduled without any regard of their originating database.
+.. versionchanged:: 3.2.0 Fair share scheduling was introduced. Multiple
+ ``_replicator`` databases get an equal chance (configurable) of running
+ their jobs. Previously replication jobs were scheduled without any regard of
+ their originating database.
The ``_replicator`` database works like any other in CouchDB, but
documents added to it will trigger replications. Create (``PUT`` or