diff --git a/_includes/writing/language.html b/_includes/writing/language.html index cb4dfe4..d780ad0 100644 --- a/_includes/writing/language.html +++ b/_includes/writing/language.html @@ -11,13 +11,14 @@
Don't use apostrophes for plural abbreviations.
Don't use i.e. or e.g.; they are not localization-friendly.
Use bold text to draw the reader's eye to key phrases and statements in your email and web content. For product copy or help articles, use bold for static UI elements like menu items, buttons, screen headings, and anything else you want to call attention to.
@@ -30,14 +31,14 @@Use sentence case in all titles, headings, menu items, labels, and buttons.
Use colons to introduce a bulleted list or series of steps. Don't use colons at the end of headings.
In keeping with our more conversational, friendly voice, use contractions.
+While we are not using exactly casual language, we want to stay consistent with our friendly voice, so use contractions.
Quote with quotes, not italics.
Avoid exclamation marks! They should only be used for exciting or new things! At the most, there should only be one exclamation mark per page!
When possible, avoid gendered pronouns. If you can't, then they or their is preferable to his or her or he or she.
Not sure if it's coworker or co-worker? See the Word List (coming soon!)
Use different verbs depending on what you're telling the user to do:
Yes:
Use lists to draw the reader's eye and make items easier to scan and follow. Use proper punctuation in your items if they are complete sentences. Try to limit lists to six items or fewer. If you need more items, see if you can split the list into multiple lists.
Use bulleted lists for options, or a list where the order of the items doesn't matter. Phrase each item in a parallel way. If the bullets complete the introductory sentence, start the fragments with lowercase and skip the periods.
Yes:
-Due to security concerns, all employees are now required to:
+Due to security concerns, everyone is now required to:
No:
-Due to security concerns, all employees are now required to follow the regulations below:
+Due to security concerns, everyone is now required to follow the regulations below:
To add a new user macro:
Use monospaced font for names of a file or directory. It is mostly used in administrator and developer docs. For example:
-The location of the Home directory is stored in a configuration file called confluence-init.properties
, which is located in the confluence/WEB-INF/classes
directory in your Confluence Installation directory.
Write out numbers one through ten. After ten, you can use 11, 12, 108, and so on.
-Can't remember if it's filesystem or file system? Check out the Word List (coming soon!)
Use the Oxford or serial comma to offset the final item in a list.
In most cases, second person is best. It fits Atlassian's casual, conversational tone to refer to the reader directly. Exceptions can be made for specific types of writing, such as whitepapers and press releases.
-Not sure whether it's My projects or Your projects? It can be fuzzy, so sometimes, we aren't either! For best results, avoid using mine, my, or your in UI copy.
+In most cases, second person is best. Exceptions can be made for specific types of writing, such as whitepapers and press releases.
+Not sure whether it's My projects or Your projects? For best results, avoid using mine, my, or your in UI copy.
If you need to use mine, my, or your, the rule of thumb is to think of the UI as a conversation between the system and the user.
If the system is presenting information to the user, such as in a dialog box, then your is more appropriate, because it's like saying "Here are your things", or "What would you like to do?"
If the user is performing an action, such as clicking a button or a link, then mine/my is more appropriate, because it's like saying "Show me my stuff!".
Use double quotes (") for a direct quote. For UI elements, page titles, and other objects, use bold text or italics as appropriate.
@@ -175,7 +169,7 @@Use sentence case for . Don't use bold, italics, or standard punctuation in headings. It's ok to use question marks and exclamation points if they fit the criteria for those two marvelous pieces of punctuation.
+Use sentence case. Don't use bold, italics, or standard punctuation in headings. It's ok to use question marks and exclamation points if they fit the criteria for those two marvelous pieces of punctuation.
Go to More ••• > Link issues.
We write with US English spelling and punctuation, but our Australian roots are still part of our personality. Communications directly from native Aussies can use the Queen's English – e.g., colour, optimise, theatre.
-For example, Aussie PMs writing JAC comments to customers can use Australian English. Developers should code in US English.
+We write with US English spelling and punctuation. Developers should code in US English.
We follow the AP Style Guide.
- -