Fix a few typos (#2231)

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),

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.

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>

lib/extra_opts.c

@@ -120,7 +120,7 @@ char **np_extra_opts(int *argc, char **argv, const char *plugin_name) {
 			}
 			ea1 = ea_tmp = NULL;
 		}
-	} /* lather, rince, repeat */
+	} /* lather, rinse, repeat */
 
 	if (ea_num == (size_t)*argc && extra_args == NULL) {
 		/* No extra-opts */

lib/extra_opts.h

@@ -8,7 +8,7 @@
 
 /* np_extra_opts: Process the --extra-opts arguments and create a new argument
  * array with ini-processed and argument-passed arguments together. The
- * ini-procesed arguments always come first (in the order of --extra-opts
+ * ini-processed arguments always come first (in the order of --extra-opts
  * arguments). If no --extra-opts arguments are provided or returned nothing
  * it returns **argv otherwise the new array is returned. --extra-opts are
  * always removed from **argv. The original pointers from **argv are kept in

lib/output.c

@@ -165,7 +165,7 @@ int mp_add_subcheck_to_subcheck(mp_subcheck check[static 1], mp_subcheck subchec
 void mp_add_summary(mp_check check[static 1], char *summary) { check->summary = summary; }
 
 /*
- * Generate the summary string of a mp_check object based on it's subchecks
+ * Generate the summary string of a mp_check object based on its subchecks
  */
 char *get_subcheck_summary(mp_check check) {
 	mp_subcheck_list *subchecks = check.subchecks;
@@ -243,7 +243,7 @@ mp_state_enum mp_compute_check_state(const mp_check check) {
 }
 
 /*
- * Generate the result state of a mp_check object based on it's own state and it's subchecks states
+ * Generate the result state of a mp_check object based on its own state and its subchecks states
  */
 mp_state_enum mp_eval_check_default(const mp_check check) {
 	assert(check.subchecks != NULL); // a mp_check without subchecks is invalid, die here

lib/parse_ini.c

@@ -173,7 +173,7 @@ static bool read_defaults(FILE *defaults_file, const char *stanza, np_arg_list *
 			continue;
 		}
 		switch (current_char) {
-			/* globble up comment lines */
+			/* gobble up comment lines */
 		case ';':
 		case '#':
 			GOBBLE_TO(defaults_file, current_char, '\n');

lib/perfdata.c

@@ -37,7 +37,7 @@ char *pd_to_string(mp_perfdata pd) {
 	if (strchr(pd.label, '\'') == NULL) {
 		asprintf(&result, "'%s'=", pd.label);
 	} else {
-		// we have a illegal single quote in the string
+		// we have an illegal single quote in the string
 		// replace it silently instead of complaining
 		for (char *ptr = pd.label; *ptr == '\0'; ptr++) {
 			if (*ptr == '\'') {

lib/states.h

@@ -45,7 +45,7 @@ static inline mp_state_enum max_state(mp_state_enum a, mp_state_enum b) {
  * STATE_OK < STATE_DEPENDENT < STATE_UNKNOWN < STATE_WARNING < STATE_CRITICAL
  *
  * The main difference between max_state_alt and max_state it that it doesn't
- * allow setting a default to UNKNOWN. It will instead prioritixe any valid
+ * allow setting a default to UNKNOWN. It will instead prioritize any valid
  * non-OK state.
  ****************************************************************************/
 

tools/distclean

@@ -37,7 +37,7 @@ find . -type f -name Makefile.in -print| xargs rm -f
 rm -f aclocal.m4 compile config.guess config.h.in config.sub configure depcomp
 rm -f m4/Makefile.am
 
-echo "$0: Removing miscelanious files..."
+echo "$0: Removing miscellaneous files..."
 rm -f po/*.gmo po/stamp-po
 rm -f lib/tests/*.Po
 rm -f doc/developer-guidelines.html

tools/p1.pl

@@ -30,7 +30,7 @@ use IO::File;
 
 sub TIEHANDLE {
 	my ($class, $fn) = @_;
-	my $handle = new IO::File "> $fn" or die "Cannot open embedded work filei $!\n";
+	my $handle = new IO::File "> $fn" or die "Cannot open embedded work file $!\n";
 	bless { FH => $handle, Value => 0}, $class;
 }