svn commit: r1142683 - /incubator/ooo/site/trunk/content/openofficeorg/docs/edit-cms.mdtext

[jo...@apache.org]

Author: joes
Date: Mon Jul  4 14:19:49 2011
New Revision: 1142683

URL: http://svn.apache.org/viewvc?rev=1142683&view=rev
Log:
parens

Modified:
    incubator/ooo/site/trunk/content/openofficeorg/docs/edit-cms.mdtext

Modified: incubator/ooo/site/trunk/content/openofficeorg/docs/edit-cms.mdtext
URL: http://svn.apache.org/viewvc/incubator/ooo/site/trunk/content/openofficeorg/docs/edit-cms.mdtext?rev=1142683&r1=1142682&r2=1142683&view=diff
==============================================================================
--- incubator/ooo/site/trunk/content/openofficeorg/docs/edit-cms.mdtext (original)
+++ incubator/ooo/site/trunk/content/openofficeorg/docs/edit-cms.mdtext Mon Jul  4 14:19:49 2011
@@ -35,11 +35,11 @@ The general flow for updating the websit
 
  1. You check out the latest version of the web page's source.
  1. You edit the page source using [Markdown text syntax][1] (mdtext).
- 1. You commit the source into the repository.  You will see the SVN commit mail with
-    your log message.
+ 1. You commit the source into the repository.  (You will see the SVN commit mail with
+    your log message.)
  1. 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).
+    into HTML files in the staging directory.  (You will see a commit mail with "Staging
+    update by buildbot" as log message.)
  1. 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.)