Index: /FCKeditor.Java/trunk/src/site/apt/connector.apt
===================================================================
--- /FCKeditor.Java/trunk/src/site/apt/connector.apt	(revision 3198)
+++ /FCKeditor.Java/trunk/src/site/apt/connector.apt	(revision 3199)
@@ -46,5 +46,5 @@
     You have to choose an implementation, either an existing or a custom one.
 
-  Existing, ready-to-go implementations:
+  Ready-to-go implementations:
 
    * {{{java-core/apidocs/net/fckeditor/connector/impl/AbstractLocalFileSystemConnector.html}<<<net.fckeditor.connector.impl.AbstractLocalFileSystemConnector>>>}} (abstract class):
@@ -82,2 +82,5 @@
   in erroneous and undefined behavior. See {{{userpathbuilder.html}UserPathBuilder}}
   for more details.
+  
+    [Keep in mind:] If you write your own Connector implementation, it could be necessary to write
+                    your own listener to resolve the files managed by the File Browser inside your web-app.   
Index: /FCKeditor.Java/trunk/src/site/apt/userpathbuilder.apt
===================================================================
--- /FCKeditor.Java/trunk/src/site/apt/userpathbuilder.apt	(revision 3198)
+++ /FCKeditor.Java/trunk/src/site/apt/userpathbuilder.apt	(revision 3199)
@@ -33,5 +33,5 @@
   Hard-coded storage paths can be cumbersome under certain circumstances. You may
   need to change the storage path on-the-fly or serve paths on a user/request
-  basis. you are able to calculate the absolute storage path as well as the responded
+  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}}.
 
@@ -45,5 +45,5 @@
   You have to choose an implementation, either an existing or a custom one.
 
-  Existing, ready-to-go implementations:
+  Ready-to-go implementations:
 
    * {{{java-core/apidocs/net/fckeditor/requestcycle/impl/ContextPathBuilder.html}<<<net.fckeditor.requestcycle.impl.ContextPathBuilder>>>}} (default):