svn commit: r852005 - in /websites/staging/openoffice/trunk/content: ./ orientation/intro-doc.html

[bu...@apache.org]

Author: buildbot
Date: Tue Feb 26 08:21:45 2013
New Revision: 852005

Log:
Staging update by buildbot for openoffice

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

Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 26 08:21:45 2013
@@ -1 +1 @@
-1449975
+1450061

Modified: websites/staging/openoffice/trunk/content/orientation/intro-doc.html
==============================================================================
--- websites/staging/openoffice/trunk/content/orientation/intro-doc.html (original)
+++ websites/staging/openoffice/trunk/content/orientation/intro-doc.html Tue Feb 26 08:21:45 2013
@@ -100,7 +100,7 @@
   
     <h1 class="title">Introduction to Documentation</h1>
     <h2 id="introduction">Introduction</h2>
-<p>In this orientation module you will learn how to get started in the OpenOffice Documentation Team</p>
+<p>In this orientation module you will learn how to get started in the OpenOffice Documentation Team.</p>
 <p>To complete this module, read through the material on this page, including the linked references.  There will also
 be some start-up tasks for you to perform, such as signing up for an account in our wiki.</p>
 <p>Your first task is to subscribe to our Documentation mailing list. You can subscribe by sending an email to 
@@ -125,7 +125,7 @@ are doing just basic editing. Others are
 <li>They might post a question to our <a href="http://forum.openoffice.org">community support forum</a></li>
 <li>They might go to the <a href="http://www.openoffice.org">OpenOffice.org website</a> and look for a solution there</li>
 </ul>
-<p>The documentation we write aids both the end-users as well as those who support the end users.  We aim to provide authorative, up-to-date material for Apache OpenOffice, and to aid
+<p>The documentation we write aids both the end-users as well as those who support the end users.  We aim to provide authoritative, up-to-date material for Apache OpenOffice, and to aid
 users of all skill levels.  If we do our tasks well, users are more satisfied and more productive.</p>
 <h2 id="varieties-of-documentation">Varieties of Documentation</h2>
 <p>We maintain documentation in a variety of forms:</p>
@@ -159,7 +159,7 @@ language errors.  So you don't need to h
 <li>Reviewing draft documentation for technical correctness, e.g., repeating the steps described in a task and verifying that they are complete and no steps are missing.</li>
 <li>Editing draft documentation for clarity and style.</li>
 <li>Preparing screenshots, diagrams and artwork for covers.</li>
-<li>Developing tools and scripts to aid in repetivive tasks, such as document format conversions.</li>
+<li>Developing tools and scripts to aid in repetitive tasks, such as document format conversions.</li>
 </ul>
 <h2 id="getting-started">Getting Started</h2>
 <p>The Documentation Team is the easiest one to get started with.  There are just a few basic steps:</p>