Fix some wording, use spellchecker ;-)

2024-12-04 22:19:57 +00:00 · 2011-06-28 13:12:06 +02:00 · 2011-06-28 13:12:06 +02:00 · bd118c65fd
commit bd118c65fd
parent 29c49f643f
6 changed files with 24 additions and 24 deletions
--- a/20
+++ b/20
@ -13,13 +13,13 @@ ngIRCd Release 18

  ngIRCd 18~rc1 (2011-06-27)
  - PAM warning message: make clear which "Password" config option is ignored.
-  - New configuration opion "MorePrivacy" to "censor" some user information.
-    When enabled, signon time and idle time is censored. Part and quit
+  - New configuration option "MorePrivacy" to "censor" some user information.
+    When enabled, signon time and idle time is left out. Part and quit
    messages are made to look the same. WHOWAS requests are silently dropped.
    All of this is useful if one wish to conceal users that access the ngircd
    servers from TOR or I2P.
  - New configuration option "ScrubCTCP" to scrub incoming CTCP commands. If
-    activated, the server silently drops incomming CTCP requests from both
+    activated, the server silently drops incoming CTCP requests from both
    other servers and from users. The server that scrubs CTCP will not forward
    the CTCP requests to other servers in the network either, which can spell
    trouble if not every oper knows about the CTCP-scrubbing. Scrubbing CTCP
@ -43,7 +43,7 @@ ngIRCd Release 18
    would be best to just use 4096 bits, but that takes minutes, even on
    current hardware ...
  - contrib/platformtest.sh: fix gcc version detection.
-  - Avoid needlesly scary 'buffer overflow' messages: When the write buffer
+  - Avoid needlessly scary 'buffer overflow' messages: When the write buffer
    space grows too large, ngIRCd has to disconnect the client to avoid
    wasting too much memory, which is logged with a scary 'write buffer
    overflow' message. Change this to a more descriptive wording.
@ -59,8 +59,8 @@ ngIRCd Release 18
    like e.g. snircd (QuakeNet) does.
  - Generate WALLOPS message on SQUIT from IRC operators; so SQUIT now behaves
    like CONNECT and DISCONNECT commands, when called by an IRC operator.
-  - Allow servers to send more commands in the first 10 secods ("burst"). This
-    helps to speed up server login and network synchronisation.
+  - Allow servers to send more commands in the first 10 seconds ("burst"). This
+    helps to speed up server login and network synchronization.
  - Add support for up to 3 targets in WHOIS queries, also allow up to one
    wildcard query from local hosts. Follows ircd 2.10 implementation rather
    than RFC 2812. At most 10 entries are returned per wildcard expansion.
@ -83,7 +83,7 @@ ngIRCd Release 18
  - Don't access possibly free'd CLIENT structure. Ooops.
  - Allow "Port = 0" in [Server] blocks. Port number 0 marks remote servers
    that try to connect to this daemon, but where this daemon never tries to
-    establis a connection on its own: only incoming connections are allowed.
+    establish a connection on its own: only incoming connections are allowed.
  - Configuration: fix 'Value of "..." is not a number!' for negative values.
  - Enable WHOIS command to return information about services.
  - Implement channel mode 'O': "IRC operators only". This channel mode is
@ -100,9 +100,9 @@ ngIRCd Release 18
    in [Global] are still accepted, so there is no functional change.
  - Fix confusing "adding to invite list" debug messages: adding entries to
    ban list produced 'invite list' debug output ...
-  - Don't throttle services and servers beeing registered.
+  - Don't throttle services and servers being registered.
  - Xcode: correctly sort files :-)
-  - Don't assert() when serching a client for an invalid server token (this is
+  - Don't assert() when searching a client for an invalid server token (this is
    only relevant when a trusted server on a server-server link sends invalid
    commands).

@ -113,7 +113,7 @@ ngIRCd Release 17.1 (2010-12-19)
  - Reset ID of outgoing server link on DNS error correctly
  - Don't log critical (or worse) messages to stderr
  - Manual page ngircd(8): add SIGNALS section
-  - Manual pages: update and simplyfy AUTHORS section
+  - Manual pages: update and simplify AUTHORS section
  - Remove "error file" when compiled with debug code enabled
  - README: Updated list of implemented commands
  - add doc/README-Interix.txt and doc/Bopm.txt to distribution tarball
--- a/2
+++ b/2
@ -134,7 +134,7 @@ Again: "end users" do not need this step!

 The configure-script is used to detect local system dependencies.

-In the perfect case, configure should recognise all needed libraries, header
+In the perfect case, configure should recognize all needed libraries, header
 files and so on. If this shouldn't work, "./configure --help" shows all
 possible options.

--- a/10
+++ b/10
@ -11,13 +11,13 @@
 ngIRCd Release 18

  ngIRCd 18~rc1 (2011-06-27)
-  - New configuration opion "MorePrivacy" to "censor" some user information.
-    When enabled, signon time and idle time is censored. Part and quit
+  - New configuration option "MorePrivacy" to "censor" some user information.
+    When enabled, signon time and idle time is left out. Part and quit
    messages are made to look the same. WHOWAS requests are silently dropped.
    All of this is useful if one wish to conceal users that access the ngircd
    servers from TOR or I2P.
  - New configuration option "ScrubCTCP" to scrub incoming CTCP commands. If
