Remove confusing preposition #469
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
Unless intended to be "too," rather than a "to" statement, the extra "to" should be removed for readability.
|
Thanks! Nice catch. Note that the preferred way to submit documentation fixes is to post in #docs on the Discord server. |
|
Gotcha. Will do.
…On Mar 13, 2021 at 1:19:29 PM, leastbad ***@***.***> wrote:
Thanks! Nice catch.
Note that the preferred way to submit documentation fixes is to post in
#docs on the Discord server.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#469 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAVJFMXMQR264D6QSBVRN3TDOUDDANCNFSM4ZEAVOIQ>
.
|
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.
Unless intended to be "too," rather than a "to" statement, the extra "to" should be removed for readability.
Type of PR (feature, enhancement, bug fix, etc.)
Description
Please include a summary of the change and which issue is fixed.
Fixes # (issue)
Why should this be added
Explain value.
Checklist
Please note that the best way to suggest changes or updates to the documentation is to join Discord and leave a note in the #docs channel. Any documentation updates posted as PRs cannot be accepted at this time. ❤️