Annoying Orange Wiki

Welcome to the Annoying Orange Wiki! We are happy that you are here. Before you start editing, make sure you know the Wiki Rules. We also have a discord server in case you just want to hang out!

READ MORE

Annoying Orange Wiki
Register
No edit summary
No edit summary
Tag: Visual edit
 
(42 intermediate revisions by 3 users not shown)
Line 1: Line 1:
  +
{{Alert|You MUST Read This Page Before Contributing To The Wiki}}
{{WIP
 
|User=MHLU
 
}}Since top-contributors [[User:MHLU|MHLU]] and [[User:Brainulator9|Brainulator9]] were tired of users (especially anonymous users) making mistakes and having to clean-up after them, they decided that users read and follow the new policy, '''Manual of Style.'''
 
   
 
The '''Manual of Style''' is a guide that is pertinent to all articles created that fall under the scope of {{SITENAME}}. It helps clarify the content and makes the encyclopedia much more simple for fans of The Annoying Orange to read. The goal is to make the entire encyclopedia more convenient for contributors to use.
In their opinion, not following the Manual of Style deliberately is still considered a kind of spam. It takes three chances before a user can be blocked from editing; however, indefinite blocks '''cannot''' be made by violating the Manual of Style. However, this is not required on talk pages or non-article edits (see below).
 
   
 
In their opinion, not following the Manual of Style deliberately is still considered a kind of spam. It takes a user three chances before they can be blocked from editing due to disruption. However, this is not required on talk pages or non-article edits (see below).
==The Manual of Style==
 
   
 
==Basic principles==
===Introduction===
 
 
===Language===
 
An encyclopedic article is an article for readers to study. The writing is ''not'' for showing off one's exceptional way of writing, even if it is the purpose that you write here.
   
 
===Spelling===
''"This wiki has been around since 2010. It is still a growing wiki. Read the [[Template:Notice|notice template]] for more information.<br />This wiki has at least ten edits of vandalism daily, mostly from unregistered contributors. It would be very helpful if people followed my guide."<br />-MHLU''
 
 
'''Wikia does not have a spell checker.''' Remember to check your spelling before publishing an article, as if you were at school (checking a writing assignment before turning the paper in). The following demonstrates:<br />'''Unacceptable: '''<font color="red">Orange iz uh mane charicter form da Anoyng Orang seris.</font><br />'''Acceptable: '''<font color="green">Orange is a main character from the Annoying Orange series. </font>
 
'''The Manual of Style''' is a guide that is pertinent to all Annoying Orange Wiki articles. It helps clarify the language and makes the encyclopedia much easier for Annoying Orange fans to read. The goal is to make the whole encyclopedia much easier for contributors to use.
 
 
===Basic principles===
 
====Language====
 
An encyclopedic article is an article for readers to study. The writing is ''not'' for showing off one's exceptional way of writing, even if it is the purpose that you write here.
 
=====Spelling=====
 
'''Wikia does not have a spell checker.''' Remember to check your spelling before publishing an article, as if you were at school (checking a writing assignment before turning the paper in). The following demonstrates:<br />'''Unacceptable: '''<font color="red">Orange is a mane charicter form the Annoyng Orang seris.</font><br />'''Acceptable: '''<font color="green">Orange is a main character from the Annoying Orange series. </font>
 
   
 
Therefore, if you do not check your spelling, your edit will be undone, and you will be [[Annoying Orange Wiki:Warning vandals|warned]] if you have more than two major mistakes.
 
Therefore, if you do not check your spelling, your edit will be undone, and you will be [[Annoying Orange Wiki:Warning vandals|warned]] if you have more than two major mistakes.
   
=====Grammar=====
+
===Grammar===
 
Just the old-school way: capitalize your I's, end your sentences with punctuation, and do not use the wrong homophone. Grammar can be easily remembered with spelling.
 
