[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
slackdocs:styleguide [2012/09/04 07:17 (UTC)] – [Pages That Require Attention from an Admin] Capital letters in languages sycamorexslackdocs:styleguide [2012/09/05 16:13 (UTC)] – [A General Note on Style] hazel
Line 95: Line 95:
   * Write complete sentences and try to avoid grammatical errors. If English is not your native language, you can always get help from an English editor.   * Write complete sentences and try to avoid grammatical errors. If English is not your native language, you can always get help from an English editor.
   * Follow proper [[http://www.writersblock.ca/tips/monthtip/tipmar98.htm|capitalization rules]] for words in titles and headings.   * Follow proper [[http://www.writersblock.ca/tips/monthtip/tipmar98.htm|capitalization rules]] for words in titles and headings.
-  * Long passages of plain text are hard to read; always consider if something can be better expressed using a list format. Use numbered lists only for sequential operations, bulleted lists for options or examples (as shown here).+  * Long passages of plain text are hard to read; always consider if something can be better expressed using a list format. Use numbered lists only for sequential operations, bulleted lists for options or examples (as shown here). Sometimes a table or a flowchart can be useful.
   * If quoting computer output, reproduce it exactly, including spelling (which is usually American). Use %%<code></code>%% tags to enclose the output for better legibility.   * If quoting computer output, reproduce it exactly, including spelling (which is usually American). Use %%<code></code>%% tags to enclose the output for better legibility.
 +  * If your text has examples of key presses, use the %%<key></key>%% markup to make a visual impact. <key>Alt-F2</key> looks better than "''Alt-F2''".
 +  * Avoid the passive voice. Use it only when alternatives would be clumsy.
 +  * Try to avoid long-windedness. "To do x, use the -y option" or "To do x, type foo -y" reads better than "If you want foo to do x for you, you need to type foo -y".
  
  
 slackdocs:styleguide ()