[documentation-guide] more structure for style chapter

[Pete Travis]

commit e44269175dd3c5b5a90a7ce5036c502f6195d5a9
Author: Pete Travis <pete at thefool.petetravis.com>
Date:   Mon Oct 24 23:05:20 2011 -0600

    more structure for style chapter

 en-US/style.xml |   17 +++++++++++++++--
 1 files changed, 15 insertions(+), 2 deletions(-)
---
diff --git a/en-US/style.xml b/en-US/style.xml
index 866fb13..c567762 100644
--- a/en-US/style.xml
+++ b/en-US/style.xml
@@ -8,21 +8,34 @@
 	<para>
 		Your writing should be styled consistently and concisely. This section will outline style conventions to be used when writing documentation.
 	</para>
-	
-	<section id="sect-documentation_guide-style-be_Consistent">
+	<section id="sect-documentation_guide-style-be_consistent">
 		<title>Be Consistent</title>
 		<para>
 			Make the flow of information easy to follow from point to point. If you need to sidetrack, link.
 		</para>
+	</section>	
 	<section id="sect-documentation_guide-style-be_direct">
 		<title>Be Direct</title>
 		<para>
 			Get straight to the point.
 		</para>
+	</section>	
 	<section id="sect-documentation_guide-style-be_concise">		
 		<title>Be Concise</title>
 		<para>
 			Don't use bromides and frivolous clauses.
 		</para>
+	</section>
+	<section id="sect-documentation_guide-style-be_professional">
+		<title>Be Professional</title>
+		<para>
+			Keep your writing relevant and impersonal.
+		</para>
+	</section>
+	<section id="sect-documentation_guide-style-be_accurate">
+		<title>Be Accurate</title>
+		<para>
+			Use clear, contextually appropriate language.
+		</para>	
 	</section>	
 </chapter>
\ No newline at end of file