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 2019/09/27 15:01:06 UTC
[couchdb-documentation] branch master updated: Fix typo (#446)
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 443b135 Fix typo (#446)
443b135 is described below
commit 443b1356b94f09c09bf62224118d0dbfb8ea1bff
Author: Travis Paul <Tr...@visPaul.me>
AuthorDate: Fri Sep 27 08:01:01 2019 -0700
Fix typo (#446)
* Remove duplicate
* Replace "duplicate" with "multiple" regarding autogenerated UUIDs
---
src/best-practices/documents.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/best-practices/documents.rst b/src/best-practices/documents.rst
index 9cc181c..0af2913 100644
--- a/src/best-practices/documents.rst
+++ b/src/best-practices/documents.rst
@@ -29,10 +29,10 @@ a few reasons:
- If for any reason you miss the ``200 OK`` reply from CouchDB, and storing the
document is attempted again, you would end up with the same document content
- stored under duplicate ``_id``\ s. This could easily happen with intermediary
+ stored under multiple ``_id``\ s. This could easily happen with intermediary
proxies and cache systems that may not inform developers that the failed
transaction is being retried.
-- ``_id``\ s are are the only unique enforced value within CouchDB so you might
+- ``_id``\ s are the only unique enforced value within CouchDB so you might
as well make use of this. CouchDB stores its documents in a B+ tree. Each
additional or updated document is stored as a leaf node, and may require
re-writing intermediary and parent nodes. You may be able to take advantage of