svn commit: r804304 - /websites/staging/openofficeorg/trunk/content/openofficeorg/community-faqs.html

[bu...@apache.org]

Author: buildbot
Date: Thu Feb  9 01:43:00 2012
New Revision: 804304

Log:
Staging update by buildbot for openofficeorg

Modified:
    websites/staging/openofficeorg/trunk/content/openofficeorg/community-faqs.html

Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/community-faqs.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/community-faqs.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/community-faqs.html Thu Feb  9 01:43:00 2012
@@ -88,18 +88,18 @@ set of simple processes to ensure things
 <p>In ASF projects we don't like to vote. We reserve that for the few things that need 
 official approval for legal or process reasons (e.g. a release or a new committer). 
 Most of the time we work with the consensus building techniques documented below.</p>
-<h3 id="what_is_lazy_consensus">What is "Lazy Consensus"?</h3>
+<h2 id="what_is_lazy_consensus">What is "Lazy Consensus"?</h2>
 <p><a href="/openofficeorg/docs/governance/lazyConsensus.html">Lazy consensus</a> is the first, and possibly the most important, consensus building 
 tool we have. Essentially lazy consensus means that you don't need to get explicit
 approval to proceed, but you need to be prepared to listen if someone objects.</p>
-<h3 id="consensus_building">Consensus Building</h3>
+<h2 id="consensus_building">Consensus Building</h2>
 <p>Sometimes lazy consensus is not appropriate. In such cases it is necessary to
 make a proposal to the mailing list and discuss options. There are mechanisms
 for quickly showing your support or otherwise for a proposal and 
 <a href="/openofficeorg/docs/governance/consensusBuilding.html">building consensus</a> amongst the community.</p>
 <p>Once there is a consensus people can proceed with the work under the <a href="/openofficeorg/docs/governance/lazyConsensus.html">lazy 
 consensus</a> model.</p>
-<h3 id="what_about_voting">What about voting?</h3>
+<h2 id="what_about_voting">What about voting?</h2>
 <p>Occasionally a "feel" for consensus is not enough. Sometimes we need to 
 have a measurable consensus. For example, when <a href="/openofficeorg/docs/governance/voting.html">voting</a> in new committers or 
 to approve a release. </p>