Skip to content

Commit a4cfe30

Browse files
authored
Change bold text to headings to add id for links
1 parent 77aab0b commit a4cfe30

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

CONTRIBUTING.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -34,21 +34,21 @@ When writing step-by-step instructions (e.g. how to install something), try to f
3434

3535
### Syntax
3636

37-
**Prefer JSX to `createElement`.**
37+
#### Prefer JSX to `createElement`.
3838

3939
Ignore this if you're specifically describing `createElement`.
4040

41-
**Use `const` where possible, otherwise `let`. Don't use `var`.**
41+
#### Use `const` where possible, otherwise `let`. Don't use `var`.
4242

4343
Ignore this if you're specifically writing about ES5.
4444

45-
**Don't use ES6 features when equivalent ES5 features have no downsides.**
45+
#### Don't use ES6 features when equivalent ES5 features have no downsides.
4646

4747
Remember that ES6 is still new to a lot of people. While we use it in many places (`const` / `let`, classes, arrow functions), if the equivalent ES5 code is just as straightforward and readable, consider using it.
4848

4949
In particular, you should prefer named `function` declarations over `const myFunction = () => ...` arrows for top-level functions. However, you *should* use arrow functions where they provide a tangible improvement (such as preserving `this` context inside a component). Consider both sides of the tradeoff when deciding whether to use a new feature.
5050

51-
**Don't use features that aren't standardized yet.**
51+
#### Don't use features that aren't standardized yet.
5252

5353
For example, **don't** write this:
5454

0 commit comments

Comments
 (0)