From 159c9fb8c95ba5be5a033310e32c4df28a136499 Mon Sep 17 00:00:00 2001
From: zooko <>
Date: Tue, 19 May 2009 19:24:14 +0000
Subject: [PATCH] go back to instructing people use alllowercasenames for
 modules, even though in a couple of cases (e.g. check_results.py) we use
 underscores for clarity.

[Imported from Trac: page CodingStandards, version 5]
---
 CodingStandards.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CodingStandards.md b/CodingStandards.md
index 9dbc61c..c25271b 100644
--- a/CodingStandards.md
+++ b/CodingStandards.md
@@ -9,7 +9,7 @@ Tahoe requires Python v2.4.2 or greater. No effort should be made to offer compa
 
 ### naming and layout
 
- * Use `underscore_separated_names` for functions, `CamelCapNames` for classes, `all_lower_case_names` for modules, and `ALL_CAPS_NAMES` for constants. Use all lower-case variable names (e.g. `variable_name` or `variablename`). Prepend a leading underscore to private names.
+ * Use `underscore_separated_names` for functions, `CamelCapNames` for classes, `alllowercasenames` for modules, and `ALL_CAPS_NAMES` for constants. Use all lower-case variable names (e.g. `variable_name` or `variablename`). Prepend a leading underscore to private names.
  * Put parenthesis around tuples if it helps make the code more readable, leave them off it not.
 
 ### comments, idioms, miscellany, license