From 423d0c52674bfa4ec49e4ae8bce645131f657f74 Mon Sep 17 00:00:00 2001 From: Dirk Mueller Date: Mon, 16 Feb 2026 11:21:21 +0100 Subject: Fix a few typos (#2231) --- doc/developer-guidelines.sgml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'doc/developer-guidelines.sgml') diff --git a/doc/developer-guidelines.sgml b/doc/developer-guidelines.sgml index 0afa733b..8288b897 100644 --- a/doc/developer-guidelines.sgml +++ b/doc/developer-guidelines.sgml @@ -23,9 +23,9 @@ Preface - The purpose of this guidelines is to provide a reference for + The purpose of these guidelines is to provide a reference for the plugin developers and encourage the standardization of the - different kind of plugins: C, shell, perl, python, etc. + different kinds of plugins: C, shell, perl, python, etc. Monitoring Plugins Development Guidelines Copyright (C) 2000-2024 (Monitoring Plugins Team) @@ -68,7 +68,7 @@ You should always print something to STDOUT that tells if the service is working or why it is failing. Try to keep the output short - - probably less that 80 characters. Remember that you ideally would like + probably less than 80 characters. Remember that you ideally would like the entire output to appear in a pager message, which will get chopped off after a certain length. @@ -214,7 +214,7 @@ back a numerical value, or metric, which is then compared to the warning and critical thresholds. Use the get_status(double, thresholds *) function to compare the value against the thresholds. - This is the generalised format for ranges: + This is the generalized format for ranges: [@]start:end @@ -474,7 +474,7 @@ If writing to a file (perhaps recording - performance data) explicitly close close it. The plugin never + performance data) explicitly close it. The plugin never calls exit; that is caught by p1.pl, so output streams are never closed. -- cgit v1.2.3-74-g34f1