Skip to content

Commit 0787aac

Browse files
authored
Fix grammar, spelling and formatting
I do this quite a lot on Stack Overflow, I've tried to edit your English and make the formatting more consistent using the same level of heading, but maintain as much as what you'd written as possible.
1 parent a215e8b commit 0787aac

File tree

1 file changed

+17
-14
lines changed

1 file changed

+17
-14
lines changed

README.md

Lines changed: 17 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,14 @@
11
# CSS Micro Reset
22

3-
You probably don't need CSS Reset, at least not complete CSS Reset.
3+
You probably don't need CSS Reset, at least not the complete CSS Reset.
44

5-
Every Browser has it's own CSS Reset. Reseting it again means that later you need to set all reseted elements.
5+
Every Browser has it's own CSS Reset. Resetting it again means that later you need to set all resetted elements.
66

7-
Basically you have Browser Reset -> Your Reset -> Setting all Reseted Elements -> probably another styling at the end.
7+
Basically you have:
88

9-
#### Let take typical H1 tag mistake:
9+
Browser Reset -> Your Reset -> Setting all Resetted Elements -> Probably more styling after.
10+
11+
## A typical `H1` tag mistake:
1012

1113
```css
1214
/* Chrome Reset */
@@ -40,7 +42,7 @@ h1 {
4042
font-weight: normal;
4143
}
4244

43-
/* And probably you will do one more H1 setting */
45+
/* And probably you will do one more further H1 setting */
4446

4547
h1 {
4648
color: #111;
@@ -50,27 +52,28 @@ font-weight: normal;
5052

5153
/* I will assume one or two more setting of H1 tag here :) */
5254
```
53-
**We all did this mistake too many times.**
5455

55-
Why not skip the reset and set just the elements you need for your project?
56+
## We've all made this mistake too many times.
57+
58+
Why not skip the reset and just set the elements that you need for your project?
5659

57-
Also why reseting some elements if you are not using them in your project. Example: If you don't have forms in your project don't reset them.
60+
Also why are you resetting some elements if you are not using them in your project. For example, if you don't have forms in your project, don't reset them.
5861

59-
Other thing: It's Ok some elements to be different in different browsers.
62+
Another thing: It's Ok for some elements to be different between browsers.
6063

61-
Why not start with bare bones reset and if needed add some elements?
64+
Why not start with bare bones reset and only add some elements if needed?
6265

63-
I've did just that: **Micro CSS Reset**
66+
I've done just that: **CSS Micro Reset**
6467

65-
Feel free to add or remove elements to Micro CSS Reset, don't just blindly use it. Example: if don't use tables remove all the table related tags in the Micro CSS Reset.
68+
Feel free to add or remove elements to CSS Micro Reset, don't just blindly use it. For example, if don't use tables remove all the table related tags in the CSS Micro Reset.
6669

6770
Like I said in the beginning: You may not need this or any other CSS reset.
6871

6972
*Before use, understand what this reset does.*
7073

7174
## Download or Install
7275

73-
You can copy-paste the CSS code, use direct download, or use npm:
76+
You can copy-paste the CSS code, use the direct download, or use npm:
7477

7578
```
7679
$ npm i css-micro-reset
@@ -81,6 +84,6 @@ Or use the CDN link:
8184
<link rel="stylesheet" href="https://unpkg.com/css-micro-reset@1.0.0/micro-css-reset.css">
8285
```
8386

84-
### License
87+
## License
8588

8689
This project is licensed under the MIT License

0 commit comments

Comments
 (0)