Just the old-school way: capitalize your I's, end your sentences with punctuation, and do not use the wrong homophone. Grammar can be easily remembered with spelling.
   
Line 28: Line 21:
 
Therefore, if you do not check your grammar concisely, the same consequences will happen (you will be warned). This is part of this guideline that can ''also'' be counted as vandalism.
 
Therefore, if you do not check your grammar concisely, the same consequences will happen (you will be warned). This is part of this guideline that can ''also'' be counted as vandalism.
   
=====Clear, consise wording=====
+
===Clear, consise wording===
As stated above, articles are not to show off someone's exceptional English. The example below shows what is unacceptable and what can be used on an article (Elephant)<br />'''Unacceptable''': <font color="red">'''Pachyderm''' was a momentous titanic pachyderm that came into view in ''Elephants are Huge''.</font><br />'''Acceptable''': <font color="green">'''Elephant''' was a extremely giant pachyderm that first appeared in ''Elephants are Huge''.</font>
+
As stated above, articles are not to show off someone's exceptional English. The example below shows what is unacceptable and what can be used on an article (Elephant).<br />'''Unacceptable''': <font color="red">'''Pachyderm''' was a momentous titanic pachyderm that came into view in ''Elephants are Huge''.</font><br />'''Acceptable''': <font color="green">'''Elephant''' was an extremely giant pachyderm that first appeared in ''Elephants are Huge''.</font>
   
 
Therefore, don't overload an article with technically advanced English, because youngsters and people understanding basic English occassionally read an encyclopedia.
 
Therefore, don't overload an article with technically advanced English, because youngsters and people understanding basic English occassionally read an encyclopedia.
   
===Article titles, headings, and sections===
+
==Article titles, headings, and sections==
====Article titles====
+
===Article titles===
 
The rule about article titles is violated very often, even by registered users and administrators. The rules are as follows:
 
The rule about article titles is violated very often, even by registered users and administrators. The rules are as follows:
 
*Capitalize the beginning of the title.
 
*Capitalize the beginning of the title.
 
*The title should be a clear match of an article's contents (therefore, don't put "Clementine" if the article is about a lemon).
 
*The title should be a clear match of an article's contents (therefore, don't put "Clementine" if the article is about a lemon).
*The intial (first) letter of the title is capitalized, unless in rare cases, such as ''iPhone''.
+
*The initial (first) letter of the title is capitalized, unless in rare cases, such as ''iPhone''.
*Capital letters are only supposed to be used only in where they would in normal sentences (<font color="green">Grandpa Lemon's motorcycle</font>, not <font color="red">Grandpa Lemon's Motorcycle</font> unless it is a character's name (<font color="green">Bunny Rabbit</font>).
+
*Capital letters are only supposed to be used only in where they would in normal sentences (<font color="green">Grandpa Lemon's motorcycle</font>, not <font color="red">Grandpa Lemon's Motorcycle</font>) unless it is a character's name (<font color="green">Bunny Rabbit</font>).
 
*'''Like in library searches''', do not start a title with the words ''a'', ''an'', or ''the'' unless it is a proper title (<font color="green">The Annoying Orange</font>).
 
*'''Like in library searches''', do not start a title with the words ''a'', ''an'', or ''the'' unless it is a proper title (<font color="green">The Annoying Orange</font>).
 
*Titles should be short (<font color="green">Orange</font>, not <font color="red">Super Duper Irritating Annoying Orange</font>).
 
*Titles should be short (<font color="green">Orange</font>, not <font color="red">Super Duper Irritating Annoying Orange</font>).
 
*Avoid special characters (/, +, {}, []), use ''and'' instead of ''&'', unless the ampersand is part of a name (<font color="green">Steinway & Sons</font>).
 
*Avoid special characters (/, +, {}, []), use ''and'' instead of ''&'', unless the ampersand is part of a name (<font color="green">Steinway & Sons</font>).
   
==== Section headings ====
+
=== Section headings ===
 
Headings provide an overview in the table of contents and allow readers to navigate through the text more easily.
 
Headings provide an overview in the table of contents and allow readers to navigate through the text more easily.
 
* Section and subsection headings should preferably be unique within a page; otherwise, after editing, the display can arrive at the wrong section (see also below) and the automatic edit summary can be ambiguous.
 
* Section and subsection headings should preferably be unique within a page; otherwise, after editing, the display can arrive at the wrong section (see also below) and the automatic edit summary can be ambiguous.
Line 51: Line 44:
 
* Spaced or unspaced multiple equal signs are the style markup for headings. The triple apostrophes (<code><nowiki>'''</nowiki></code>) that make words appear in boldface are not used in headings. The nesting hierarchy for headings is as follows:
 
