anchor.diff:        .grid__cell-xs.grid__cell-xs_size_12.raw-text
           br
           :markdown
  -          Congradulations! You should get whole `index.css` file in `dist` directory.
  +          Congradulations! You should get the `index.css` file with all styles in the `dist` directory.
   
  -          While building CSS is straight forward, JavaScript and Templates is a bit more complex subject. There are some tools, that can help you to build projects, that structured in layers and blocks (like [gulp-bem](https://github.com/floatdrop/gulp-bem)).
  +          While building CSS is straight forward, JavaScript and Templates is a bit more complex subject. There are some tools that can help you to build projects structured in layers and blocks (like [gulp-bem](https://github.com/floatdrop/gulp-bem)).
   
  -          You can look at how this site is getting built. We are using Jade for templates and [gulp-bem-pack](https://github.com/floatdrop/gulp-bem-pack) for JavaScript. Dive in site repository — [https://github.com/getbem/getbem.com](https://github.com/getbem/getbem.com).
  +          You can look at how this site is built. We are using Jade for templates and [gulp-bem-pack](https://github.com/floatdrop/gulp-bem-pack) for JavaScript. Dive into the site repository — [https://github.com/getbem/getbem.com](https://github.com/getbem/getbem.com).
  
positive.code:           ```
        .grid__cell-sm.grid__cell-sm_size_4.raw-text
          :markdown
            ### 3. Run build task
  
            ```bash
            gulp build
  
negative.code:     .grid__row
        .grid__cell-xs.grid__cell-xs_size_12.raw-text
          :markdown
            When you are building up a website that contains more than one page — you will soon feel that storing all CSS in a single `index.css` file is a huge pain. When the file becomes larger than __1000__ lines of code, you won't be able to either effectively navigate it or keep maintaining it.
  
            Things are getting worse when you have a team that makes changes in that single file. You will often get merge conflicts (if you are using VCS). Sometimes styles that depend on each other will appear on the opposite sides of this file.
  
            And the most painful part is transfering common parts of this file into another (often new) project.
  
            We propose an easy and intuitive way to structure your BEM CSS code in the filesystem that will solve these problems.
  
            If you have read the [Naming](/naming/) article, you already know that every independent entity on the website will be represented as a __Block__ with __Elements__ that can have __Modifiers__. Keeping that in mind we will split our `index.css` into multiple CSS files on the filesystem. For each BEM entity we will create some files and place them to their own directories:
  
      .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 its own directory and styles file:
  
          .types
            .types__d_b block/
            .types__f_b   block.css
  
          p New blocks should have their own directories:
  
          .types
            .types__d_b block/
  