environment for the application in use and the task performed.
.P
In tiling mode windows are managed in a master and stacking area. The master
-area contains the window which currently needs most attention, whereas the
+area contains the windows which currently need most attention, whereas the
stacking area contains all other windows. In floating mode windows can be
resized and moved freely. Dialog windows are always managed floating,
-regardless of the mode selected.
+regardless of the mode applied.
.P
Windows are grouped by tags. Each window can be tagged with one or multiple
tags. Selecting certain tags displays all windows with these tags.
.B Mod1-s
Shrink master area (tiling mode only).
.TP
+.B Mod1-i
+Increase windows of master area (tiling mode only).
+.TP
+.B Mod1-d
+Decrease windows of master area (tiling mode only).
+.TP
.B Mod1-Shift-[1..n]
Apply
.RB nth
code. This keeps it fast, secure and simple.
.SH CAVEATS
The status bar may display
-.BR "broken pipe"
+.BR "EOF"
when dwm has been started by an X session manager like
.BR xdm (1),
because those close standard output before executing dwm.
.P
Java applications which use the XToolkit/XAWT backend may draw grey windows
only. The XToolkit/XAWT backend breaks ICCCM-compliance in recent JDK 1.5 and early
-JDK 1.6 versions, because it assumes a reparenting window manager. As workaround
-wether you use JDK 1.4 (which don't contains the XToolkit/XAWT backend) or you
-define the following environment variable accordingly (to use the older Motif
+JDK 1.6 versions, because it assumes a reparenting window manager. As a workaround
+you can use JDK 1.4 (which doesn't contain the XToolkit/XAWT backend) or you
+can set the following environment variable (to use the older Motif
backend instead):
.BR AWT_TOOLKIT=MToolkit .
.SH SEE ALSO