svn commit: r795392 - /websites/staging/rave/trunk/content/rave/documentation/rave-extensions.html

[bu...@apache.org]

Author: buildbot
Date: Tue Sep  6 15:49:54 2011
New Revision: 795392

Log:
Staging update by buildbot

Modified:
    websites/staging/rave/trunk/content/rave/documentation/rave-extensions.html

Modified: websites/staging/rave/trunk/content/rave/documentation/rave-extensions.html
==============================================================================
--- websites/staging/rave/trunk/content/rave/documentation/rave-extensions.html (original)
+++ websites/staging/rave/trunk/content/rave/documentation/rave-extensions.html Tue Sep  6 15:49:54 2011
@@ -84,7 +84,7 @@ Extension developers will be able to use
 
 <h2 id="best_practices">Best Practices</h2>
 <ul>
-<li>Add new javascript functions to new file or copy existing functions to new file and customize them and their imports so that changes in rave libraries can come to your project.</li>
+<li>Add new javascript functions to new file or copy existing functions to new file and customize them and change imports based on your need. Reason is, changes/fixes in rave libraries should come to your project.</li>
 <li>If you are are customizing css or adding new css methods add new files so that changes in default rave css files will come to your portal</li>
 <li>Report any bug or issue to Rave Jira <a href="https://issues.apache.org/jira/browse/RAVE">Rave JIRA</a> </li>
 </ul>