docs: fix more typos#3027
Conversation
Signed-off-by: John E <jeis4wpi@outlook.com>
|
Thanks again. |
There was a problem hiding this comment.
Looks good.
Just a tip for future pull requests. When making a pull request it should be done with a different branch than develop. You should execute git checkout -b pull-request-branch-name when the develop branch is checked out. That is where pull-request-branch-name is a short descriptive name for the branch and the changes it makes. For example, for this pull request you could use typo-fixes.
Also, rather than asking if the pull request is okay, just give a description of what is done for the pull request message. For this, something like docs: fix more typos would be sufficient. You don't need to also ask if the pull request is okay.
|
Thank you for the feedback. Apologies for the wrong branch. Best of luck with 2.21 release. |
|
@drgrice1 Are you going to make a PR for the release branch? I can if you aren't already doing that. |
More typo fixes (#3027 for the release candidate)
|
@somiaj: Thanks for reminding me. It is done. |
3 participants
docs: fix more typos
Is this one okay as well ?