Grammar fixes for python core operations docs#15832
Conversation
|
Please fix whitespace issues: |
|
@alalek Does my commit above fix the issue, or are there more cases of trailing whitespace? Also, should I squash the two commits above or keep as is? |
asmorkalov
left a comment
There was a problem hiding this comment.
@collinbrake Please squash commits. You can check trailing white spaces on your side with git command git diff --check.
| are always on faces :D ) and performance (because we search in a small area). | ||
|
|
||
| ROI is again obtained using Numpy indexing. Here I am selecting the ball and copying it to another | ||
| ROI is obtained by using Numpy indexing again. Here I am selecting the ball and copying it to another |
There was a problem hiding this comment.
IMHO, this line changed its meaning.
|
@asmorkalov I am going to revert these changes on a different branch -- closing pull request. |
|
No need to re-create new PRs. |
|
@collinbrake The grammar fixes look good to me 👍. Please squash your commits. |
|
@asmorkalov Thanks for your help with this! I was planning to squash the commits, so I probably should have labeled this PR as a work in progress until I got that finished. |
This pullrequest improves the grammar in the following sections: