Conversation
- librairy → library - there're → there are - does not provides → does not provide - will maybe never be → may never be - Curently → Currently - Do not launch → Does not launch - Computations → Computation - quantity → amount - OOM → OOMs - superior or equal → greater than or equal - inferior → fewer - thanks → thank - writting → writing
There was a problem hiding this comment.
Pull request overview
This PR improves the English in the project README to make the library description and usage guidance clearer for readers.
Changes:
- Corrects typos (e.g., “librairy” → “library”, “writting” → “writing”) and grammar throughout the README.
- Refines phrasing in several sections (goal/intro, heap and CPU usage considerations, acknowledgments) for clarity.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| It's meant to be used in JRuby programs. | ||
| It can be used in Scala programs, of course, but there're better, pure, ways with such language to achieve the same goal. | ||
| It can be used in Scala programs, of course, but there are better, pure, ways with such language to achieve the same goal. |
There was a problem hiding this comment.
This sentence still reads ungrammatically/awkwardly ("better, pure, ways" and "such language"). Consider rephrasing (e.g., remove the commas and use "such a language" / "in Scala"), so the meaning is clear.
| It can be used in Scala programs, of course, but there are better, pure, ways with such language to achieve the same goal. | |
| It can be used in Scala programs, of course, but there are better, purer ways in Scala to achieve the same goal. |
| Because this lib knows nothing about the computations you'll ask it to execute, in order to maximise CPU usage | ||
| and therefore the speed of your Excel extraction, you'll have to ensure that the number of registered computations (number of calls to the `addRows` function) | ||
| is greater than or equal to the number of cores your CPU has. |
There was a problem hiding this comment.
The sentence break here makes the clause structure a bit incorrect/unclear ("Because …, in order to … and therefore …"). Consider rewriting as a single sentence (e.g., "Because …, to maximise CPU usage (and therefore speed), …") for readability.
| Because this lib knows nothing about the computations you'll ask it to execute, in order to maximise CPU usage | |
| and therefore the speed of your Excel extraction, you'll have to ensure that the number of registered computations (number of calls to the `addRows` function) | |
| is greater than or equal to the number of cores your CPU has. | |
| Because this lib knows nothing about the computations you'll ask it to execute, to maximise CPU usage and therefore the speed of your Excel extraction, you'll have to ensure that the number of registered computations (number of calls to the `addRows` function) is greater than or equal to the number of cores your CPU has. |
- librairy → library - there're → there are - does not provides → does not provide - will maybe never be → may never be - Curently → Currently - Do not launch → Does not launch - Computations → Computation - quantity → amount - OOM → OOMs - superior or equal → greater than or equal - inferior → fewer - thanks → thank - writting → writing
Summary