INN commit: branches/2.6 (3 files)

INN Commit rra at isc.org
Sat Nov 21 09:04:35 UTC 2020


    Date: Saturday, November 21, 2020 @ 01:04:34
  Author: iulius
Revision: 10409

Typo fixes

Modified:
  branches/2.6/Makefile.global.in
  branches/2.6/contrib/innconfcheck
  branches/2.6/doc/pod/hacking.pod

----------------------+
 Makefile.global.in   |    2 +-
 contrib/innconfcheck |    6 +++---
 doc/pod/hacking.pod  |    2 +-
 3 files changed, 5 insertions(+), 5 deletions(-)

Modified: Makefile.global.in
===================================================================
--- Makefile.global.in	2020-11-21 08:49:31 UTC (rev 10408)
+++ Makefile.global.in	2020-11-21 09:04:34 UTC (rev 10409)
@@ -356,7 +356,7 @@
 CP_MAN		= $(INSTALL) $(OWNER) -m 0444
 
 ##  Some additional definitions needed by some versions of make, to ensure a
-##  consistant set of variables are available.
+##  consistent set of variables are available.
 
 SHELL		= @SHELL@
 

Modified: contrib/innconfcheck
===================================================================
--- contrib/innconfcheck	2020-11-21 08:49:31 UTC (rev 10408)
+++ contrib/innconfcheck	2020-11-21 09:04:34 UTC (rev 10409)
@@ -50,7 +50,7 @@
 # INNCONFPOD=/usr/local/src/inn-2.3.0/doc/pod/inn.conf.pod
 INNCONFPOD=/usr/local/news/man/man5/inn.conf.pod
 
-# NROFF should be set to an approbate program for formating the man page
+# NROFF should be set to an approbate program for formatting the man page
 # this could be the vendor provided nroff, the FSF's groff (which could be
 # used for producing PostScript output) or Earl Hood's man2html from
 # http://www.oac.uci.edu/indiv/ehood/man2html.html
@@ -70,7 +70,7 @@
 # approach is that if the format of the inn.conf man page ever changes
 # assumptions about the format that this script makes will probably break.
 # Presently, the base/orginal format of the inn.conf man page is in perl
-# POD documentation.  The formating of this file is less likely to change
+# POD documentation.  The formatting of this file is less likely to change
 # in the future and is a cleaner format for automated editing.  However, 
 # their is some disadvantages to using this file.  First disadvantage, 
 # the POD file is not installed by INN 2.3.0 by default (see INNCONFPOD 
@@ -98,7 +98,7 @@
 #   s#^.Ip "\fIvarifycancels\f$" 4#.Ip "\verifycancels: false\f$" 4#
 # once piped to sed, this expression will replace the man page item to
 # include the setting from the inn.conf file.  The nroff and pager
-# applications then polish the script off to provide a documented formated
+# applications then polish the script off to provide a documented formatted
 # in a way that is easier to find incorrect setting withen.
 
 if [ $EDITPOD -eq 0 ] ; then

Modified: doc/pod/hacking.pod
===================================================================
--- doc/pod/hacking.pod	2020-11-21 08:49:31 UTC (rev 10408)
+++ doc/pod/hacking.pod	2020-11-21 09:04:34 UTC (rev 10409)
@@ -614,7 +614,7 @@
 arguments to the called function, misidentifies some macro calls as being
 type declarations, and fouls up long but simple case statements).  It
 would be excellent if someday we could just run all of INN's code through
-B<indent> routinely to enforce a consistant coding style, but B<indent>
+B<indent> routinely to enforce a consistent coding style, but B<indent>
 isn't quite ready for that.
 
 For users of emacs cc-mode, use the "bsd" style but with:



More information about the inn-committers mailing list