Improve wording in the readme #52
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
glensc
force-pushed
the
readme-update
branch
2 times, most recently
from
0b2be13 to
88c8291
Compare
jrfnl
reviewed
Mar 14, 2021
- Update Fork section to be neutral and include current fork relation - Improve wording in the rest of the readme - Add git blame as well into readme
|
@jrfnl, I've updated based on your suggestions. I may have missed some suggestions, if the GitHub UI didn't show them anymore after the previous suggestion apply. |
|
In my opinion, it looks beautiful now :) |
jrfnl
approved these changes
Mar 15, 2021
|
@glensc Thanks for updating the PR! |
|
Thank you both, it looks so better 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make the text more fluent, include the rest of the forking history, include bit about output types, and remove negative emotions from the readme.