svn commit: r999754 - in /websites/staging/openoffice/trunk/content: ./ orientation/intro-development.html

[bu...@apache.org]

Author: buildbot
Date: Fri Oct 21 16:06:36 2016
New Revision: 999754

Log:
Staging update by buildbot for openoffice

Modified:
    websites/staging/openoffice/trunk/content/   (props changed)
    websites/staging/openoffice/trunk/content/orientation/intro-development.html

Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Oct 21 16:06:36 2016
@@ -1 +1 @@
-1766057
+1766060

Modified: websites/staging/openoffice/trunk/content/orientation/intro-development.html
==============================================================================
--- websites/staging/openoffice/trunk/content/orientation/intro-development.html (original)
+++ websites/staging/openoffice/trunk/content/orientation/intro-development.html Fri Oct 21 16:06:36 2016
@@ -131,7 +131,7 @@ h2:hover > .headerlink, h3:hover > .head
 <p>Let's be honest. The size, age and complexity of OpenOffice's C++ codebase makes coding a challenge. This is not a trivial codebase to learn. But if you like a good challenge then you'll love this project!  There are tasks suitable for programmers with a range of programming experience, and we have many veteran OpenOffice hackers in the project who are happy to answer your questions.</p>
 <p>And in its favor, there are few other programs that you can help develop, that have the reach of OpenOffice. Many millions of users depend on OpenOffice, with another million downloads every week, downloads from almost every country in the world. So the work you do, the bugs you fix, the features you add, will benefit millions of users around the world.</p>
 <h2 id="building-openoffice">Building OpenOffice<a class="headerlink" href="#building-openoffice" title="Permanent link">&para;</a></h2>
-<p>It all starts by establishing a local build environment. Building OpenOffice on Linux or Mac is relatively easy, but expect the first attempt to require some trial and error. very configuration is slightly different.</p>
+<p>It all starts by establishing a local build environment. Building OpenOffice on Linux or Mac is relatively easy, but expect the first attempt to require some trial and error. Every configuration is slightly different.</p>
 <p>Building on Windows is more complicated, due to the need to install more prerequisite tools.</p>
 <p>Our <a href="http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO">Building Guide</a> on the wiki is your starting point. Follow the instructions there, step by step. Ask questions on the dev list if you get stuck. If you get an error it can be useful to search our <a href="http://markmail.org/search/+list:org.apache.incubator.ooo-dev">mailing list archives</a> to see if it is a known problem with a known solution.</p>
 <p>Note also the current list of configuration flags used in building the development snapshot builds at the bottom of the <a href="https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-AOO3.4.1">development snapshot builds page</a>.