diff options
| author | Dirkjan Ochtman <djc@apache.org> | 2013-08-19 15:10:20 +0200 |
|---|---|---|
| committer | Dirkjan Ochtman <djc@apache.org> | 2013-08-19 15:10:20 +0200 |
| commit | 86455f3fca8ad6d6860ccaead50cae868b681a08 (patch) | |
| tree | 613d7df5640b180668ae54be7de86dd9c4cea709 | |
| parent | 01f395eb73cb3294f15773bc1f066b6dced689a2 (diff) | |
| download | couchdb-86455f3fca8ad6d6860ccaead50cae868b681a08.tar.gz | |
Fix typo, consistency with vertical whitespace.
| -rw-r--r-- | share/doc/src/api/database.rst | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/share/doc/src/api/database.rst b/share/doc/src/api/database.rst index 4ef330dec..2ef4ad73f 100644 --- a/share/doc/src/api/database.rst +++ b/share/doc/src/api/database.rst @@ -998,7 +998,7 @@ should use a defined view if you want to achieve the best performance. * **Response**: JSON structure with purged documents and purge sequence * **Admin Privileges Required**: no -Occasionaly something into ends up in your database that should never have +Occasionally something into ends up in your database that should never have written to it, like a password or private key. Purge can help you here. A database purge permanently removes the references to deleted documents @@ -1009,7 +1009,6 @@ deleted documents are replicated to other databases as having been deleted. This also means that you can check the status of a document and identify that the document has been deleted. - .. note:: Don't use purge as a regular operation, it is designed to be used |