[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#305651: 'man xtoolplaces' typos: "existance", "searchs", "seperated" and "specifed"



Package: xtoolplaces
Version: 1.7.1-1
Severity: minor
Tags: patch


Found some typos in '/usr/share/man/man1/xtoolplaces.1.gz', see attached '.diff'.

Hope this helps...

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)

Versions of packages xtoolplaces depends on:
ii  libc6                    2.3.2.ds1-21    GNU C Library: Shared libraries an
ii  xlibs                    4.3.0.dfsg.1-12 X Keyboard Extension (XKB) configu

-- no debconf information
--- -	2005-04-21 04:10:18.980451000 -0400
+++ /tmp/xtoolplaces1.gz.9045	2005-04-21 04:10:18.974971728 -0400
@@ -137,7 +137,7 @@
 know, only \f2xconsole\f1, by Roman J. Budzianowski, sets the class
 to 'XConsole'.
 
-The more common console programs this version currently searchs for are:
+The more common console programs this version currently searches for are:
 \f2contool\f1, a console program to capture and display console output by
 Chuck Musciano; Sun's \f2shelltool\f1 and \f2cmdtool\f1 in console mode; and
 \f2xterm\f1 in console mode, by Tom Weinstein and a whole bunch of other people.
@@ -167,14 +167,14 @@
 set for WM_NAME or WM_CLASS for a particular window.
 .SH MISSING APPLICATIONS (-m)
 The '-m' option was added because some older X applications don't set
-WM_COMMAND.  Xtoolplaces uses the existance of WM_COMMAND to know what
+WM_COMMAND.  Xtoolplaces uses the existence of WM_COMMAND to know what
 windows to save information from.  The missing applications (to save despite
 not having WM_COMMAND set) file is a list of X applications, one per line.
 Missing applications files have the same three line types as addons (see
 ADDING ARGUMENTS above) except that the argument lines consist of just the name
 (as gotten from WM_NAME or WM_CLASS) of the application to save.  For example,
 we know that the programs \f2xman\f1 and \f2xyz\f1 don't set WM_COMMAND but we
-wish to save their states anyway.  The file specifed with '-m' would look like:
+wish to save their states anyway.  The file specified with '-m' would look like:
 
 .in +5
 .nf
@@ -186,7 +186,7 @@
 A program will be saved if the name in the file matches EITHER the value
 set for WM_NAME or WM_CLASS for a particular window.
 .SH SCREEN LISTS
-A list of screens is a list of numbers seperated by spaces and quoted (by
+A list of screens is a list of numbers separated by spaces and quoted (by
 single or double quotes) to prevent the shell from parsing the list (i.e. to
 save screens 1 and 3 would be -s '1 3').  The default screen to save is the
 one listed in either the environment variable \f2DISPLAY\f1 or with the '-d'

Reply to: