--- rxvt-unicode/doc/rxvt.1.pod	2006/01/29 20:51:27	1.107
+++ rxvt-unicode/doc/rxvt.1.pod	2006/01/29 22:27:04	1.109
@@ -97,7 +97,7 @@
 
 =item B<-depth> I<bitdepth>
 
-Compile I<frills>: Attempt to find a visual with the given bit depth;
+Compile I<xft>: Attempt to find a visual with the given bit depth;
 resource B<depth>.
 
 =item B<-geometry> I<geom>
@@ -514,7 +514,7 @@
 
 =item B<depth:> I<bitdepth>
 
-Compile I<frills>: Attempt to find a visual with the given bit depth;
+Compile I<xft>: Attempt to find a visual with the given bit depth;
 option B<-depth>.
 
 =item B<geometry:> I<geom>
@@ -1342,13 +1342,15 @@
 a number 0-15, as a convenient shorthand to reference the colour name of
 color0-color15.
 
-If Xft support has been compiled in and as long as Xft/Xrender don't get
-their act together, rxvt-unicode will support C<#ARGB>, C<#AARRGGBB>
+If Xft support has been compiled in and as long as Xft/Xrender/X don't get
+their act together, rxvt-unicode will support C<rgba:rrrr/gggg/bbbb/aaaa>
+(recommended, but B<MUST> have 4 digits/component), C<#ARGB>, C<#AARRGGBB>
 and C<#AAAARRRRGGGGBBBB> colour specifications, in addition to the ones
 provided by X, where the additional A component specifies alpha (opacity)
 values (0 is completely transparent and the maximum is opaque). You
-probably need to specify B<"-depth 32">, too, as X is far from just
-supporting ARGB visuals out of the box.
+probably need to specify B<"-depth 32">, too, and have the luck that your
+X-server uses ARGB pixel layout, as X is far from just supporting ARGB
+visuals out of the box, and rxvt-unicode just fudges around.
 
 Note that B<-rv> (B<"reverseVideo: True">) simulates reverse video by
 always swapping the foreground/background colours. This is in contrast to