docs: split a run-on sentence #29442
Conversation
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
| @@ -1 +1 @@ | |||
| Subproject commit 96626ab9c1242b42a60df9b3cd9a0dc8920b5ea6 | |||
| Subproject commit 58ab642c30d9f97735d5745b5d01781ee199c6ae | |||
There was a problem hiding this comment.
Woah, I have no idea how that happened. Sorry, I'll be more careful in the future, and will fix this right now…
This is two sentences that have been comma spliced, and should be split with a full stop. (This error made me stop and re-read, and I submit this as an actual improvement to readability, not as a grammar weird-o!)
rjbs
force-pushed
the
docs-comma-splice
branch
from
16028e3 to
618d226
Compare
|
I've removed a mistaken commit to a submodule, leaving only the intended change. |
|
it's all good, it happens all the time. Thanks again for the patch! |
|
@bors: r+ rollup |
|
📌 Commit 618d226 has been approved by |
This is two sentences that have been comma spliced, and should be split with a full stop. (This error made me stop and re-read, and I submit this as an actual improvement to readability, not as a grammar weird-o!)
This is two sentences that have been comma spliced, and should
be split with a full stop. (This error made me stop and re-read,
and I submit this as an actual improvement to readability, not
as a grammar weird-o!)