Thanks for the feedback. This is the first time, I got a feedback on this.

I used it for highlighting points. I think I am over using it. Will minimize it.

Usually you would use bold like that where you would stress the vocalisation when reading it aloud, not for highlighting key points you want to make. If you read that and stress those words it just sounds weird and confusing.

> This is the first time, I got a feedback on this.

That comma placement is strange too. I'm thinking not a native english speaker. It's a great tool though. Not taking away from that at all. Thanks for making it. :)

While that may be true, how is that observation relevant?

In the spirit of providing feedback to help improve the documentation, and with regard to the bold text:

The article made it difficult to find out what React Storybook is quickly.

The style of article is informational, which is usually written like a pyramid. High level information at the top, then works into more detail-oriented sections, most important first. For example, "any react application" would probably come in the second paragraph, after the high level intro as that was an important point (based on the repetition) in the bullets.

Minimize? Get rid of it entirely.

Yeah it feels a bit overly emphatic and somewhat pleading -- better to argue your point through the library itself.

Agreed but he's using it to emphasize a point not for making skimming easier.

Frequently bolding key words for quotable/sharable emphasis is one of the more recently-developed growth hacks. (not sarcasm)

It always throws me off. As much as I love it, Nicolás Bevacqua's Ponyfoo is a bad example of this. Too much emphasis that it becomes noise.[1]

[1] An example: https://ponyfoo.com/articles/github-for-human-beings

Luckily the content is good enough that it doesn't matter. But IMO emphasis should be barely used at all.

Yeah, kinda weird for a text that supposedly talks about making good UI.

(Which I meant to add is really excellent work)