svn commit: r532745 - /lenya/trunk/src/modules/fckeditor/README.txt

Author: andreas
Date: Thu Apr 26 06:54:45 2007
New Revision: 532745

URL: http://svn.apache.org/viewvc?view=rev&rev=532745
Log:
Added license header, added note about keeping the website in sync

Modified:
    lenya/trunk/src/modules/fckeditor/README.txt

Modified: lenya/trunk/src/modules/fckeditor/README.txt
URL: 
http://svn.apache.org/viewvc/lenya/trunk/src/modules/fckeditor/README.txt?view=diff&rev=532745&r1=532744&r2=532745
==============================================================================
--- lenya/trunk/src/modules/fckeditor/README.txt (original)
+++ lenya/trunk/src/modules/fckeditor/README.txt Thu Apr 26 06:54:45 2007
@@ -1,3 +1,25 @@
+#
+# Copyright 1999-2006 The Apache Software Foundation
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+# ----------------------------------------------------------------------
+#
+# A note for developers: If you change this file, please keep the
+# documentation on the Lenya website in sync. Thanks!
+#
+
+
 How to configure/install:
 1. download the latest release of fckeditor from http://www.fckeditor.net/
 
@@ -5,7 +27,9 @@
    (resources directory should now contain a directory named fckeditor)
    
 3. register the module with your publication, so that the appropriate menu
-   item can be displayed: in <yourpub>/config/publication.xconf, add the line
+   item can be displayed: in the <modules> section of 
<yourpub>/config/publication.xml,
+   add the line
+   
    <module name="fckeditor"/>
 
 4. make sure you have the appropriate usecase policies in