Fix a few typos (#2231)

3 files changed, 7 insertions, 7 deletions

diff --git a/doc/NEW_STARTERS b/doc/NEW_STARTERS
index 2c5aac88..4fda35fb 100644
--- a/doc/NEW_STARTERS
+++ b/doc/NEW_STARTERS
@@ -10,7 +10,7 @@ Need to know:
 
 1. Add member to team mailing list (https://www.monitoring-plugins.org/list/listinfo/team/)
    and to the commits mailing list (https://www.monitoring-plugins.org/list/listinfo/commits/),
-   add sourceforge email address via Privacy Options->Sender filters)
+   add sourceforge email address via Privacy Options->Sender filters
 2. Add Sourceforge access:
   - Translator: CVS access, Shell access, Release Tech (no)
   - Developer: Project role: Developer, CVS access, Shell access, Release Tech (no), Task Manager (A&T),
diff --git a/doc/RELEASING.md b/doc/RELEASING.md
index e1f3bf74..700683e7 100644
--- a/doc/RELEASING.md
+++ b/doc/RELEASING.md
@@ -9,7 +9,7 @@ using the remote name `monitoring-plugins` (rather than `origin`).
 Before you start
 ----------------
 
-- Check Github Actions status.
+- Check GitHub Actions status.
 - Update local Git repository to the current `master` tip.  For a
   maintenance release (e.g., version 2.4.1), update to the current
   `maint-2.4` tip, instead.
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 id="preface"><title>Preface</title>
-    <para>The purpose of this guidelines is to provide a reference for
+    <para>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.</para>
+    different kinds of plugins: C, shell, perl, python, etc.</para>
 
         <para>Monitoring Plugins Development Guidelines Copyright (C) 2000-2024
         (Monitoring Plugins Team)</para>
@@ -68,7 +68,7 @@
 
                 <para>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.</para>
 
@@ -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.</para>
-                <para>This is the generalised format for ranges:</para>
+                <para>This is the generalized format for ranges:</para>
 
                 <literallayout>
                 [@]start:end
@@ -474,7 +474,7 @@
                         </listitem>
 
                         <listitem><para>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 <emphasis role="strong">exit</emphasis>; that is caught by
                         p1.pl, so output streams are never closed.</para>
                         </listitem>