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

[bu...@apache.org]

Author: buildbot
Date: Sat Jul 26 09:23:36 2014
New Revision: 917448

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 Sat Jul 26 09:23:36 2014
@@ -1 +1 @@
-1610552
+1613586

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 Sat Jul 26 09:23:36 2014
@@ -104,8 +104,7 @@ native language mailing lists and suppor
 page describes the steps to create and maintain an NL website.  Following these steps you
 can create a website translation like our <a href="http://www.openoffice.org/es">Spanish</a>, 
 <a href="http://www.openoffice.org/tr">Turkish</a> or <a href="http://www.openoffice.org/nl">Dutch</a> websites. </p>
-<p>user interface
-Making updates to the Apache OpenOffice project's websites is simple.  It's even easy 
+<p>Making updates to the Apache OpenOffice project's websites is simple.  It's even easy 
 for non-committers (new contributors - like you) to create a patch to request that 
 pages are updated by the project community.</p>
 <h2 id="the-xx-website">The XX Website</h2>
@@ -126,13 +125,13 @@ badly out-of-date or is non-standard.  H
 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>Let's take an example.  Suppose your target language is Italian (it).  You will want to do
-the following.  If you are not a Committer and are familiar with Subversion then you will
+the following.  If you are not a Committer and are not familiar with Subversion then you will
 want to get help with these steps by asking on the mailing list.</p>
 <ol>
 <li>Make a copy (svn copy) of the <a href="https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/xx/">ooo-site/trunk/content/xx directory</a>
  as ooo-site/trunk/content/test-it.  In the copy replace all instances of "/xx" 
-in paths with "/test-it"/.</li>
-<li>Also make a copy of <a href="https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/templates/xx/">ooos-site/trunk/templates/xx</a>
+in paths with "/test-it".</li>
+<li>Also make a copy of <a href="https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/templates/xx/">ooo-site/trunk/templates/xx</a>
 and call the copy ooo-site/trunk/templates/test-it.</li>
 <li>Commit these changes and publish via the CMS</li>
 <li>If you are a committer then you can translate the contents of the files in /test-it locally