* Spaced or unspaced multiple equal signs are the style markup for headings. The triple apostrophes (<code><nowiki>'''</nowiki></code>) that make words appear in boldface are not used in headings. The nesting hierarchy for headings is as follows:
 
** the automatically generated top-level heading of a page is H1, which gives the article title;
 
** the automatically generated top-level heading of a page is H1, which gives the article title;
** primary headings are then <code><nowiki>==H2==</nowiki></code>, <code><nowiki>===H3===</nowiki></code>, <code><nowiki>====H4====</nowiki></code>, and so on until the lowest-level heading <code><nowiki>======H6======</nowiki></code>.
+
** primary headings are then <code><nowiki>==H2==</nowiki></code>, <code><nowiki>==H3==</nowiki></code>, <code><nowiki>===H4===</nowiki></code>, and so on until the lowest-level heading <code><nowiki>===H6===</nowiki></code>.
 
* Spaces between the <code><nowiki>==</nowiki></code> and the heading text are optional (<code><nowiki>==H2==</nowiki></code> is equivalent to <code style="white-space: nowrap"><nowiki>== H2 ==</nowiki></code>). These extra spaces will not affect the way the heading is displayed to readers.
 
* Spaces between the <code><nowiki>==</nowiki></code> and the heading text are optional (<code><nowiki>==H2==</nowiki></code> is equivalent to <code style="white-space: nowrap"><nowiki>== H2 ==</nowiki></code>). These extra spaces will not affect the way the heading is displayed to readers.
 
* Include one blank line above the heading, for better readability in the edit window. Some editors also prefer an (optional) blank line below the heading. Only two or more blank lines above or below will add more white space in the public appearance of the page.
 
* Include one blank line above the heading, for better readability in the edit window. Some editors also prefer an (optional) blank line below the heading. Only two or more blank lines above or below will add more white space in the public appearance of the page.
  +
===Wording===
 
  +
==False information==
====Capital letters====
 
  +
Do '''not''' add poorly-sourced or false information; this is actually known as vandalism and can lead to a block.
 
==Wording==
 
===Capital letters===
 
There are differences between the major varieties of English in the use of capitals (uppercase letters). Where this is an issue, the rules and conventions of the cultural and linguistic context apply. As with spelling, maintain consistency within an article.
 
There are differences between the major varieties of English in the use of capitals (uppercase letters). Where this is an issue, the rules and conventions of the cultural and linguistic context apply. As with spelling, maintain consistency within an article.
 
Do not use capital letters for emphasis (<font color="red">Contrary to popular belief, aardvarks are NOT the same as anteaters.</font>); where wording alone cannot provide the emphasis, use italics (<font color="green">Contrary to popular belief, aardvarks are ''not'' the same as anteaters.</font>)
 
Do not use capital letters for emphasis (<font color="red">Contrary to popular belief, aardvarks are NOT the same as anteaters.</font>); where wording alone cannot provide the emphasis, use italics (<font color="green">Contrary to popular belief, aardvarks are ''not'' the same as anteaters.</font>)
   
====Use of "the"====
+
===Use of "the"===
 
Generally do not capitalize the definite article in the middle of a sentence. However, some idiomatic exceptions, including most titles of artistic works, should be quoted exactly according to common usage. Consider consulting the sources of the article.
 
Generally do not capitalize the definite article in the middle of a sentence. However, some idiomatic exceptions, including most titles of artistic works, should be quoted exactly according to common usage. Consider consulting the sources of the article.
   
Line 69: Line 65:
 
(exception): <font color="green">There are two seaside resorts in The Hague.</font>
 
(exception): <font color="green">There are two seaside resorts in The Hague.</font>
   
====Calendar wording====
+
===Calendar wording===
 
*'''Months, days of the week, and holidays''' start with a capital letter.
 
*'''Months, days of the week, and holidays''' start with a capital letter.
 
*Dates should not be written like <font color="red">8/23/2010</font>; instead <font color="green">23 August 2010</font> or <font color="green">August 23, 2010</font>.
 
*Dates should not be written like <font color="red">8/23/2010</font>; instead <font color="green">23 August 2010</font> or <font color="green">August 23, 2010</font>.
   
===Abbreviations===
+
==Abbreviations==
====Write down the full version and abbreviation and first occurance====
+
===Write down the full version and abbreviation and first occurance===
 
Therefore, if there happens to be an '''abbreviation''' in a sentence (e.g. United States), write the sentence in the form <font color="green">United States (US)</font>.
 
Therefore, if there happens to be an '''abbreviation''' in a sentence (e.g. United States), write the sentence in the form <font color="green">United States (US)</font>.
====Periods====
+
===Periods===
 
Do not add periods to abbreviations (we would appreciate <font color="green">PhD</font> over <font color="red">Ph.D</font>).
 
Do not add periods to abbreviations (we would appreciate <font color="green">PhD</font> over <font color="red">Ph.D</font>).
====Do not make up abbreviations====
+
===Do not make up abbreviations===
 
Do ''not'' make up unofficial abbreviations, therefore, if the page [[Fruit Basket]] was not officially abbreviated "FB", do not use <font color="red">FB</font>.
 
Do ''not'' make up unofficial abbreviations, therefore, if the page [[Fruit Basket]] was not officially abbreviated "FB", do not use <font color="red">FB</font>.
  +
  +
==Semicolons==
  +
'''This rule is violated ''very'' often.''' A semicolon (;) is sometimes an alternative to a full stop (period), enabling related material to be kept in the same sentence; it marks a more decisive division in a sentence than a comma. If the semicolon separates clauses, normally each clause must be independent (meaning that it could stand on its own as a sentence); often, only a comma or only a semicolon will be correct in a given sentence.
  +
  +
Correct: <font color="green">I never seen him before, but I recognize him.</font>
  +
<br />Incorrect: <font color="red">I never seen him before; but I recognize him.</font>
  +
<br />Correct: <font color="green">Oranges are an acid fruit; bananas are classified as alkaline.</font>
  +
<br />Incorrect: <font color="red">Oranges are an acid fruit, bananas are classified as alkaline.</font>
  +
  +
==First and second person==
  +
===First person===
  +
First person should ''never'' be used, as Annoying Orange Wiki articles are not subjective on someone's opinion, but it can be used during quotations (see the section [[Annoying Orange Wiki:Manual of Style#Quotations|Quotations]].)
  +
===Second person===
  +
  +
Use of second person (you) is very discouraged.
  +
  +
Incorrect: <font color="red">When you watch the video, you can see that Orange is annoying.</font>
  +
<br />Correct: <font color="green">When a viewer watches the video, he or she can see that Orange is annoying.</font>
  +
  +
==Varieties of English==
  +
Both varieties (UK and US) of English are accepted; therefore, if the English Annoying Orange Wiki articles are not your normal English, do not change it unnecessarily.
  +
  +
==Quotations==
  +
Use the symbol (") instead of <nowiki>('')</nowiki>, or this will italicize the text.
  +
  +
At the end and beginning of ''every'' quote, you should add quotation marks.
  +
  +
===Linking===
  +
Please try to avoid linking in quotes, which may clutter the quotation, violate the principle of leaving quotations unchanged, and mislead or confuse the reader.
  +
  +
==Slashes==
  +
The slash (/) should generally be avoided. Slashes should ''not'' be used to adjoin to words (<font color="red">orange/pear</font>). Instead, use the word "and" or "or".
  +
  +
==Number signs==
  +
Avoid the number-sign (#), instead use "No.". Also avoid the numero sign (№).
  +
  +
==Commas==
  +
Do not put spacing before commas, but rather after them. The same applies to any other period, semicolon, or quotation mark.
  +
  +
==Precise language==
  +
Do ''not'' add stuff in an article that will get out-of-date or age quickly (<font color"red">recently, soon, before). Instead, add the '''date'''.
  +
  +
==Numbers==
  +
*Render single-digit whole numbers from zero to nine as words.
  +
*Render numbers greater than nine as figures or, with consistency within each article, render numbers over nine that take two words or fewer to say as words (about five million people; 16 or sixteen; 84 or eighty-four; 200 or two hundred; but 3.75, 544, 21 million). Words may be preferable for approximations.
  +
*Render comparable quantities, mentioned together, either all as words or all as figures (5 cats and 32 dogs or five cats and thirty-two dogs, but not five cats and 32 dogs or 5 cats and thirty-two dogs).
  +
*Render differently (with words or figures) adjacent quantities that are not comparable (thirty-six 6.4-inch rifled guns, not 36 6.4-inch rifled guns).
  +
  +
==Comments==
  +
Usage of <nowiki><code><!-- Your text here --></code></nowiki>, replacing "Your text here" with a comment, will add an invisible comment to editors, but will not affect the appearance of any article. The comment can only be seen while in editing mode. They are '''<u>not</u>''' to be used often. Inappropriate comments inserted to pages will be removed.
  +
  +
Comments can also be used to make a part of an article invisible.
  +
<!-- Here's an example. -->
  +
  +
==Other information==
  +
*The templates used to warn the users about the Manual of Style can be seen [[Annoying Orange Wiki:Warning vandals|here]].
  +
*Please do not change the content without permission. If you happen to find an error on this page, please contact Brainulator9 before correcting it.
  +
  +
==See also==
  +
*[[User:Brainulator9]]
  +
*[[Annoying Orange Wiki:Not YouTube]] - a policy which also highlights the Manual of Style.
  +
  +
  +
[[Category:Annoying Orange Wiki|Manual of Style]]
  +
  +
__NOEDITSECTION__

Latest revision as of 21:16, 16 August 2020

Notice

You MUST Read This Page Before Contributing To The Wiki


The Manual of Style is a guide that is pertinent to all articles created that fall under the scope of Annoying Orange Wiki. It helps clarify the content and makes the encyclopedia much more simple for fans of The Annoying Orange to read. The goal is to make the entire encyclopedia more convenient for contributors to use.

In their opinion, not following the Manual of Style deliberately is still considered a kind of spam. It takes a user three chances before they can be blocked from editing due to disruption. However, this is not required on talk pages or non-article edits (see below).

Basic principles

Language

An encyclopedic article is an article for readers to study. The writing is not for showing off one's exceptional way of writing, even if it is the purpose that you write here.

Spelling

Wikia does not have a spell checker. Remember to check your spelling before publishing an article, as if you were at school (checking a writing assignment before turning the paper in). The following demonstrates:
Unacceptable: Orange iz uh mane charicter form da Anoyng Orang seris.
Acceptable: Orange is a main character from the Annoying Orange series.

Therefore, if you do not check your spelling, your edit will be undone, and you will be warned if you have more than two major mistakes.

Grammar

Just the old-school way: capitalize your I's, end your sentences with punctuation, and do not use the wrong homophone. Grammar can be easily remembered with spelling.

This is not like YouTube or Facebook. The following shows what's right and what is not:
Unacceptable: pear is a great guy. i think he is cool.
Acceptable: Pear is a great character; I think he is cool.

Therefore, if you do not check your grammar concisely, the same consequences will happen (you will be warned). This is part of this guideline that can also be counted as vandalism.

Clear, consise wording

As stated above, articles are not to show off someone's exceptional English. The example below shows what is unacceptable and what can be used on an article (Elephant).
Unacceptable: Pachyderm was a momentous titanic pachyderm that came into view in Elephants are Huge.
Acceptable: Elephant was an extremely giant pachyderm that first appeared in Elephants are Huge.

Therefore, don't overload an article with technically advanced English, because youngsters and people understanding basic English occassionally read an encyclopedia.

Article titles, headings, and sections

Article titles

The rule about article titles is violated very often, even by registered users and administrators. The rules are as follows:

  • Capitalize the beginning of the title.
  • The title should be a clear match of an article's contents (therefore, don't put "Clementine" if the article is about a lemon).
  • The initial (first) letter of the title is capitalized, unless in rare cases, such as iPhone.
  • Capital letters are only supposed to be used only in where they would in normal sentences (Grandpa Lemon's motorcycle, not Grandpa Lemon's Motorcycle) unless it is a character's name (Bunny Rabbit).
  • Like in library searches, do not start a title with the words a, an, or the unless it is a proper title (The Annoying Orange).
  • Titles should be short (Orange, not Super Duper Irritating Annoying Orange).
  • Avoid special characters (/, +, {}, []), use and instead of &, unless the ampersand is part of a name (Steinway & Sons).

Section headings

Headings provide an overview in the table of contents and allow readers to navigate through the text more easily.

  • Section and subsection headings should preferably be unique within a page; otherwise, after editing, the display can arrive at the wrong section (see also below) and the automatic edit summary can be ambiguous.
  • Headings should not normally contain links, especially where only part of a heading is linked.
  • Headings should not explicitly refer to the subject of the article, or to higher-level headings, unless doing so is shorter or clearer (Biography) is preferable to His biography when his refers to the subject of the article; headings can be assumed to be about the subject unless otherwise indicated).
  • Spaced or unspaced multiple equal signs are the style markup for headings. The triple apostrophes (''') that make words appear in boldface are not used in headings. The nesting hierarchy for headings is as follows:
    • the automatically generated top-level heading of a page is H1, which gives the article title;
    • primary headings are then ==H2==, ==H3==, ===H4===, and so on until the lowest-level heading ===H6===.
  • Spaces between the == and the heading text are optional (==H2== is equivalent to == H2 ==). These extra spaces will not affect the way the heading is displayed to readers.
  • Include one blank line above the heading, for better readability in the edit window. Some editors also prefer an (optional) blank line below the heading. Only two or more blank lines above or below will add more white space in the public appearance of the page.

