From 4508e57f0726dbb00414f6d646201507d20d8f86 Mon Sep 17 00:00:00 2001
From: Benjamin Michaelis <benjamin@michaelis.net>
Date: Wed, 17 Feb 2021 15:55:58 -0800
Subject: [PATCH] Update Guidelines(8th Edition).xml

- Include "DO" in guideline description
---
 docs/Guidelines(8th Edition).xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/Guidelines(8th Edition).xml b/docs/Guidelines(8th Edition).xml
index 0fc2864c..2d8e2aff 100644
--- a/docs/Guidelines(8th Edition).xml	
+++ b/docs/Guidelines(8th Edition).xml	
@@ -64,7 +64,7 @@
 	<guideline key="Ch06_2fa1861" severity="DO" section="Naming" subsection="Variables and fields">"DO name properties using a noun, noun phrase, or adjective."</guideline>
 	<guideline key="Ch06_7dda59f" severity="CONSIDER" section="Naming" subsection="Miscellaneous">CONSIDER giving a property the same name as its type.</guideline>
 	<guideline key="Ch06_d75e3ef" severity="AVOID" section="Naming" subsection="Casing">AVOID naming fields with camelCase.</guideline>
-        <guideline key="" severity="DO" section="Naming" subsection="Variables and fields">Name fields with PascalCase and a leading underscore.</guideline>
+        <guideline key="" severity="DO" section="Naming" subsection="Variables and fields">DO name fields with PascalCase and a leading underscore.</guideline>
 	<guideline key="Ch06_028c753" severity="DO" section="Naming" subsection="Casing">"DO favor prefixing Boolean properties with “Is,” “Can,” or “Has,” when that practice adds value."</guideline>
 	<guideline key="Ch06_d80065c" severity="DO" section="Naming" subsection="Variables and fields">DO declare all instance fields as private (and expose them via a property).</guideline>
 	<guideline key="Ch06_0d3a13f" severity="DO" section="Naming" subsection="Casing">DO name properties with PascalCase.</guideline>