Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

emails: Fix two grammar nits. #5667

Closed
wants to merge 1 commit into from
Closed

Conversation

jrowan
Copy link
Collaborator

@jrowan jrowan commented Jul 3, 2017

No description provided.

@smarx
Copy link

smarx commented Jul 3, 2017

Automated message from Dropbox CLA bot

@jrowan, it looks like you've already signed the Dropbox CLA. Thanks!

@jrowan
Copy link
Collaborator Author

jrowan commented Jul 3, 2017

As a related question/nit, we use both the space-around style -- like this -- and the directly-abutting style--this one--for em dashes, even within those that are spelled out as — in an html setting (it varies by email/place in the documentation). For plain text emails, the spaces look good, so maybe we should default to spaces everywhere (this is what the Associated Press style guide recommends, but most other ones suggest no spaces around the em dash). Maybe it's worth documenting a set of rules for grammar/usage/spelling of copy and help text somewhere the way we do for code style.

@timabbott
Copy link
Sponsor Member

Sounds reasonable to me. We could start with a text style guide in docs/text-style.md and grow it over time. @synicalsyntax FYI, you may be interested in this concept as well.

@timabbott
Copy link
Sponsor Member

Merged, thanks @jrowan!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants