Updated AV1115 for local functions (#148)

dennisdoomen · May 7, 2018 · c28253c · c28253c
1 parent f86ebd4
commit c28253c
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/_pages/1100_MemberDesignGuidelines.md b/_pages/1100_MemberDesignGuidelines.md
@@ -25,9 +25,9 @@ Having properties that cannot be used at the same time typically signals a type
 
 This violation is often seen in domain models and introduces all kinds of conditional logic related to those conflicting rules, causing a ripple effect that significantly increases the maintenance burden.
 
-### <a name="av1115"></a> A method or property should do only one thing (AV1115) ![](/assets/images/1.png)
+### <a name="av1115"></a> A property, method or local function should do only one thing (AV1115) ![](/assets/images/1.png)
 
-Similarly to rule AV1000, a method should have a single responsibility.
+Similarly to rule AV1000, a method body should have a single responsibility.
 
 ### <a name="av1125"></a> Don't expose stateful objects through static members (AV1125) ![](/assets/images/2.png)
 

diff --git a/_pages/Cheatsheet.md b/_pages/Cheatsheet.md
@@ -44,7 +44,7 @@ NOTE: Requires Markdown Extra. See http://michelf.ca/projects/php-markdown/extra
 
 * Allow properties to be set in any order (AV1100)  
 * Don’t use mutual exclusive properties (AV1110)  
-* A method or property should do only one thing (AV1115)  
+* A property, method or local function should do only one thing (AV1115)  
 * Don’t expose stateful objects through static members (AV1125)   
 * Return an `IEnumerable<T>` or `ICollection<T>` instead of a concrete collection class (AV1130)   
 * Properties, methods and arguments representing strings or collections should never be `null` (AV1135)