From 53e9061dcf4d57980762dcc4da50b476dc9f89cf Mon Sep 17 00:00:00 2001 From: Michael Friedrich Date: Fri, 21 Aug 2015 12:23:14 +0200 Subject: [PATCH] Doc: Fix markdown formatting for global zones fixes #9977 --- doc/12-distributed-monitoring-ha.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/doc/12-distributed-monitoring-ha.md b/doc/12-distributed-monitoring-ha.md index fcc6662a9..5a6c8d81d 100644 --- a/doc/12-distributed-monitoring-ha.md +++ b/doc/12-distributed-monitoring-ha.md @@ -340,7 +340,7 @@ on your configuration master unique. > Only put templates, groups, etc into this zone. DO NOT add checkable objects such as > hosts or services here. If they are checked by all instances globally, this will lead > into duplicated check results and unclear state history. Not easy to troubleshoot too - -> you've been warned. +> you have been warned. That is not necessary by defining a global zone shipping all those templates. By setting `global = true` you ensure that this zone serving common configuration templates will be @@ -365,12 +365,10 @@ your zone configuration visible to all nodes. global = true } -> **Note** -> -> If the remote node does not have this zone configured, it will ignore the configuration -> update, if it accepts synchronized configuration. +If the remote node does not have this zone configured, it will ignore the configuration +update, if it accepts synchronized configuration. -If you don't require any global configuration, skip this setting. +If you do not require any global configuration, skip this setting. ### Zone Configuration Synchronisation Permissions