-    activated, the server silently drops incomming CTCP requests from both
+    activated, the server silently drops incoming CTCP requests from both
    other servers and from users. The server that scrubs CTCP will not forward
    the CTCP requests to other servers in the network either, which can spell
    trouble if not every oper knows about the CTCP-scrubbing. Scrubbing CTCP
@ -34,7 +34,7 @@ ngIRCd Release 18
    the [Global] section are deprecated now, but are still recognized.
    => Don't forget to check your configuration, use "ngircd --configtest"!
  - New documentation "how to contribute": doc/Contributing.txt.
-  - Avoid needlesly scary 'buffer overflow' messages: When the write buffer
+  - Avoid needlessly scary 'buffer overflow' messages: When the write buffer
    space grows too large, ngIRCd has to disconnect the client to avoid
    wasting too much memory, which is logged with a scary 'write buffer
    overflow' message. Change this to a more descriptive wording.
@ -63,7 +63,7 @@ ngIRCd Release 18
    the moment. This enhances reliability on slow links.
  - Allow "Port = 0" in [Server] blocks. Port number 0 marks remote servers
    that try to connect to this daemon, but where this daemon never tries to
-    establis a connection on its own: only incoming connections are allowed.
+    establish a connection on its own: only incoming connections are allowed.
  - Enable WHOIS command to return information about services.
  - Implement channel mode 'O': "IRC operators only". This channel mode is
    used on DALnet (bahamut), for example.
--- a/doc/sample-ngircd.conf.tmpl
+++ b/doc/sample-ngircd.conf.tmpl
@ -57,7 +57,7 @@
 	# This tells ngIRCd to write its current process ID to a file.
 	# Note that the pidfile is written AFTER chroot and switching the
 	# user ID, e.g. the directory the pidfile resides in must be
-	# writeable by the ngIRCd user and exist in the chroot directory.
+	# writable by the ngIRCd user and exist in the chroot directory.
 	;PidFile = /var/run/ngircd/ngircd.pid

 	# Ports on which the server should listen. There may be more than
@ -110,7 +110,7 @@

 [Options]
 	# Optional features and configuration options to further tweak the
-	# behavior of ngIRCd. If you wan't to get started quickly, you most
+	# behavior of ngIRCd. If you want to get started quickly, you most
 	# probably don't have to make changes here -- they are all optional.

 	# Are remote IRC operators allowed to control this server, e.g.
@ -170,7 +170,7 @@
 	# "PONG" reply.
 	;RequireAuthPing = no

-	# Silently drop all incomming CTCP requests.
+	# Silently drop all incoming CTCP requests.
 	;ScrubCTCP = no

 	# Syslog "facility" to which ngIRCd should send log messages.
--- a/man/ngircd.8.tmpl
+++ b/man/ngircd.8.tmpl
@ -26,7 +26,7 @@ there are good chances that it also supports other UNIX-based operating
 systems as well. By default, ngIRCd writes diagnostic and informational messages using
 the syslog mechanism.
 .SH OPTIONS
-The default behaviour of
+The default behavior of
 .BR ngircd
 is to read its standard configuration file (see below), to detach from the
 controlling terminal and to wait for clients.
@ -68,7 +68,7 @@ Default "message of the day" (MOTD).
 The daemon understands the following signals:
 .TP
 \fBTERM\fR
-Shut down all conections and terminate the daemon.
+Shut down all connections and terminate the daemon.
 .TP
 \fBHUP\fR
 Shut down all listening sockets, re-read the configuration file and
--- a/man/ngircd.conf.5.tmpl
+++ b/man/ngircd.conf.5.tmpl
@ -128,7 +128,7 @@ if ngIRCd is using PAM!
 \fBPidFile\fR (string)
 This tells ngIRCd to write its current process ID to a file. Note that the
 pidfile is written AFTER chroot and switching the user ID, e.g. the directory
-the pidfile resides in must be writeable by the ngIRCd user and exist in the
+the pidfile resides in must be writable by the ngIRCd user and exist in the
 chroot directory (if configured, see above).
 .TP
 \fBPorts\fR (list of numbers)
@ -192,7 +192,7 @@ If a client fails to answer a PING with a PONG within <PongTimeout>
 seconds, it will be disconnected by the server. Default: 20.
 .SH [OPTIONS]
 Optional features and configuration options to further tweak the behavior of
-ngIRCd. If you wan't to get started quickly, you most probably don't have to
+ngIRCd. If you want to get started quickly, you most probably don't have to
 make changes here -- they are all optional.
 .TP
 \fBAllowRemoteOper\fR (boolean)
@ -291,7 +291,7 @@ Default: no.
 If set to true, ngIRCd will silently drop all CTCP requests sent to it from
 both clients and servers. It will also not forward CTCP requests to any
 other servers. CTCP requests can be used to query user clients about which
-software they are using and which versions said softare is. CTCP can also be
+software they are using and which versions said software is. CTCP can also be
 used to reveal clients IP numbers. ACTION CTCP requests are not blocked,
 this means that /me commands will not be dropped, but please note that
 blocking CTCP will disable file sharing between users!