False information

Do not add poorly-sourced or false information; this is actually known as vandalism and can lead to a block.

Wording

Capital letters

There are differences between the major varieties of English in the use of capitals (uppercase letters). Where this is an issue, the rules and conventions of the cultural and linguistic context apply. As with spelling, maintain consistency within an article. Do not use capital letters for emphasis (Contrary to popular belief, aardvarks are NOT the same as anteaters.); where wording alone cannot provide the emphasis, use italics (Contrary to popular belief, aardvarks are not the same as anteaters.)

Use of "the"

Generally do not capitalize the definite article in the middle of a sentence. However, some idiomatic exceptions, including most titles of artistic works, should be quoted exactly according to common usage. Consider consulting the sources of the article.

Incorrect (generic): There was an article about The United States in yesterday's newspaper.
Correct (generic): There was an article about the United States in yesterday's newspaper.
Incorrect (title): Dane Boedigheimer made the Annoying Orange.
Correct (title): Dane Boedigheimer made The Annoying Orange.
Correct (title): Homer wrote the Odyssey.
Incorrect (exception): There are two seaside resorts in the Hague.
Correct (exception): There are two seaside resorts in The Hague.

Calendar wording

  • Months, days of the week, and holidays start with a capital letter.
  • Dates should not be written like 8/23/2010; instead 23 August 2010 or August 23, 2010.

