You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openoffice.apache.org by bu...@apache.org on 2011/06/20 03:22:03 UTC

svn commit: r791235 - /websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/lazyConsensus.html

Author: buildbot
Date: Mon Jun 20 01:22:03 2011
New Revision: 791235

Log:
Staging update by buildbot

Modified:
    websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/lazyConsensus.html

Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/lazyConsensus.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/lazyConsensus.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/lazyConsensus.html Mon Jun 20 01:22:03 2011
@@ -65,7 +65,7 @@ Consensus means that when you are convin
 would like to see happen you can simply assume that you already have consensus
 and get on with the work. You don't have to insist people discuss and/or
 approve your plan, and you certainly don't need to call a vote to get approval.
-You just assume you have the communities support unless someone says otherwise.</p>
+You just assume you have the community's support unless someone says otherwise.</p>
 <p>We have a time machine (Subversion), this means that as long as you commit 
 (or submit patches) early and often the community has plenty of opportunity 
 to indicate disapproval. If you believe the community will support your action