Incorrect definition of single responsibility principle in docs

[jasonsemko]

One such technique is the single responsibility principle, that is, a component should ideally only do one thing.

From Martin Fowlers book "Clean Architecture" below:

Of all the SOLID principles, the Single Responsibility Principle might be the least well understood. That's likely because it has a particularly inappropriate name. It is too easy for programmers to hear the name and then assume that it means everyone module should do just one thing.

Is this something you all are open to me updating?

[jasonsemko]

This occurs on the "Thinking in React" page

[ianfabs]

Perhaps the wording oversimplifies the core concepts, a quick google search yielded a definition not too far off from the React documentations wording:

The single responsibility principle (SRP) states that every class or module in a program should have responsibility for just a single piece of that program's functionality. Further, the elements of that responsibility should be encapsulated by the responsible class rather than spread out in unrelated classes

This particular excerpt

[...] every class or module in a program should have responsibility for just a single piece of that program's functionality.

This is exactly what I understood from the React documentations phrasing. However I understand that some people may have a hard time with this word, and being explicit is always better than leaving important concepts up to interpretation by others, especially beginners. A better phrasing might be:

One such technique is the single responsibility principle, that is, a component should ideally only have responsibility for just a single piece of your app's functionality. The elements of that responsibility should be encapsulated by the responsible component rather than spread out in unrelated components.

I think this modified explanation not only adheres to the original idea of SRP but it also concisely explains the concept in React-familiar terminology. Please feel free to suggest improvements, aas they are warmly welcome :-)