svn commit: r920404 - in /websites/staging/openoffice/trunk/content: ./ website-native.html

[bu...@apache.org]

Author: buildbot
Date: Mon Aug 25 21:25:00 2014
New Revision: 920404

Log:
Staging update by buildbot for openoffice

Modified:
    websites/staging/openoffice/trunk/content/   (props changed)
    websites/staging/openoffice/trunk/content/website-native.html

Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Aug 25 21:25:00 2014
@@ -1 +1 @@
-1620454
+1620458

Modified: websites/staging/openoffice/trunk/content/website-native.html
==============================================================================
--- websites/staging/openoffice/trunk/content/website-native.html (original)
+++ websites/staging/openoffice/trunk/content/website-native.html Mon Aug 25 21:25:00 2014
@@ -124,7 +124,7 @@ want to translate.</p>
 badly out-of-date or is non-standard. However, until your new translation is ready to go it 
 is probably best not to wipe out the existing NL page. So initially you will probably want
 to do your work in a test directory.</p>
-<p><strong>Let's take an concreate example:</strong>
+<p><strong>Let's take a concrete example:</strong>
 <br />
 Suppose your target language is Italian (it). You will want to do
 the following. If you are not a Committer and are not familiar with Subversion then you