Abbreviations

Write down the full version and abbreviation and first occurance

Therefore, if there happens to be an abbreviation in a sentence (e.g. United States), write the sentence in the form United States (US).

Periods

Do not add periods to abbreviations (we would appreciate PhD over Ph.D).

Do not make up abbreviations

Do not make up unofficial abbreviations, therefore, if the page Fruit Basket was not officially abbreviated "FB", do not use FB.

Semicolons

This rule is violated very often. A semicolon (;) is sometimes an alternative to a full stop (period), enabling related material to be kept in the same sentence; it marks a more decisive division in a sentence than a comma. If the semicolon separates clauses, normally each clause must be independent (meaning that it could stand on its own as a sentence); often, only a comma or only a semicolon will be correct in a given sentence.

Correct: I never seen him before, but I recognize him.
Incorrect: I never seen him before; but I recognize him.
Correct: Oranges are an acid fruit; bananas are classified as alkaline.
Incorrect: Oranges are an acid fruit, bananas are classified as alkaline.

First and second person

First person

First person should never be used, as Annoying Orange Wiki articles are not subjective on someone's opinion, but it can be used during quotations (see the section Quotations.)

Second person

Use of second person (you) is very discouraged.

Incorrect: When you watch the video, you can see that Orange is annoying.
Correct: When a viewer watches the video, he or she can see that Orange is annoying.

