You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 89 cases, the specification starts a sentence with “Can be set, to”, like in “Can be set, to change the URL.”. To me the comma looks superfluous, and that removing it improves reading flow.
As there are so many occurrences I’m filing this issue. I’m happy to prepare a PR once there’s a signal this can be changed.
The text was updated successfully, but these errors were encountered:
I'm not that proficient in English so I won't comment the gramatical correctness of the thing, but at least I see that the pattern is
Can be set to a value
Can be set, to do something
And as a developper that makes a lot of sense to me: some properties can not be set, letting us know that here it can be set, and that it will do X is expected.
That a comma is (or can be) fine is not the point, but that the sentences in question seem to work without it. That is, the suggestion aims at avoiding to unnecessarily slow reading flow.
In 89 cases, the specification starts a sentence with “Can be set, to”, like in “Can be set, to change the URL.”. To me the comma looks superfluous, and that removing it improves reading flow.
As there are so many occurrences I’m filing this issue. I’m happy to prepare a PR once there’s a signal this can be changed.
The text was updated successfully, but these errors were encountered: