svn commit: r792156 - /websites/staging/openofficeorg/trunk/content/openofficeorg/docs/edit-cms.html

[bu...@apache.org]

Author: buildbot
Date: Mon Jul  4 14:18:46 2011
New Revision: 792156

Log:
Staging update by buildbot

Modified:
    websites/staging/openofficeorg/trunk/content/openofficeorg/docs/edit-cms.html

Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/docs/edit-cms.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/docs/edit-cms.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/docs/edit-cms.html Mon Jul  4 14:18:46 2011
@@ -86,12 +86,13 @@ there are potentially four different ver
 <li>You check out the latest version of the web page's source.</li>
 <li>You edit the page source using <a href="http://daringfireball.net/projects/markdown/syntax">Markdown text syntax</a> (mdtext).</li>
 <li>You commit the source into the repository.  You will see the SVN commit mail with
-    your log message</li>
+    your log message.</li>
 <li>The commit automatically triggers a build that converts the markdown files 
-into HTML files in the staging directory.  You will see a commit mail with "Staging update by buildbot" as log message).</li>
+    into HTML files in the staging directory.  You will see a commit mail with "Staging
+    update by buildbot" as log message).</li>
 <li>You verify that the staged webpage is correct and then tell the CMS to publish 
-the changes to the production directory.  (You will see a commit mail with "Publishing merge to openofficeorg site by <your Apache ID>"
-    as log message.)</li>
+    the changes to the production directory.  (You will see a commit mail with "Publishing
+    merge to openofficeorg site by <your Apache ID>" as log message.)</li>
 </ol>
 <p>The intent of this workflow is to allow committers flexibility in changing 
 webpages and testing changes on a staging website, before moving these changes to