chore: Copy-edit Neovim readme #888
Conversation
alerque
requested review from
Myriad-Dreamin and
Enter-tainer
as code owners
|
Why add a merge commit from main when there are no conflicts or changes? This just creates clutter in PR history, notifications, and (when you do eventually go to merge) also the squash commit message or merge history. Just because the GH interface has a button for it doesn't need it needs to be or should be clicked in all circumstances. The UI will show you whether there would be any merge conflicts before you attempt to merge. If there are merge conflicts to be resolved that's another matter entirely of course. Also if there are CI changes or some other relevant thing that needs to be brought into the PR that's sometimes reasonable. |
Because this PR was based on the commit that didn't pass the CI (❌), 254c4ce.
So I merged new changes to get a checked mark (✅) in this PR. |
|
Fair enough. |
This just cleans up a few things to make the Neovim related docs read a bit more naturally. No big deal, but presumably whoever wrote this was not a native English speaker because articles and prepositions were a bit scrambled.