summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authoryar <yar@FreeBSD.org>2006-08-12 20:30:10 +0000
committeryar <yar@FreeBSD.org>2006-08-12 20:30:10 +0000
commitcb8a8edaa802e99723d6be7be9cd59d3c9164ab4 (patch)
treeb092263ed458ca200a7be82e21af00dfb7ca5fb0
parent43cc84ae193f42ff902900e15796eee8118f131f (diff)
downloadFreeBSD-src-cb8a8edaa802e99723d6be7be9cd59d3c9164ab4.zip
FreeBSD-src-cb8a8edaa802e99723d6be7be9cd59d3c9164ab4.tar.gz
MFC the most visible bits of the corrections by Darren Pilgrim:
src/games/fortune/datfiles/fortunes 1.224 src/lib/libc/sys/kse.2 1.18 src/share/doc/papers/timecounter/timecounter.ms 1.4 src/share/man/man4/devctl.4 1.5
-rw-r--r--games/fortune/datfiles/fortunes2
-rw-r--r--lib/libc/sys/kse.22
-rw-r--r--share/doc/papers/timecounter/timecounter.ms2
-rw-r--r--share/man/man4/devctl.42
4 files changed, 4 insertions, 4 deletions
diff --git a/games/fortune/datfiles/fortunes b/games/fortune/datfiles/fortunes
index fe1779f..65d754e 100644
--- a/games/fortune/datfiles/fortunes
+++ b/games/fortune/datfiles/fortunes
@@ -5460,7 +5460,7 @@ never when standing.
Most of us just sit back and marvel at such a story; how could that terminal
know whether the poor guy was sitting or standing? Good debuggers, though,
know that there has to be a reason. Electrical theories are the easiest to
-hypothesize: was there a loose with under the carpet, or problems with static
+hypothesize: was there a loose wire under the carpet, or problems with static
electricity? But electrical problems are rarely consistently reproducible.
An alert IBMer finally noticed that the problem was in the terminal's keyboard:
the tops of two keys were switched. When the programmer was seated he was a
diff --git a/lib/libc/sys/kse.2 b/lib/libc/sys/kse.2
index d4ef2fc..2b525e2 100644
--- a/lib/libc/sys/kse.2
+++ b/lib/libc/sys/kse.2
@@ -267,7 +267,7 @@ This system call does not return unless there is an error.
.Pp
As a special case, if the last remaining KSE in the last remaining KSE group
invokes this system call, then the KSE is not destroyed;
-instead, the KSE just looses the association with its mailbox and
+instead, the KSE just loses the association with its mailbox and
.Fn kse_exit
returns normally.
This returns the process to its original, unthreaded state.
diff --git a/share/doc/papers/timecounter/timecounter.ms b/share/doc/papers/timecounter/timecounter.ms
index 96ac3d9..097ab65 100644
--- a/share/doc/papers/timecounter/timecounter.ms
+++ b/share/doc/papers/timecounter/timecounter.ms
@@ -72,7 +72,7 @@ Despite the fact that time is the physical quantity (or maybe entity
?) about which we know the least, it is at the same time [sic!] what we
can measure with the highest precision of all physical quantities.
.LP
-The current crop of atomic clocks will neither gain nor loose a
+The current crop of atomic clocks will neither gain nor lose a
second in the next couple hundred million years, provided we
stick to the preventative maintenance schedules. This is a feat
roughly in line with to knowing the circumference of the Earth
diff --git a/share/man/man4/devctl.4 b/share/man/man4/devctl.4
index 5b3bb12..cfbf71b 100644
--- a/share/man/man4/devctl.4
+++ b/share/man/man4/devctl.4
@@ -69,7 +69,7 @@ or
The read channel for this device is used to report changes to
userland in realtime.
We return one record at a time.
-If you try to read this device a character at a time, you will loose
+If you try to read this device a character at a time, you will lose
the rest of the data.
Listening programs are expected to cope.
.Pp
OpenPOWER on IntegriCloud