From effc8a55fd2d0129545e1b9200f7a17bfe367057 Mon Sep 17 00:00:00 2001
From: Artem Zakharchenko <kettanaito@gmail.com>
Date: Fri, 30 Jun 2017 12:29:56 +0200
Subject: [PATCH] Update README.md

---
 README.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/README.md b/README.md
index 258cf5e..09ff148 100644
--- a/README.md
+++ b/README.md
@@ -41,6 +41,11 @@ return (<Button disabled={isDisabled} />);
 ```
 prefix? + action (A) + high context (HC) + low context (LC)
 ```
+This is not a rule, but rather a pattern which can be applied quite often when naming variables.
+
+> Keep in mind, that order of the contexts affects the core meaning of a variable. For example, `shouldUpdateComponent` means *you* are about to update a component, while `shouldComponentUpdate` tells you that *component* will update on itself, and you are but controlling whether it should.
+In other words, high context emphasizes the meaning of the variable.
+
 ### Example
 | Name | Prefix | Action | High context | Low context |
 | ---- | ---- | ------ | ------------ | ----------- |