From fa1801cbc4548f282ea7967b8fbaf37d95fe39fe Mon Sep 17 00:00:00 2001 From: Chun-Hung Tseng Date: Tue, 9 Apr 2024 15:40:52 +0200 Subject: [PATCH] documentation: improve logging.md Signed-off-by: Chun-Hung Tseng --- Documentation/contributor-guide/logging.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/contributor-guide/logging.md b/Documentation/contributor-guide/logging.md index 9eb903201..6798ebf6e 100644 --- a/Documentation/contributor-guide/logging.md +++ b/Documentation/contributor-guide/logging.md @@ -7,14 +7,14 @@ etcd uses the [zap][zap] library for logging application output categorized into * Send a normal message to a remote peer * Write a log entry to disk -* Info: Normal, working log information, everything is fine, but helpful notices for auditing or common operations. Should rather not be logged more frequently than once per a few seconds in normal server's operation. +* Info: Normal, working log information, everything is fine, but helpful notices for auditing or common operations. Should rather not be logged more frequently than once per a few seconds in a normal server's operation. * Examples: * Startup configuration - * Start to do snapshot + * Start to do a snapshot * Warning: (Hopefully) Temporary conditions that may cause errors, but may work fine. A replica disappearing (that may reconnect) is a warning. * Examples: - * Failure to send raft message to a remote peer + * Failure to send a raft message to a remote peer * Failure to receive heartbeat message within the configured election timeout * Error: Data has been lost, a request has failed for a bad reason, or a required resource has been lost.