Update README.md

README.md

@@ -44,9 +44,11 @@ sudo npm install -g less-plugin-autoprefixer
 
 Why
 ---
-Stop learning Frameworks. Start building web apps. Go back to the basics and write HTML with understandable classes to exactly know what you do and how to change it. Make your work independend from nested dependencies which can break your build from the bottom up. Use the HTML class attribute what it is made for. And use it much, and right. While classes usually have been intended to be what the name suggests: classes (groups), the simple grouping of similar styled elements turned to become limited for modern and complex mobile web. A class name headers do not tell enough today and there can be very different headers reacting different on narrowed mobile devices. That's why classes became more and more cluttered and confusing labels and frameworks started to misuse it and the nesting of html elements in combination of classes mage the html almost unreadable. Today classes should still be used what they are made for, but in an extended manner. Not to group headers but to group styles.
+ > Stop learning Frameworks. Start building web apps. 
 
-QCSS keeps the parts independed from any other concept and you can do the so called "sliding" changes rapidly by changing numbers in classes. Without revamping the whole LESS/SASS stack or other concepts which need many additional concept overthinking while editing. These modern doubtless helpful additonal layers all have the one big disadvantage that they suffer from: the ability to keep up consistency and colligation when making direct minimalist changes in a little corner of a project or when "unchaining" of style groups is needed. QCSS uses a smart class group concept, easy to remember after some working with it and simple to define. And you always know what comes from where. 
+Go back to the basics and write HTML with understandable classes to exactly know what you do and how to change it. Make your work independend from nested dependencies which can break your build from the bottom up. Use the HTML class attribute what it is made for. Or better sad: what it is intended for today. And use it much, and right. While classes usually have been intended to be what the name suggests: classes (groups), the simple grouping of similar styled elements turned to become limited for modern and complex mobile web. A class name like _headers_ do not tell enough today. And there can be very different _headers_ reacting different on narrowed mobile devices. You also have to go back to the headers section of your CSS to knnow what styles you have used or of other things cause the unwanted look. That's why classes became more and more cluttered and confusing labels and frameworks started to misuse it and the nesting of html elements in combination of classes made the HTML almost unreadable. Today, classes should still be used what they are made for. But in an extended manner. Not to group such like _headers_ but such like _styles_. And voila you get a _header_ like this `<header class="b1 m1 maxh2"></header>` and you will know by reading the HTML that it has a minimal border, a minimal margin and a max-height of x2.
+
+QCSS keeps its concept independed from any other and can perfectly integrated into other concepts. And you can do the so called "sliding" changes rapidly by changing numbers in classes. Without revamping the whole LESS/SASS stack or other concepts which need many additional concept overthinking while editing. These modern doubtless helpful additonal layers all have the one big disadvantage that they suffer from: the ability to keep up consistency and colligation when making direct minimalist changes in a little corner of a project or when "unchaining" of style groups is needed. QCSS uses a smart class group concept, easy to remember after some working with it and simple to define. And you always know what comes from where. 
 
 As I have often stated *"Do not put more on the table than you can eat."* or *"Don't chain longer than you'll be able to survey."*