anchor.diff:            ```
         .grid__cell-sm.grid__cell-sm_size_4.raw-text
           :markdown
  -          ### 3. Run build task
  +          ### 3. Run the build task
   
             ```bash
             gulp build
  
positive.code:     .grid__row
        .grid__cell-xs.grid__cell-xs_size_12.raw-text
          :markdown
            When you developing site, that contains more than one page — you will soon feel, that storing all CSS in `index.css` file is huge pain. When single file becomes more than __1000__ lines of code you can't effectivly navigate in it, neither maintain it.
  
            Things getting worse, when you have a team, that making changes in single file. Often you will get merge conflicts (if you are using VCS). Some times styles, that belongs to each other will be in opposite ends of this file.
  
            And most painful part — is transfering common parts of this file into other (often new) project.
  
            We propose easy and intuitive way to structure your BEM CSS code on file system, that will solve these problems.
  
            If you are read [Naming](/naming/) article, you already know, that any separate entity on the site will be a __Block__ with __Elements__ that can have __Modifiers__. Keeping that in mind we will split our `index.css` into multiple CSS files on file system. For each BEM entity we will create some files and place them to own folder:
  
      .grid__row
        .grid__cell-sm.grid__cell-sm_size_4.grid__block-cell.raw-text
          .heading.heading_level_3 Blocks
  
          p Each block will have it's own directory and file with styles:
  
          .types
            .types__d_b block/
            .types__f_b   block.css
  
          p New blocks should have their own folders:
  
          .types
            .types__d_b block/
  
negative.code:       .grid__cell-sm.grid__cell-sm_size_4.grid__modifier-cell.raw-text
          .heading.heading_level_3 Modifiers
  
          p Both blocks and elements can have modifiers, so they can be placed either in the block directory:
  
          .types
            .types__d_b block/
  