content-sync - SPN, pick-25

Author: thomaskoslowski

src/common/en/intro_monitor.asciidoc

@@ -2,14 +2,13 @@
 // IGNORE acknowledgement
 include::global_attr.adoc[]
 = {CMK} in monitoring
-:revdate: 2025-01-30
 :title: {CMK} in monitoring
 :description: Acknowledging problems and setting up scheduled downtimes are important tasks in monitoring with {CMK}. Read here how to perform these tasks.
 
 {related-start}
-xref:intro_finetune#[Fine-tuning the monitoring]
 xref:basics_ackn#[Acknowledging problems]
 xref:basics_downtimes#[Scheduled downtimes]
+xref:intro_finetune#[Fine-tuning the monitoring]
 {related-end}
 
 
@@ -20,7 +19,7 @@ So you have added hosts and looked at some important tools
 -- and now we are ready to start with the actual monitoring.
 After all, the whole point of {CMK} is not to be permanently occupied with the configuration, but to provide support for IT operations.
 
-It is true that the views available by default, or e.g. the [.guihint]#Overview# snap-in, already show you very precisely how many and what problems currently exist.
+It is true that the xref:glossar#view[views] available by default, or e.g. the [.guihint]#Overview# snap-in, already show you very precisely how many and what problems currently exist.
 But to model a _workflow_, i.e. 'systematic work procedures' with the monitoring, you need a bit more information on:
 
 * the acknowledgment of problems
@@ -55,15 +54,19 @@ The easiest way is to use the predefined views in the [.guihint]#Monitor > Probl
 By the way, you can almost get to these more quickly by clicking on the problem count in the [.guihint]#Overview#.
 
 You can click on the problematic host or service in the list and then, on the page with its details, perform the acknowledgment only for this individual host or service.
-However, we will stay on the list page because you have all the options here to acknowledge only one problem or several problems at once.
+However, you will stay on the page with the list because you have all the options here to acknowledge only one problem or several problems at once.
 
 It is not at all uncommon that you would like to acknowledge a number of (related) problems in a single action.
 This is easily done by clicking [.guihint]#Show checkboxes# to display a new first column in the list, which contains a checkbox in front of each row.
 The checkboxes are all unchecked as the selection is yours -- select the checkbox for each host or service you want to act on.
 
-*Important:* If you perform an action on a page with a list without checkboxes, then this action will be performed for *all* the listed entries.
+[TIP]
+====
+If you perform an action on a page with a list without checkboxes, then this action will be performed for *all* the listed entries.
+====
 
-Now click on [.guihint]#Acknowledge problems#, which will display the following panel at the top of the page:
+Now click on [.guihint]#Acknowledge problems#,
+which will display the following panel at the top of the page:
 
 ifdef::onprem[]
 .The dialog for acknowledging problems in {RE}
@@ -76,7 +79,8 @@ endif::[]
 
 Enter a comment and click [.guihint]#Acknowledge problems# -- and with the confirmation of the 'Are you sure?' question{nbsp}...
 
-image::intro_really_acknowledge.png[alt="Confirmation dialog for acknowledgment."]
+.Confirmation prompt before application
+image::intro_really_acknowledge.png[alt="Dialog for confirming acknowledgment."]
 
 … all the selected problems will be flagged as having been acknowledged.
 
@@ -85,7 +89,7 @@ Finally, a couple of tips:
 * You can also remove acknowledgments with the [.guihint]#Commands > Remove acknowledgments# menu entry.
 * Acknowledgments can run automatically.
 ifdef::onprem[]
-The [.guihint]#Expire on# option serves this purpose, but it is only available in the commercial editions.
+The [.guihint]#Expire on# option serves this purpose, but it is only available in the commercial xref:glossar#edition[editions].
 endif::[]
 ifdef::saas[]
 The [.guihint]#Expire on# option serves this purpose.