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
{{ message }}
This repository was archived by the owner on Oct 9, 2018. It is now read-only.
I think, that we should use always "can not" since documentation is usually written in formal language.
This also applies for all other short forms like for example "isn't".
Bear in mind that “can not” is ambiguous in some locales; in consequence, it should never be; the unambiguous “cannot” should instead be used.
I contest that documentation is usually or should be written in rigidly formal language; I believe “can’t” to be entirely acceptable. (This simply leaves me ambivalent about which direction it goes.)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We're using "can't" and "can not" in error messages. I think for consistency we should settle on one.
The text was updated successfully, but these errors were encountered: