proof reading documentation

[iamstarkov]

there are two problems:

• docs might have typos and grammar mistakes, because English is not my native language
• docs might have logic flaws and be unintuitive for other developers_, because I am knee deep in this project, so I understand everything and it seems easy for me, so I struggle to understand what is missing in documentation.

So I need help from native speakers and from developers who are new to this project

[GertSallaerts]

Personally I would reduce/remove the entire motivation section. My thoughts are, just tell people something like

withTheme makes sure your theme is always available and up to date for the component it wraps. It does not matter how far down the React tree it is, nor does it matter if you use PureComponent or other ways of update blocking in between, the theme will always be available and up to date.

I'd remove all the extra information about context etc. Because it's like you say, users should not have to worry about context, that's up to library owners. We just promise them it works, they don't need to worry their heads about whether or not we're using context.

Anyway, that's just my personal opinion on the subject. What are your thoughts?