svn commit: r921552 - in /websites/staging/openoffice/trunk/content: ./ developer-faqs.html

[bu...@apache.org]

Author: buildbot
Date: Sun Sep  7 21:05:28 2014
New Revision: 921552

Log:
Staging update by buildbot for openoffice

Modified:
    websites/staging/openoffice/trunk/content/   (props changed)
    websites/staging/openoffice/trunk/content/developer-faqs.html

Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Sep  7 21:05:28 2014
@@ -1 +1 @@
-1623229
+1623230

Modified: websites/staging/openoffice/trunk/content/developer-faqs.html
==============================================================================
--- websites/staging/openoffice/trunk/content/developer-faqs.html (original)
+++ websites/staging/openoffice/trunk/content/developer-faqs.html Sun Sep  7 21:05:28 2014
@@ -155,7 +155,8 @@ e.g. issue 1234 is to use a #i1234# at t
 <h2 id="wzxhzdk6where-can-i-find-out-more-about-code-developmentwzxhzdk7"><a name="where_can_i_find_out_more_about_code_development">Where can I find out more about code development?</a></h2>
 <p>You might want to start by reviewing the legacy information on <a href="http://www.openoffice.org/development/">OpenOffice.org
 development</a>. Or, take
-a look at information posted on the <a href="http://wiki.openoffice.org/wiki/Main_Page">Apache OpenOffice wiki</a>.</p>
+a look at information posted on the <a href="http://wiki.openoffice.org/wiki/Main_Page">Apache OpenOffice wiki</a>
+under <em>Documentation - For Developers</em>.</p>
 <p>Of course, you will need the <a href="http://openoffice.apache.org/source.html">source code</a> to do anything.</p>
 <p>You don't have to be an actual committer to submit code. You can submit patches through
 the Apache OpenOffice Bugzilla issue reporting system. You simply need to file an issue