anchor.diff:            notation, it is pretty natural to write `&_mod` there and finally get a modifier declared as it was recommended.
           a(id="can-i-create-global-modifier")
           :markdown
  -          ## Can I create a modifier global applicable to any block? Like `visible`/`invisible`.
  +          ## Can I create a global modifier applicable to any block? Like `visible`/`invisible`.
   
             > I've heard that global modifiers like `visible`, `invisible`, `red`, `opacity50` are not welcomed in BEM. Why?
  -          > I think it is useful to incorporate common properties like this in such a global class and than apply it to different blocks.
  +          > I think it is useful to incorporate common properties like this in such a global class and then apply it to different blocks.
   
             Indeed you can have 2 main CSS classes at the same DOM node. In BEM we call it `mix`:
   
  
positive.code:           All this hell can be avoided by encapsulating a modifier in a block like `.block_mod`.
  
            Indeed using global modifiers makes the resultant code less. However if you measure the real difference in bytes it usually does not
            seam that big. Especially if you are using CSS optimizator which can combine selectors.
  
negative.code:             display: none;
            }
            ```
            Both block and modifier selectors have the same specificity. As modifier declaration goes after the block, it redefines the CSS
            properties. These styles belong to block and are stored in the block file. Thus, independently on how the resultant CSS is built
            from source, you will always have them in this order and be sure that redefining happens.
  
            In the case of global modifier, its properties can be redefined by the blocks if they follow modifiers in code:
  