Bug#351016: 'man dosemu' typos: "elsewere", "wether", "singlestep", "programm", etc.
Found some typos in '/usr/share/man/man1/dosemu.bin.1.gz', see attached '.diff'.
Hope this helps...
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Versions of packages dosemu depends on:
ii libc6 2.3.5-12 GNU C Library: Shared libraries an
ii libslang1 1.4.9dbs-10 The S-Lang programming library - r
ii libx11-6 6.9.0.dfsg.1-4 X Window System protocol client li
ii libxext6 6.9.0.dfsg.1-4 X Window System miscellaneous exte
ii xbase-clients 6.9.0.dfsg.1-4 miscellaneous X clients
ii xlibs 6.9.0.dfsg.1-4 X Window System client libraries m
ii xutils 6.9.0.dfsg.1-4 X Window System utility programs
Versions of packages dosemu recommends:
ii dosemu-freedos 1:0.0.b9r5a-1 FreeDOS package for DOSEMU
-- debconf information excluded
--- dosemu.bin.1 2005-08-06 09:50:51.000000000 -0400
+++ /tmp/dosemu.bin.1 2006-02-02 04:49:57.000000000 -0500
@@ -132,7 +132,7 @@
boot from floppy disk B (does not need to be a real floppy disk, see below)
-boot from hard disk C (does not need to be a real hard disk or even a
+boot from hard disk C (does not need to be a real hard disk or even an
msdos filesystem, see below)
@@ -250,7 +250,7 @@
with -H1 and then start dosdebug.
DOSEMU will then lock before jumping into the loaded bootsector waiting
for dosdebug to connect. Once connected you are in `stopped' state
-and can set breakpoints or singlestep through the bootstrap code.
+and can set breakpoints or single-step through the bootstrap code.
use stderr for output of Debugging messages
@@ -306,7 +306,7 @@
) can be used to force
returning handshake taggs via `outpipe' such that the frontend knows
-when the control command has started or finished and wether it was successful.
+when the control command has started or finished and whether it was successful.
The format of this tagging is
@@ -320,7 +320,7 @@
is 0 for success.
A tiny control terminal, which can serve as example, is the supplied
-programm. It takes just the two pipes as arguments and you may then
+program. It takes just the two pipes as arguments and you may then
enter control commands, which of them `help' is the most important one;-)
@@ -645,7 +645,7 @@
-directory may be moved elsewere.
+directory may be moved elsewhere.
For more information see