|
|
@@ -423,7 +423,7 @@ max_network_delay
|
|
|
[HeartBeating mechanism]
|
|
|
This constant specifies in milliseconds the approximate delay that your network takes
|
|
|
to transport one packet from one machine to another. This value is to be set by system
|
|
|
-engineers and please dont change if not sure as this effects the failure detection
|
|
|
+engineers and please don't change if not sure as this effects the failure detection
|
|
|
mechanism using heartbeat.
|
|
|
|
|
|
The default is 50 milliseconds.
|
|
|
@@ -538,7 +538,7 @@ The default is off.
|
|
|
|
|
|
.PP
|
|
|
The following options are valid both for top level logging directive
|
|
|
-and they can be overriden in logger_subsys entries.
|
|
|
+and they can be overridden in logger_subsys entries.
|
|
|
|
|
|
.TP
|
|
|
to_stderr
|
|
|
@@ -610,7 +610,7 @@ The default is: info.
|
|
|
.TP
|
|
|
debug
|
|
|
This specifies whether debug output is logged for this particular logger. Also can contain
|
|
|
-value trace, what is highest level of debug informations.
|
|
|
+value trace, what is highest level of debug information.
|
|
|
|
|
|
The default is off.
|
|
|
|
|
|
@@ -645,7 +645,7 @@ See votequorum(5) for configuration options.
|
|
|
.PP
|
|
|
Within the
|
|
|
.B nodelist
|
|
|
-directive it is possible to specify specific informations about nodes in cluster. Directive
|
|
|
+directive it is possible to specify specific information about nodes in cluster. Directive
|
|
|
can contain only
|
|
|
.B node
|
|
|
sub-directive, which specifies every node that should be a member of the membership, and where
|