diff --git a/twander.1 b/twander.1
index 4c036d3..174f712 100644
--- a/twander.1
+++ b/twander.1
@@ -3629,10 +3629,13 @@
 .fi
 .ft \" revert
 
-Thereafter, when \fCtwander\fP runs,  the "emacs" command will
-be loaded to process any file whose name ends in ".txt" when the
-user selects that file and either double-clicks on it or presses
-"Enter".
+Thereafter, when \fCtwander\fP runs, the "emacs" command will be
+loaded to process any file whose name ends in ".txt" when the user
+selects that file and either double-clicks on it or presses "Enter".
+On Windows systems, this check is done in a case-insensitive way, so
+the association above would match files ending in, ".txt", ".TXT",
+".Txt", and so on.  On Unix-like systems, the check is case-sensitive
+and the type string must match exactly.
 
 Notice that the "handler command" can consist of pretty much anything
 that you can use in a command definition (as described in the previous
@@ -3666,11 +3669,11 @@
 .SS A Few Association Subtleties
 
 .IP \(bu 4
-The \fCASSOC\fP keyword is case-sensitive.  You must enter it entirely
-in upper-case.  However, the order of \fCASSOC\fP statements is unimportant.
-\fCtwander\fP distinguishes \fCASSOC\fP statements by their unique
-file "type" strings.  Well ...  this is true so long as you make sure
-the type strings
+The \fCASSOC\fP keyword itself is case-sensitive - you must enter it
+entirely in upper-case.  However, the order of \fCASSOC\fP statements
+is unimportant.  \fCtwander\fP distinguishes \fCASSOC\fP statements by
+their unique file "type" strings.  Well ...  this is true so long as
+you make sure the type strings
 .B are
 unique!  Suppose you put this in your Configuration File:
 
@@ -3691,12 +3694,11 @@
 unique file type.
 
 .IP \(bu 4
-The "default" association - if defined - will only be applied
-if no explicit association for a given selection is found.
-However, there is one exception.  If a selection has no matching
-association but is known to the underlying operating system to be
-.B executable,
-the default association will not be applied.  That way, you can
+The "default" association - if defined - will only be applied if no
+explicit association for a given selection is found and the file in
+question is not
+.B executable.
+That way, you can
 still double-click (or press "Enter") on executable files to run
 them without the default association getting in the way.  Of course,
 if you've explicitly defined an association for the type of executable
@@ -3786,12 +3788,12 @@
 association mechanism across the many OS and window manager variants
 in use on those platforms.
 
-But Microsoft Windows is a different matter.  All modern variants
-of these systems have consistent built-in support for association.
+But Microsoft Windows is a different matter.  All modern variants of
+these systems have consistent built-in support for association.
 \fCtwander\fP was designed to "play nice" with the underlying
-associations defined in the Windows registry.  It works very
-simply.  \fCtwander\fP associations take precedence.  If you
-define this:
+associations defined in the Windows registry.  It works very simply:
+An association defined in \fCtwander\fP will take precedence over the
+native Windows association.  Say you define this:
 
 .ft C \" courier
 .nf
@@ -3808,10 +3810,10 @@
 association for that file type (if any) will be applied.
 
 This is a very handy feature.  You may wish to temporarily or
-permanently change which Windows program is associated with
-a given file type.  Instead of having to fiddle around with
-reassociating things in Windows, you can just edit the \fCtwander\fP
-Configuration File.
+permanently change which program is associated with a given file type
+when you're running \fCtwander\fP.  Instead of having to fiddle around
+with reassociating things in Windows, you can just edit the
+\fCtwander\fP Configuration File.
 
 
 .SS Conditional Processing Statements
@@ -5043,4 +5045,4 @@
 .ft \" revert
 
 .SH DOCUMENT REVISION INFORMATION
-$Id: twander.1,v 1.136 2006/12/18 16:45:51 tundra Exp $
\ No newline at end of file
+$Id: twander.1,v 1.137 2006/12/18 20:48:55 tundra Exp $
\ No newline at end of file