Varieties of English

Both varieties (UK and US) of English are accepted; therefore, if the English Annoying Orange Wiki articles are not your normal English, do not change it unnecessarily.

Quotations

Use the symbol (") instead of (''), or this will italicize the text.

At the end and beginning of every quote, you should add quotation marks.

Linking

Please try to avoid linking in quotes, which may clutter the quotation, violate the principle of leaving quotations unchanged, and mislead or confuse the reader.

Slashes

The slash (/) should generally be avoided. Slashes should not be used to adjoin to words (orange/pear). Instead, use the word "and" or "or".

Number signs

Avoid the number-sign (#), instead use "No.". Also avoid the numero sign (№).

Commas

Do not put spacing before commas, but rather after them. The same applies to any other period, semicolon, or quotation mark.

Precise language

Do not add stuff in an article that will get out-of-date or age quickly (recently, soon, before). Instead, add the date.

Numbers

  • Render single-digit whole numbers from zero to nine as words.
  • Render numbers greater than nine as figures or, with consistency within each article, render numbers over nine that take two words or fewer to say as words (about five million people; 16 or sixteen; 84 or eighty-four; 200 or two hundred; but 3.75, 544, 21 million). Words may be preferable for approximations.
  • Render comparable quantities, mentioned together, either all as words or all as figures (5 cats and 32 dogs or five cats and thirty-two dogs, but not five cats and 32 dogs or 5 cats and thirty-two dogs).
  • Render differently (with words or figures) adjacent quantities that are not comparable (thirty-six 6.4-inch rifled guns, not 36 6.4-inch rifled guns).

Comments

Usage of <code><!-- Your text here --></code>, replacing "Your text here" with a comment, will add an invisible comment to editors, but will not affect the appearance of any article. The comment can only be seen while in editing mode. They are not to be used often. Inappropriate comments inserted to pages will be removed.

Comments can also be used to make a part of an article invisible.

Other information

  • The templates used to warn the users about the Manual of Style can be seen here.
  • Please do not change the content without permission. If you happen to find an error on this page, please contact Brainulator9 before correcting it.

See also