Index: /FCKeditor.Java/trunk/src/site/apt/useraction.apt
===================================================================
--- /FCKeditor.Java/trunk/src/site/apt/useraction.apt	(revision 3066)
+++ /FCKeditor.Java/trunk/src/site/apt/useraction.apt	(revision 3067)
@@ -86,4 +86,4 @@
 
   The system will respond messages to the user as they may be necessary. You can
-  localized every one of them. See {{{properties.html}Configuration}} and
-  {{{localization.html}Localization}} for more details.
+  localized every one of them. See {{{localization.html}Localization}} for more 
+  details.
Index: /FCKeditor.Java/trunk/src/site/apt/userpathbuilder.apt
===================================================================
--- /FCKeditor.Java/trunk/src/site/apt/userpathbuilder.apt	(revision 3066)
+++ /FCKeditor.Java/trunk/src/site/apt/userpathbuilder.apt	(revision 3067)
@@ -24,6 +24,6 @@
 UserPath Builder
 
-  The integration pack offers you control over every command sent by a user
-  through the File Browser.
+  The integration pack offers you control over the path under which files from the
+  File Browser are stored and browsed, additionally the URL they are reflected by.
 
   Read on to see how you can refit the system to your needs:
@@ -31,5 +31,8 @@
 * Rationale
 
-  aaa
+  Hard-coded file locations can be cumbersome under certain circumstances. You may
+  need to change the storage location on-the-fly or serve location on a user/request
+  basis. you are able to calculate the absolute storage path as well as the responded
+  URL the way you want according to the underlying {{{connector.html}Connector}}.  
 
 * The interface
@@ -45,13 +48,14 @@
 
    * {{{java-core/apidocs/net/fckeditor/requestcycle/impl/ContextPathBuilder.html}<<<net.fckeditor.requestcycle.impl.ContextPathBuilder>>>}} (default):
-     It always returns <<<false>>> for every method.
+     It always returns <<<connector.userFilesPath>>> with the current context
+     prepended and <<<connector.userFilesAbsolutePath>>> as-is.
 
    * {{{java-core/apidocs/net/fckeditor/requestcycle/impl/ServerRootPathBuilder.html}<<<net.fckeditor.requestcycle.impl.ServerRootPathBuilder>>>}}:
-     It always returns <<<true>>> for every method.
+     It always returns <<<connector.userFiles*Path>>> properties as-is.
 
    []
 
   If no existing implementation suits your needs, create your own. Implement the
-  interface and resolve the locale the way you want.
+  interface and resolve the paths the way you want.
 
 ** Declaring an implementation
@@ -65,11 +69,22 @@
 +------------------------------------------------------------------------------+
 
-* Configuration
+* Path configuration
 
-  There is one common way to easily configure a predefined or custom implementation.
+  There is one common way to easily configure paths for an existing or a custom
+  implementation: 
   Create/edit the <<<fckeditor.properties>>> and set <<<connector.userFilesPath>>>
-  and <<<connector.userFilesAbsolutePath>>> according to the semantics of the
-  chosen implementation (see {{{properties.html}Configuration}} for details).
+  and <<<connector.userFilesAbsolutePath>>> properties according to the semantics of
+  the chosen implementation (see {{{properties.html}Configuration}} for details).
+  
   If you decide to create your own implementation, you are free to use our properties
   but if you do so, access them by calling <<<PropertiesLoader#getUserFilesPath>>>
   and <<<PropertiesLoader#getUserFilesAbsolutePath>>>.
+  
+  If this still does not fit your needs, calculate the paths dynamically in the
+  getter methods and return whatever makes sense to you.
+  
+    [Attention:] Every Connector relies on a specific UserPathBuilder implementation
+                 because it serves the paths the way the connector needs them.
+                 Make sure that your implemention is accompanied by the correct
+                 Connector. E.g. using the <<<ContextPathBuilder>>> with the <<<LocalConnector>>>
+                 would result in erroneous and undefined behavior.