svn commit: r1242203 - /incubator/ooo/site/trunk/content/openofficeorg/community-faqs.mdtext

[ro...@apache.org]

Author: robweir
Date: Thu Feb  9 01:42:56 2012
New Revision: 1242203

URL: http://svn.apache.org/viewvc?rev=1242203&view=rev
Log:
Consistent header levels

Modified:
    incubator/ooo/site/trunk/content/openofficeorg/community-faqs.mdtext

Modified: incubator/ooo/site/trunk/content/openofficeorg/community-faqs.mdtext
URL: http://svn.apache.org/viewvc/incubator/ooo/site/trunk/content/openofficeorg/community-faqs.mdtext?rev=1242203&r1=1242202&r2=1242203&view=diff
==============================================================================
--- incubator/ooo/site/trunk/content/openofficeorg/community-faqs.mdtext (original)
+++ incubator/ooo/site/trunk/content/openofficeorg/community-faqs.mdtext Thu Feb  9 01:42:56 2012
@@ -31,13 +31,13 @@ official approval for legal or process r
 Most of the time we work with the consensus building techniques documented below.
 
 
-### What is "Lazy Consensus"?
+## What is "Lazy Consensus"?
 
 [Lazy consensus][10] 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.
 
-### Consensus Building
+## Consensus Building
 
 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
@@ -47,7 +47,7 @@ for quickly showing your support or othe
 Once there is a consensus people can proceed with the work under the [lazy 
 consensus][12] model.
 
-### What about voting?
+## What about voting?
 
 Occasionally a "feel" for consensus is not enough. Sometimes we need to 
 have a measurable consensus. For example, when [voting][13] in new committers or