svn commit: r1613586 - /openoffice/site/trunk/content/website-native.mdtext

[pe...@apache.org]

Author: pescetti
Date: Sat Jul 26 09:23:32 2014
New Revision: 1613586

URL: http://svn.apache.org/r1613586
Log:
Fix a few typos.

Modified:
    openoffice/site/trunk/content/website-native.mdtext

Modified: openoffice/site/trunk/content/website-native.mdtext
URL: http://svn.apache.org/viewvc/openoffice/site/trunk/content/website-native.mdtext?rev=1613586&r1=1613585&r2=1613586&view=diff
==============================================================================
--- openoffice/site/trunk/content/website-native.mdtext (original)
+++ openoffice/site/trunk/content/website-native.mdtext Sat Jul 26 09:23:32 2014
@@ -24,7 +24,6 @@ page describes the steps to create and m
 can create a website translation like our [Spanish](http://www.openoffice.org/es), 
 [Turkish](http://www.openoffice.org/tr) or [Dutch](http://www.openoffice.org/nl) websites. 
 
-user interface
 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.
@@ -51,13 +50,13 @@ is probably best not to wipe out the exi
 to do your work in a test directory.
 
 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.
 
  1. Make a copy (svn copy) of the [ooo-site/trunk/content/xx directory](https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/xx/)
  as ooo-site/trunk/content/test-it.  In the copy replace all instances of "/xx" 
-in paths with "/test-it"/.
- 1. Also make a copy of [ooos-site/trunk/templates/xx](https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/templates/xx/)
+in paths with "/test-it".
+ 1. Also make a copy of [ooo-site/trunk/templates/xx](https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/templates/xx/)
 and call the copy ooo-site/trunk/templates/test-it.
  1. Commit these changes and publish via the CMS
  1. If you are a committer then you can translate the contents of the files in /test-it locally
@@ -147,4 +146,4 @@ due to a CMS build issue we've run into 
 ## Maintaining NL Websites
 
 Do try to check your NL website every few weeks to see if any changes are needed.  Try to keep it in sync
-with the English website.  Is there a new announcement header?  A new release?  A new blog post?
\ No newline at end of file
+with the English website.  Is there a new announcement header?  A new release?  A new blog post?