Fix assorted typos in manpages

This commit is contained in:
Pavel Labath 2011-04-02 00:29:45 +02:00 committed by Mathias Gumz
parent 906166f42d
commit 40f8c35084
5 changed files with 18 additions and 18 deletions

View file

@ -18,7 +18,7 @@ SYNTAX
------
Variable parameters are shown in emphasis: 'argument'
All other characters shown are required verbatim. Whitespce is only required to
All other characters shown are required verbatim. Whitespace is only required to
delimit words, but it is fine to add more whitespace.
DESCRIPTION
@ -71,7 +71,7 @@ Where the 'pattern' item is optional. If specified, this pattern must match for
the group to take effect. It is common to use non-window-specific patterns such
as *(workspace)* here. See *CLIENT PATTERNS* for more details.
This is followed by any number of *[app]* lines. These have a simiar format to
This is followed by any number of *[app]* lines. These have a similar format to
the *[app]* section detailed above in *APP SECTIONS*, but do not contain any
settings and do not have an associated *[end]* line.

View file

@ -93,7 +93,7 @@ button, eg. '1' is the primary button, '4'/'5' are the wheel buttons):
The mouse button 'N' is clicked (pressed and released with no
movement in between)
*MoveN*;;
The mouse button 'N' is currently held, the binded action is triggered
The mouse button 'N' is currently held, the bound action is triggered
as often as the mouse moves.
@ -201,7 +201,8 @@ These commands ordinarily affect only the currently focused window. The
*MaximizeHorizontal* / *MaximizeVertical*::
Maximize the current window in one direction only, leaving the other
dimension unchanged.
*Fullscreen*
*Fullscreen*::
Resize the window's content to fit the whole screen, without
any window decoration.
@ -237,8 +238,7 @@ These commands ordinarily affect only the currently focused window. The
*SetDecor* 'decor'::
Sets which window decorations will be shown. 'decor' has the same format
as the `[Deco]' parameter in the apps file. See `man fluxbox' section
APPLICATIONS for more info.
as the `[Deco]' parameter in the apps file. See 'fluxbox-apps(5)' for more info.
*ToggleDecor*::
Toggles the presence of the window decorations (title bar, window
@ -579,11 +579,11 @@ To check other windows besides the currently focused one, see the *Every* and
*Some* conditions below.
*Some* 'condition'::
Retuns *true* if any window on any workspace (not just the currently
Returns *true* if any window on any workspace (not just the currently
focused one) matches the 'condition'.
*Every* 'condition'::
Retuns *true* if every window on every workspace (not just the
Returns *true* if every window on every workspace (not just the
current one) matches the 'condition'.
*Not* 'condition'::

View file

@ -22,7 +22,7 @@ SYNTAX
------
Variable parameters are shown in emphasis: 'argument'
All other characters shown are required verbatim. Whitespce is only required to
All other characters shown are required verbatim. Whitespace is only required to
delimit words, but it is fine to add more whitespace.
DESCRIPTION
@ -61,7 +61,7 @@ every tag must be on its own line.
There are up to four fields in a menu line. They are of the form:::
['tag'] ('label') {'command'} <'icon'>
The <'icon'> field is always optional when show below. If specified, the 'icon'
The <'icon'> field is always optional when shown below. If specified, the 'icon'
will be scaled down and displayed in the menu alongside the text label of the
item. It must be in .xpm or .png format.
@ -127,7 +127,7 @@ Applications
Inserts a command item into the menu. When you select the menu item from the
menu, fluxbox runs 'command...' in your *$SHELL* (or /bin/sh if $SHELL is not
set). You can use this to launch applications, run shell scripts, etc. Since
all arguments are passed verbatim to te shell, you can use environment
all arguments are passed verbatim to the shell, you can use environment
variables, pipes, or anything else the shell can do. Note that processes only
see environment variables that were set before fluxbox started (such as in
~/.fluxbox/startup).

View file

@ -41,10 +41,10 @@ A style is made up of a few major components which then have their own
sub-directives. The major components are as follows:
The 'window.\*' directives control the appearance of the window frames,
window.tab.* controls the appearance of the window tabs, 'menu.\*' controls
'window.tab.\*' controls the appearance of the window tabs, 'menu.\*' controls
the appearance of the popup menu that you see when you right click on the
desktop. 'toolbar.\*' is the bar you will see at the top or bottom of your
screen. Finally the 'slit.\*' has options you can use to customize the
screen. Finally the 'slit.*' has options you can use to customize the
appearance of the slit. However if you don't set the slit directives
specifically, the slit's appearance is controlled by the toolbar
directives instead.
@ -52,7 +52,7 @@ directives instead.
To understand how the style mechanism works, it is nice to know a little about
how X11 resources work. X11 resources consist of a key and a value. The key is
constructed of several smaller keys (sometimes referred to as children),
delimited by a period (.). Keys may also contain an asterisk (\*)
delimited by a period (.). Keys may also contain an asterisk (*)
to serve as a wildcard, which means that one line of text will match
several keys. This is useful for styles that are based on one or two
colors.
@ -119,7 +119,7 @@ you set the font resource for all keys to this font name all at once (For
information about the fonts installed on your system, you can use a
program like xfontsel(1), gtkfontsel, or xlsfonts(1).)
In the last example you will notice the wildcard (\*) before font. In a Fluxbox
In the last example you will notice the wildcard (*) before font. In a Fluxbox
style you can set a value with a wildcard. The example means that every font
in the style will be what is specified. You can do this with any
component/value. For example if you wanted all of the text to be one color you
@ -222,7 +222,7 @@ FULL COMPONENT LIST
Here is the exhaustive component list for fluxbox(1) styles. Each one is listed
with their type of value required. Comments in a style file are preceded
with an exclamation point (!) which we also use here so that these can be
pasted into a new theme.cfg to be customized appropiately. Please note that
pasted into a new theme.cfg to be customized appropriately. Please note that
in order to keep styles consistent it is often the practice of stylists
to provide all of the theme-items in their style file even if they are not
used. This allows the user the ease of changing different components.
@ -473,7 +473,7 @@ These are the color formats for styles:
#000000 (Hexadecimal)
rgb:<0-255>/<0-255>/<0-255>
See /usr/share/X11/rgb.txt for an explaination.
See /usr/share/X11/rgb.txt for an explanation.
AUTHORS
-------

View file

@ -529,7 +529,7 @@ workspaces, windows, and add/remove/rename workspaces.
Pops up a dialog to enter a new name for the current workspace.
*Remove Last*:::
Remove the last workspace in the list. Any windows curretly open there will
Remove the last workspace in the list. Any windows currently open there will
be sent to the next-to-last workspace.
TOOLBAR