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 has been archived by the owner on Jul 19, 2020. It is now read-only.
To standardise the documentation and give a coherent and consistent reading for all readers, I think we should adopt a style guide (on a very informal basis – i.e. this is ideally what we want our documentation to look like but we'd rather have documentation not in keeping with the style guide than no documentation).
Something like The Chicago Manual of Style or Hart's Rules would do the trick.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
To standardise the documentation and give a coherent and consistent reading for all readers, I think we should adopt a style guide (on a very informal basis – i.e. this is ideally what we want our documentation to look like but we'd rather have documentation not in keeping with the style guide than no documentation).
Something like The Chicago Manual of Style or Hart's Rules would do the trick.
The text was updated successfully, but these errors were encountered: