Wikipedia's Manual of Style contains some conventions that differ from those in some other, well-known style guides and from what is often taught in schools. Wikipedia's editors have discussed these conventions in great detail and have reached consensus that these conventions serve our purposes best. New contributors are advised to check the FAQ and the archives to see if their concern has already been discussed.
Why does the Manual of Style recommend straight (keyboard-style) instead of curly (typographic) quotation marks and apostrophes (i.e., the characters " and ', instead of “, ”, ‘, and ’)?
Users may only know how to type in straight quotes (such as " and ') when searching for text within a page or when editing. Not all web browsers find curly quotes when users type straight quotes in search strings.
This system is preferred because Wikipedia, as an international and electronic encyclopedia, has specific needs better addressed by logical quotation than by the other styles, despite the tendency of externally published style guides to recommend the latter. These include the distinct typesetters' style (often called American, though not limited to the US), and the various British/Commonwealth styles, which are superficially similar to logical quotation but have some characteristics of typesetters' style. Logical quotation is more in keeping with the principle of minimal change to quotations, and is less prone to misquotation, ambiguity, and the introduction of errors in subsequent editing, than the alternatives. Logical quotation was adopted in 2005, and has been the subject of perennial debate that has not changed this consensus.
Why does the Manual of Style differentiate the hyphen (-), en dash (–), em dash (—), and minus sign (−)?
Appropriate use of hyphens and dashes is as much a part of literate, easy-to-read writing as are correct spelling and capitalization. The "Insert" editing tools directly below the Wikipedia editing window provide immediate access to all these characters.
Why does the Manual of Style recommend apostrophe+s for singular possessive of names ending in s?
Most modern style guides treat names ending with s just like other singular nouns when forming the possessive. The few that do not propose mutually contradictory alternatives. Numerous discussions have led to the current MoS guidance (see discussions of 2004, 2005, 2005, 2006, 2006, 2007, 2008, 2008, 2008, 2009, 2009, 2009, 2012, 2013, 2015, 2016, 2017, 2017, 2017 (the RfC establishing the present consensus), 2018, 2018, 2019, 2021,
2022).
Why doesn't the Manual of Style always follow specialized practice?
Although Wikipedia contains some highly technical content, it is written for a general audience. While specialized publications in a field, such as academic journals, are excellent sources for facts, they are not always the best sources for or examples of how to present those facts to non-experts. When adopting style recommendations from external sources, the Manual of Style incorporates a substantial number of practices from technical standards and field-specific academic style guides; however, Wikipedia defaults to preferring general-audience sources on style, especially when a specialized preference may conflict with most readers' expectations, and when different disciplines use conflicting styles.
This page falls within the scope of the Wikipedia:Manual of Style, a collaborative effort focused on enhancing clarity, consistency, and cohesiveness across the Manual of Style (MoS) guidelines by addressing inconsistencies, refining language, and integrating guidance effectively.Manual of StyleWikipedia:WikiProject Manual of StyleTemplate:WikiProject Manual of StyleManual of Style
This page may fall under the contentious topics procedure and be given additional attention, as it may be closely associated to the article titles policy and capitalisation. Both areas are subjects of debate. Contributors are urged to review the awareness criteria carefully and exercise caution when editing.
This page is within the scope of the Wikipedia Help Project, a collaborative effort to improve Wikipedia's help documentation for readers and contributors. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks. To browse help related resources see the Help Menu or Help Directory. Or ask for help on your talk page and a volunteer will visit you there.Wikipedia HelpWikipedia:Help ProjectTemplate:Wikipedia Help ProjectHelp
Add a link to new discussions at top of list and indicate what kind of discussion it is (move request, RfC, open discussion, deletion discussion, etc.). Follow the links to participate, if interested. Move to Concluded when decided, and summarize conclusion. Please keep this section at the top of the page.
Talk:Fun (band)#RfC on article tense – RfC (June–July 2025) on whether to refer to an inactive, but not apparently disbanded band in the present or past tense. Result: Modest participation discussion stalled, no conclusion.
RfC needed on issue raised at Wikipedia talk:Manual of Style/Biography/2024 archive#British peer titles in infoboxes (June–July 2004, archived without resolution). Presently, the royalty/nobility wikiprojects have imposed putting British peerage titles in place of names in biographical infoboxes, against MOS:BIO, MOS:INFOBOX, and the template's documentation. Either the community will accept this as a best practice and the guidelines changed to accomodate it, or it should be undone and the infobox used consistently and as-intended.
Talk:Second Italo-Ethiopian War#Flags in the infobox – a MOS:FLAGICONS matter (Nov.–Dec. 2024) Result: No formal closure, but article has been stable for a while with flag icons in the infobox, whether or not this conforms with the relevant guideline. This is the opposite of the result at "Battle of Tory Island", below.
Various simultaneously executed RMs by the same proponent all concluded against the desired over-stylizations (usually ALL-CAPS) – some by affirmative consensus against, some by no consensus to move.
Talk:Shays's Rebellion#Requested move 27 April 2024 – MOS:POSS: "Shays'" or "Shays's"? Result: "Shays's". No objective rationale was presented for an exception to the guideline, and evidence shows "Shays's" common in source material even if "Shays'" is also common, especially in older sources.
Template talk:Infobox university/Archive 23#Type – Should multiple entries be formatted as a list or a single phrase? (Apr.–May 2024) Result: 4:1 against proposed change to a list format; alternative idea at end neither accepted nor rejected.
Wikipedia talk:Image use policy/Archive 16#Collages in infoboxes – Primarily on a recent habit of military-conflict articles having collages of 4, 6, or even more images in their infobox. (Mar.–May 2024) Result: No formal closure, but a clear consensus against this practice; image galleries (when appropriate at all per WP:GALLERY) belong in the article body.
Wikipedia:Requests for comment/Names of deceased trans people (moved from WP:VPPOL) – Yet another round of this long-term, multi-RfC process. Consensus about "deadnames" seemed possible this time but was mostly elusive. (Dec. 2023 – Jan. 2024) Result: no consensus to change the wording of MOS:GENDERID based on this proposal; consensus against changing "should be included" to "may be included".
Related: See numerous previous deadname-related and more general GENDERID discussions listed below.
Wikipedia talk:Article titles/Archive 61#Request for comment on the relationship between WP:CRITERIA and WP:TITLEFORMAT – has stylistic implications (punctuation, leading "The", etc.) despite not being intrinsically an MoS matter (Nov. 2024) Result: "There is consensus that WP:TITLEFORMAT does not take precedence over WP:CRITERIA. Editors should continue to balance all relevant guidelines and policies when determining article titles, without giving inherent precedence to either section."
Wikipedia talk:Manual of Style/Accessibility/Archive 16#Making redundant table captions screen-reader-only – About use of {{sronly}} around table captions (which are primarily for screen readers) to hide them from the usual non-screen-reader view, only when their content repeats what is in the table headers. (Nov.–Dec. 2023) Result: Archived without firm resolion. As there was but one opposer of the idea, there is no consensus against doing this. If more opposition arose or some reason, open an RfC about it.
Wikipedia talk:Manual of Style/Trademarks#Minor consolidation merge – To merge a line-item (about stylization of stage/pen names) out of MOS:INITIALS (where the one of the examples is only semi-pertinent anyway) and into MOS:TM, leaving behind a cross-reference to MOS:TM from MOS:NAMES. (Nov.–Dec. 2023) Result: Because of some things that apply to personal not corporate names, this ended up not being practical; intead the MOS:BIO material was cleaned up and cross-references between the two MOS sections was improved; description at: Wikipedia talk:Manual of Style/Biography#Minor overhauling. No objections or other issues have come up.
Wikipedia talk:Manual of Style/Dates and numbers#MOS style for odds – About changing MOS:RATIOS to specify a format (new or otherwise) for betting-odds ratios. (Oct.–Dec. 2023) Result: No formal closure, but apparent general agreement that the : style for ratios in general applies to odds ratio in particular like the rest, and MOS:RATIOS updated to say this.
Wikipedia:Village pump (policy)/Archive 187#Proposed change MOS:TERRORIST – On how WP uses terms like "terrorist/terrorism" and "freedom fighter", specifically to add a requirement "these words should only be used in quotations or referencing third-party use of the term". (Oct. 2023) Result: "nearly unanimously opposed".
Talk:2023 Hawaii wildfires/Archive 2#Use of Hawaiian symbols in names – Involves MOS:HAWAII and could have implications for what the guideline says due to wildfire news bringing many more editorial eyes to that page than to WT:MOSHAWAII. (Aug.–Sep. 2023) Result: Archived without closure or any clear consensus; the general gist seems to be that the state of Hawaii is named Hawaii, the island is named Hawaiʻi, and diacritics (ʻokina and kahakō) should not be suppressed in the more localized names (and the US Geological Survey, which sets official placenames, along with the Hawaiʻi Board on Geographic Names, which basically tells USGS what to do in Hawaii/Hawaiʻi, both agree).
Talk:Bayes' theorem#Requested move 23 August 2023 – MOS:POSS stuff. (Aug. 2023) Result: Not moved. Lots of invalid arguments, and confused attempt to pit WP:COMMONAME against MoS (COMMONNAME is not a style policy, never has been one, and never will be; every proposal to incorporate a style matter into a policy has failed).
Wikipedia:Help desk/Archives/2023 August 5#Hyphen vs. En dash usage (Wikidata)? and d:Wikidata:Project chat/Archive/2023/08#Hyphen vs. En dash to separate years of birth/death? – Relating to concordance between wikidata descriptions and enwiki "short description". (Aug. 2023) Result: Good summary: "as long as you choose a comprehensible form, your edits are fine. However, you should not change existing descriptions for stylistic reasons, and also not to unify desriptions for a given set of items"; also observations that various languages, e.g. Spanish, do not use an en dash for this purpose. So, Wikidata will not be changing away from hyphen as default, and any desire to have WD material, like automatically provided short descriptions, will have to do that change on our end.
Talk:SAG-AFTRA#Requested move 20 July 2023 – move to SAG–AFTRA like AFL–CIO, or is there a reason to hyphenate as SAG-AFTRA? (July 2023) Result: Not moved. The closer actually misunderstood the guideline wording badly, and this has created a WP:CONSISTENT policy failure with titles of other such entities including AFL–CIO, and the Famous Players-Lasky decision covered just below. This probably needs to be re-done.
Talk:Famous Players-Lasky#Requested move 24 June 2023 – proposal to use dash instead of hyphen. (June–July 2023) Result: Use the dash per MOS:DASH; a followup RM to add "Corporation" to the title rejected that idea despite WP:NCCORP supporting it, one of several recent RM incidents suggesting that at least some portions of the page do not enjoy consensus.
Wikipedia:Village pump (policy)/Archive 182#RFC: MOS:GENDERID and the deadnames of deceased trans and nonbinary persons – Primarily about "When should Wikipedia articles include the former name of a deceased trans or nonbinary person who was not notable prior to transitioning?" (May–June 2023) Result: "there is a consensus against using the former names of transgender or non-binary people, living or dead, except when of encyclopedic interest or when necessary to avoid confusion. Also, there is clear consensus that a former name is not automatically of encyclopedic interest. Where, exactly, the lines of encyclopedic interest and avoiding confusion are is not simple or clear and will likely need discussion on individual articles, although there is definitely space for more guidance in the MOS". This has let to a lot of follow-on discussion and dispute.
Talk:Where is Thumbkin#Requested move 13 March 2026 – lowercase "thumbkin"? Result: No change of capitalization (lowercase "is" as an incipit, uppercase "Thumbkin" as a proper name personification), question mark added
Talk:The States#Requested move 17 February 2026 – move disambiguation page to lowercase and/or redirect "The States" to a primary topic? Result: Redirected both uppercase and lowercase to United States as primary topic; "(disambiguation)" added to disambiguation page
Talk:Nrx#Requested move 12 January 2026 – use all-caps for this disambiguation page name? Result: Uppercase, as nearly all listed topics are uppercased abbreviations
Talk:Major Labels#Requested move 27 July 2025 – is it sufficiently clear that this is an article about a book rather than a group of companies? Result: Not moved; title is suitable for a published work
Talk:Niviarsiat#Requested move 25 July 2025 – should either "Northeast Greenland" or "Southern Greenland" start with a capital letter? Result: The capitalization question is not relevant to the chosen titles
Talk:Blair Babe#Requested move 4 July 2025 – lowercase "Babe" or "Babes"? Result: uppercase retained (not the primary focus of the discussion and not commented on in the closing remarks)
Talk:F1NN5TER#Capitalization – Should the online persona be called "F1NN5TER", "F1nn5ter" or "Finnster"? Result: Discussion started 24 March 2024 went stale after comments on 4 April 2024 suggesting "F1NN5TER" to be the usual form
Talk:Fullbore target rifle#Major rework – Is it too risky to ask people who are carrying firearms to use lowercase? Result: lowercase "rifle" in most contexts, and other fixes
Talk:1925 Tri-State tornado#Requested move 26 December 2024 – Was this the "1925 Tri-State tornado" or "Great Tri-State Tornado" or something else? (closed, then close withdrawn and reopened after a move review, then closed and voluntarily reopened again, then closed again, then another move review, which was closed as "moot" when a parallel RM was closed.)
Talk:Washington (tree)#Requested move 30 April 2025 (18 articles) – if renamed to "[Something] tree", should "tree" be capitalized? Result: Moved to uppercase as nominated, but no clear consensus established on the capitalization
Talk:Fall of Saigon/Archive 1#Names section and capitalisation – capitalisation of Vietnamese language names and capitalisation of their English translations? Result: Archived after comments observing inconsistency, so generally suggesting sentence case for terms in Vietnamese and capitalization for translated named days (e.g. "Liberation Day") in English
Talk:Xkcd#Requested move 29 March 2025 – Should something different be done about the way this article tries to put its title in all-lowercase? Result: Not moved.
Talk:Tri-State tornado outbreak#Requested move 18 December 2024 – Was this a "Tri-State tornado outbreak" or a "tri-state tornado outbreak"? Result: Year added ("1925 Tri-State tornado outbreak"), but no explicit conclusion was expressed about capitalization (an initial move to lowercase was changed by the closer to uppercase the next day), then a move review was opened; closed as "endorse".
It seems to me that “considered” is exactly the right way to express the actual state of affairs. “Is avoided” also implies that these considerations are followed, or alternately merely implies a pattern of behaviour that doesn’t necessarily extend to Wikipedia, which would render the clarification unnecessary. Anselm Schüler (talk) 01:32, 7 March 2026 (UTC)[reply]
MOS:DEFLIST: "... even though description list terms are not headings, they act like headings in some ways. In at least one regard however, they are not: description list term wikitext (;) should not be used to subdivide large sections or otherwise to obtain a boldfacing effect."
So I changed that template to use this markup which I believe to be correct:
|list='''Labor unions'''*[[International Association of Fire Fighters]]...
I believe it is exempt, and I believe an endorsements box meets the definition of a description list. Essentially every Wikipedia election page uses semi-colons instead of the three apostrophes. aesurias(ping me in your reply, or I won't see it) (talk) 14:52, 22 March 2026 (UTC)[reply]
This is not a description list: in a description list, the semicoloned item is a term and the one (and only one) those below it is a are definitions. In this case, as Trappist says, it's a heading (since it introduces a list of multiple items fitting into the category it declares), and bold markup should be used. If the mistake is common in a certain class of articles, it's understandable how it could have persisted, but the consensus represented by the MoS outweighs that of a small group within the Wiki. UndercoverClassicistT·C15:02, 22 March 2026 (UTC)[reply]
the semicoloned item is a term and the one (and only one) below it is a definition is not strictly true. In definition lists, a term (;) may have multiple definitions (:). This example is perfectly legitimate:
Fair point: amended. But agreed, that's not what's happening here: "International Association of Fire Fighters" is not in any way a definition of "Labor unions". UndercoverClassicistT·C17:13, 22 March 2026 (UTC)[reply]
I just don't get the argument here.. it's not a "pseudo-heading", it's literally in a box. The entire thing is "pseudo". The issue with pseudo-headings is that they aren't fake sections so they can't be navigated to. This is obviously not possible here either way. If you'd really like to spend your time going through 40,000 election pages changing endorsement boxes, I won't oppose it, but I think removing the semi-colons make the boxes comically spaced out and ugly. aesurias(ping me in your reply, or I won't see it) (talk) 21:12, 22 March 2026 (UTC)[reply]
@Aesurias: 40,000 election pages? Where did you get that number? According to this page, {{Endorsements_box}} is transcluded into 2430-ish pages. That number is confirmed by this page. This search of article space returns approximately 2330 articles that have an {{Endorsements box}} template. So, where does the 40,000 number come from?
In your revert of my edit at 2026 California gubernatorial election, claimed: Endorsements box uses a semi-colon because of spacing. You have brought that same objection to this discussion: I think removing the semi-colons make the boxes comically spaced out and ugly. What spacing are you talking about? Since you appear to be unwilling to explain further, I conducted a side-by-side experiment →. Is that the spacing that you find objectionable? Inspecting the two boxes in my browser (chrome latest / win 11 / desktop / vector legacy) the height from the top of first endorsements heading to the bottom of 'third endorser' is 148.33 for semicolon markup and 156.73 for bolding markup; a difference of 8.4. Chrome does not provide units for these measurements. The difference, visually and numerically, seems rather small to me.
Is this a question, a proposal, or just an observation? I don't think OS dates should be used without at least noting this, or having the Gregorian too. Johnbod (talk) 23:31, 22 March 2026 (UTC)[reply]
Or are you questioning why the Battle of Borodino (for example) gives the data as 7 September 1812 when contemporary Russian records would have recorded it as 26 August 1812? Which I guess suggests that you are proposing a new rule:
Events that occurred after 1582 but before the polity concerned adopted the Gregorian calendar should give both dates explicitly rather than in a footnete.
So this battle would be dated 7 September [O.S. 28 August ] 1812
And George Washington was born February 22 [O.S. February 12] 1732
IMO (for whatever that's worth), the Old Style dates should be given first, with the N.S. date in brackets, if it even needs including at all. The reason being, that if you are doing historical research and working with primary documents, it is helpful to have dates that accurately match the dates on the primary documents. It is NOT really helpful, at all, to have dates that were being used in other parts of the world at the time, but not in the place you're reading about. Because - who cares? (I will note there will be exceptions, of course, and George Washington's birthdate is one such notable one, because the N.S. birthdate is very widely known). ~2026-19011-03 (talk) 01:44, 27 March 2026 (UTC)[reply]
There is another template, {{Old Style to New Style}} (or, more usefully, {{OS2NS}}) which can do that. With that template, this battle is rendered as 28 August [7 September N.S.] 1812. In both cases of course, it is just a convenient way to format the output. Neither template calculates the other date from the given date, which would be a superbly useful enhancement if anyone is so inclined?
Repeated links cannot be included in this section; however, are links provided through templates also included in this rule? Sincerely, Qədir (talk) 01:53, 30 March 2026 (UTC)[reply]
No, because navboxes, both footer and side navboxes, are provided to only 30% of daily readers. They are not shown on mobile, the predominant reader option. They are still important components of original Wikipedia, offered to millions of readers a day, but a feature only shared by 30% of readers cannot replace the functional use of adding important relevant links to See also sections. Randy Kryn (talk) 10:02, 30 March 2026 (UTC)[reply]
I think the same as well; I opened this thread just because it's not explicitly stated in the rule. So it's probably applied this way, and if it's not written in the rule, there must be a reason for it (and this might be one of those reasons). Still, the guideline says "content", and templates are probably considered part of the article's content as well. Otherwise, if this is a loophole, it needs to be discussed. Sincerely, Qədir (talk) 10:12, 30 March 2026 (UTC)[reply]
There is some merit to the comment above, as it could be an issue for long articles. Still, I think it would be useful to add a note about this. Sincerely, Qədir (talk) 10:26, 30 March 2026 (UTC)[reply]
There seems to be some uncertainty about whether the name of a victim should be bolded in the lead of an event‑based article (for example, a disappearance, killing, or murder case). I have been told that bolding the name is not appropriate for event articles, but this appears to be applied inconsistently across Wikipedia. Many similar pages do bold the victim's name in the lead, and this has been the common practice on most articles of this type that I have seen. The admin who disagrees with the bolding is the first person I have ever encountered who does not support it. Every page I have seen, whether it is a redirect or not, has always bolded the name, even on event‑based articles, which is why this has come as a surprise.
In cases where the article title refers to an event involving a specific person, the person's name is closely tied to the subject, because the event is defined by what happened to them. Although the article is about the event, the event is still centred on the individual, and their identity is inseparable from the topic. For that reason, bolding the name seems reasonable and consistent with how many editors approach similar pages.
The issue is that editors are receiving conflicting guidance. If bolding is not appropriate for event‑based articles, then it would be helpful to have a clear, centralised consensus so that the approach is applied consistently. At the moment, if someone unbolds a name on one page, it is likely to be reverted on another, which makes it difficult for newer editors to know what the correct style is.
Could we clarify whether victim names in event‑based articles should be bolded or unbolded in the lead, and whether this should be applied consistently across all such pages? If there has been a previous discussion on this point, I would appreciate being directed to it. Thank you! ItsShandog (talk) 20:47, 30 March 2026 (UTC)[reply]
If an article is about an event involving a subject about which there is no main article, especially if the article is the target of a redirect, the subject should be in bold.
The example given in the MoS is Death of Azaria Chamberlain, which begins Azaria Chantel Loren Chamberlain (11 June 1980, Mount Isa – 17 August 1980, Uluru / Ayers Rock) was a nine-week-old Australian baby girl who was killed by a dingo on the night of 17 August 1980 during a family camping trip to Uluru (Ayers Rock) in the Northern Territory. (emphasis original). UndercoverClassicistT·C20:51, 30 March 2026 (UTC)[reply]
Mathematics has an RfC for possible consensus. A discussion is taking place regarding if the page should have short description. If you would like to participate in the discussion, you are invited to add your comments on the discussion page. Thank you. GeogSage (⚔Chat?⚔) 23:09, 30 March 2026 (UTC)[reply]
I don't want to be fussy, but I don't see why you posted this here. This really has nothing to do with MOS, and this page really doesn't need any extraneous traffic. EEng03:10, 1 April 2026 (UTC)[reply]