From 5485c06bc1f21ecda9331a0405582c328851ad82 Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Fri, 24 Aug 2018 09:43:18 +0900 Subject: [PATCH] doc: fix internal link --- doc/repmgrd-degraded-monitoring.sgml | 6 +++--- doc/repmgrd-network-split.sgml | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/repmgrd-degraded-monitoring.sgml b/doc/repmgrd-degraded-monitoring.sgml index 923331ad..6f7e8a03 100644 --- a/doc/repmgrd-degraded-monitoring.sgml +++ b/doc/repmgrd-degraded-monitoring.sgml @@ -1,4 +1,4 @@ - + repmgrd degraded monitoring @@ -7,8 +7,8 @@ "degraded monitoring" mode In certain circumstances, repmgrd is not able to fulfill its primary mission - of monitoring the nodes' upstream server. In these cases it enters "degraded - monitoring" mode, where repmgrd remains active but is waiting for the situation + of monitoring the node's upstream server. In these cases it enters "degraded monitoring" + mode, where repmgrd remains active but is waiting for the situation to be resolved. diff --git a/doc/repmgrd-network-split.sgml b/doc/repmgrd-network-split.sgml index 1f305361..0eacadfa 100644 --- a/doc/repmgrd-network-split.sgml +++ b/doc/repmgrd-network-split.sgml @@ -40,8 +40,8 @@ In a failover situation, repmgrd will check if any servers in the same location as the current primary node are visible. If not, repmgrd will assume a network interruption and not promote any node in any - other location (it will however enter mode until - a primary becomes visible). + other location (it will however enter degraded monitoring + mode until a primary becomes visible).