From b5d79a8a1dc61150617e21a6bb69d2d97cadf8cc Mon Sep 17 00:00:00 2001 From: Simran Date: Tue, 23 Apr 2019 13:56:17 +0200 Subject: [PATCH] Doc - Clustering docs typos (#8827) --- .../Books/Manual/Administration/Cluster/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Documentation/Books/Manual/Administration/Cluster/README.md b/Documentation/Books/Manual/Administration/Cluster/README.md index b728075037..ba837c470d 100644 --- a/Documentation/Books/Manual/Administration/Cluster/README.md +++ b/Documentation/Books/Manual/Administration/Cluster/README.md @@ -177,15 +177,15 @@ Replacing/Removing a _DBServer_ ------------------------------- _DBServers_ are where the data of an ArangoDB cluster is stored. They -do not publish a we UI and are not meant to be accessed by any other +do not publish a web UI and are not meant to be accessed by any other entity than _Coordinators_ to perform client requests or other _DBServers_ to uphold replication and resilience. -The clean way of removing a _DBServer_ is to first releave it of all +The clean way of removing a _DBServer_ is to first relieve it of all its responsibilities for shards. This applies to _followers_ as well as _leaders_ of shards. The requirement for this operation is that no collection in any of the databases has a `relicationFactor` greater or -equal to the current number of _DBServers_ minus one. For the pupose of +equal to the current number of _DBServers_ minus one. For the purpose of cleaning out `DBServer004` for example would work as follows, when issued to any _Coordinator_ of the cluster: @@ -193,7 +193,7 @@ issued to any _Coordinator_ of the cluster: After the _DBServer_ has been cleaned out, you will find a trash bin icon to the right of the name of the _DBServer_ on any _Coordinators_' -UI. Clicking on it will remove the _DBServer_ in questiuon from the +UI. Clicking on it will remove the _DBServer_ in question from the cluster. Firing up any _DBServer_ from a clean data directory by specifying the