m (provides was an awkward verb for an inanimate style guide, it is more of an outline, and used independent clause to make the last sentence mroe clear. Easy-to-read was in the paragraph twice.) |
m (First time use in paragraph Fedora Documentation Style Guide should be spelled out, removed language that was "can be" "may be" to give clear message.) |
||
| Line 5: | Line 5: | ||
Writing high-quality documents easily understood by multiple readers is a difficult challenge. There are many different techniques that can be used in writing, and there are many different ways of writing the same information. In order to provide consistent, readable documentation, certain standards must be established. There are many different writing style guides that serve different purposes and audiences. Good style is something learned and practiced. | Writing high-quality documents easily understood by multiple readers is a difficult challenge. There are many different techniques that can be used in writing, and there are many different ways of writing the same information. In order to provide consistent, readable documentation, certain standards must be established. There are many different writing style guides that serve different purposes and audiences. Good style is something learned and practiced. | ||
The Fedora Documentation Project is tasked with producing friendly, easy-to-read documentation for a worldwide audience. This means writing clean, clear documents with great attention to differences in cultures and languages. The Fedora Documentation Style Guide outlines specific rules and recommendations for documentation contributors | The Fedora Documentation Project is tasked with producing friendly, easy-to-read documentation for a worldwide audience. This means writing clean, clear documents with great attention to differences in cultures and languages. The Fedora Documentation Style Guide outlines specific rules and recommendations for documentation contributors. The style guidelines standardize documentation of both technical and non-technical information, to increase readability and comprehension. | ||
The writers producing | The writers producing Fedora documentation come from a variety of backgrounds, each with different skill sets. Through use of the Fedora Documentation Style Guide, contributors produce and collaborate on documentation with consistent results. This style guide may vary from each contributor's familiar writing requirements. Practicing this guide will eventually become a comfortable standard with benefits outside of Fedora's documentation. This style guide will demonstrate the rules and guidelines it sets forth. | ||
This style guide borrows many ideas from the Associated Press (AP) Stylebook and The Chicago Manual of Style. It contains many differences from those guides that are intended to enhance the value of these documents for international readers and to better accommodate the technical nature of the Fedora documentation. In particular, this style guide adopts international standards for many common notations to avoid confusion among the different cultures that may benefit from Fedora's documentation. | This style guide borrows many ideas from the Associated Press (AP) Stylebook and The Chicago Manual of Style. It contains many differences from those guides that are intended to enhance the value of these documents for international readers and to better accommodate the technical nature of the Fedora documentation. In particular, this style guide adopts international standards for many common notations to avoid confusion among the different cultures that may benefit from Fedora's documentation. | ||
Revision as of 21:50, 18 September 2008
Introduction to Style
Writing high-quality documents easily understood by multiple readers is a difficult challenge. There are many different techniques that can be used in writing, and there are many different ways of writing the same information. In order to provide consistent, readable documentation, certain standards must be established. There are many different writing style guides that serve different purposes and audiences. Good style is something learned and practiced.
The Fedora Documentation Project is tasked with producing friendly, easy-to-read documentation for a worldwide audience. This means writing clean, clear documents with great attention to differences in cultures and languages. The Fedora Documentation Style Guide outlines specific rules and recommendations for documentation contributors. The style guidelines standardize documentation of both technical and non-technical information, to increase readability and comprehension.
The writers producing Fedora documentation come from a variety of backgrounds, each with different skill sets. Through use of the Fedora Documentation Style Guide, contributors produce and collaborate on documentation with consistent results. This style guide may vary from each contributor's familiar writing requirements. Practicing this guide will eventually become a comfortable standard with benefits outside of Fedora's documentation. This style guide will demonstrate the rules and guidelines it sets forth.
This style guide borrows many ideas from the Associated Press (AP) Stylebook and The Chicago Manual of Style. It contains many differences from those guides that are intended to enhance the value of these documents for international readers and to better accommodate the technical nature of the Fedora documentation. In particular, this style guide adopts international standards for many common notations to avoid confusion among the different cultures that may benefit from Fedora's documentation.