Requested moves is a process for requesting the retitling (moving) of an article, template, or project page on Wikipedia. For information on retitling files, categories, and other items, see § When not to use this page.
Any autoconfirmed user can move a page using the "Move" option in the editing toolbar; see how to move a page for more information. If you have no reason to expect a dispute concerning a move, be bold and move the page; however, it may not always be possible or desirable to do this:
Technical reasons may prevent a move; for example, a page may already exist at the target title and require deletion, or the page may be protected from moves. In such cases, see § Requesting technical moves.
Requests to revert recent, undiscussed, controversial moves may be made at WP:RM/TR. If the new name has not become the stable title, the undiscussed move will be reverted. If the new name has become the stable title, a requested move will be needed to determine the article's proper location.
A page should not be moved and a new move discussion should not be opened when there is already an open move request on a talk page. Instead, please participate in the open discussion.
Unregistered and new (not yet autoconfirmed) users are unable to move pages.
Requests are typically processed after seven days. If consensus supports the move at or after this time, a reviewer will perform it. If there is a consensus not to move the page, the request will be closed as "not moved". When consensus remains unclear, the request may be relisted to allow more time, or closed as "no consensus". See Wikipedia:Requested moves/Closing instructions for more details on the process.
Wikipedia:Move review can be used to contest the outcome of a move request as long as all steps are followed. If a discussion on the closer's talk page does not resolve an issue, then a move review will evaluate the close of the move discussion to determine whether or not the contested close was reasonable and consistent with the spirit and intent of common practice, policies, and guidelines.
Autoconfirmed editors may move a page without discussion if all of the following apply:
No article exists at the new target title;
There has been no previous discussion about the title of the page that expressed any objection to a new title; and
It seems unlikely that anyone would reasonably disagree with the move.
If you disagree with a prior bold move, and the new title has not been in place for a long time, you may revert the move yourself. If you cannot revert the move for technical reasons, then you may
request a technical move.
If you are unable to complete a move for technical reasons, you can request a technical move below. This is the correct method if you tried to move a page, but you got an error message saying something like "You do not have permission to move this page, for the following reasons:..." or "This page could not be moved, for the following reason:..."
If you are here because you want an admin to approve of your new article or your proposed page move, you are in the wrong place.
Because you are autoconfirmed, you can move most pages yourself. Do not request technical assistance on this page if you can do it yourself.
If you need help determining whether it's okay to move the page to a different title, then please follow the instructions at the top of Wikipedia:Requested moves.
Please make sure you really need technical assistance before making a request here. In particular, if the target page is a redirect back to the source page that has only one revision, you can usually move the page normally.
To list a technical request: the Uncontroversial technical requests subsection and insert the following code at the bottom of the list, filling in pages and reason:
{{subst:RMassist|current page title|new title|reason=edit summary for the move}}
This will automatically insert a bullet and include your signature. Please do not edit the article's talk page.
To request a reversion of a recent undiscussed move: Review the guidelines at WP:RMUM of whether a reversion of an undiscussed move qualifies as uncontroversial and if so, the Requests to revert undiscussed moves subsection and insert the following code at the bottom of the list, filling in pages and reason:
{{subst:RMassist|current page title|new title|reason=edit summary for the move}}
This will automatically insert a bullet and include your signature. Please do not edit the article's talk page. Note that in some cases, clerks, such as administrators or page movers may determine that your request for a reversion does not pass the criteria and may move the request to the contested section or open a formal requested move discussion for potentially controversial moves on your behalf.
If you object to a proposal listed in the uncontroversial technical requests section, please move the request to the Contested technical requests section, append a note on the request elaborating on why, and sign with ~~~~. Consider pinging the requester to let them know about the objection.
If your technical request is contested, or if a contested request is left untouched without reply, create a requested move on the article talk and remove the request from the section here. The fastest and easiest way is to click the "discuss" button at the request, save the talk page, and remove the entry on this page. A bot will automatically remove contested requests after 72 hours of inactivity.
@Skynxnex It appears you are right. I just read the AfD and the result was indeed to merge this article to the one that was inappropriately BLARed. So, yeah, that BLAR should be undone so that the merge can proceed. 1isall (talk | contribs) 13:58, 15 July 2026 (UTC)[reply]
I did a little digging on this through scholar, JSTOR, ngram search but did not find much. Based on those two sources, I'm inclined to think that Jog's night frog seems to be the most likely common name, narrowly based on the AMNH source using both names, and the "wrinkled" variety being sourced to a single citation vs the original description. WP:NCFAUNA states we should prefer the common name most used (orthography aside) by international zoological nomenclature authorities over regional ones, which in my head places IUCN above AMNH and its citation. That's all based on two sources, though. The scientific name might still be ideal. ASUKITE23:10, 14 July 2026 (UTC)[reply]
The "Jog" seems to be derived from a geographic feature, not some person's name, so I don't think the possessive form with the apostrophe+s makes so much sense. We wouldn't name a frog "Niagara's frog". — BarrelProof (talk) 00:54, 15 July 2026 (UTC)[reply]
@BarrelProof: Point taken re: grammatical norms -- though as @User:Asukite points out, Jog's night frog, with possessive, is the name given by the original describers (Biju et al. 2011). It may not seem super grammatically correct, but this practice is relatively common in the frogs for whatever reason.
Moreover, Amphibian Species of the World is the authority used for amphibian articles where taxonomy and nomenclature are concerned per WikiProject: Amphibians and Reptiles, and the non-possessive is not listed as a valid common name on ASW/AMNH or by the IUCN.
I put this below in another comment, but will say here as well: I don't have a super strong opinion where the article goes, be it Nyctibatrachus jog or one of the two common names. My preference is for scientific binomial when there are multiple valid common names in use, followed by chronologically first valid common name (Jog's night frog, with apostrophe, given by original describers in this case). DuckWrangler97 (talk) 20:06, 15 July 2026 (UTC)[reply]
@DuckWrangler97 Moved down here for now, I did not realize "Jog" was not a name, so perhaps lacking the possessive is okay, but now I'm uncertain (I don't have a strong opinion, in any case) ASUKITE14:08, 15 July 2026 (UTC)[reply]
Sounds good - to be clear, I don't have a super strong opinion where the article goes, be it Nyctibatrachus jog or one of the two common names. My preference is for scientific binomial when there are multiple common names in use, followed by chronologically first common name (Jog's Night Frog, with apostrophe, given by original describers in this case). DuckWrangler97 (talk) 19:53, 15 July 2026 (UTC)[reply]
I want to agree with the argument here, as it makes sense and would be consistent, but this was reverted recently as it has been moved several times in 2023 ASUKITE14:19, 15 July 2026 (UTC)[reply]
@162 etc. The article is barely edited. For instance, it had a total of four edits throughout 2024 and none in 2025. The only topic ever in the talk page is from a bot several years ago. With such minimal editor engagement, a full RM seems overly bureaucratic to me (How do we measure if an article's title has silent consensus behind it, if the article in question has barely been engaged with in a decade?) — EarthDude (Talk) 19:44, 14 July 2026 (UTC)[reply]
The discussion process is used for potentially controversial moves. A move is potentially controversial if either of the following applies:
there has been any past debate about the best title for the page;
someone could reasonably disagree with the move.
Use this process if there is any reason to believe a move would be contested. For technical move requests, such as to correct obvious typographical errors, see Requesting technical moves. The technical moves procedure can also be used for uncontroversial moves when the requested title is occupied by an existing article.
Do not create a new move request when one is already open on the same talk page. Instead, consider contributing to the open discussion if you would like to propose another alternative. Multiple closed move requests may be on the same page, but each should have a unique section heading.
Do not create a move request to rename one or more redirects. Redirects cannot be used as current titles in requested moves.
To request a single page move, click on the "Add topic" (or "New section") tab of the talk page of the article you want moved, without adding a new subject/header, inserting this code:
{{subst:requested move|New name|reason=Place here your rationale for the proposed page name change. You don't need to add your signature at the end, as this template will do so automatically.}}
Replace New name with the requested new name of the page (or with a simple question mark, if you want more than one possible new name to be considered). The template will automatically create the heading "Requested move 16 July 2026" and sign the post for you.
The reasons for the move can be summarized referring to applicable naming convention policies and guidelines, and providing evidence in support. If your reasoning includes search engine results, please prioritize searches limited to reliable sources (e.g. books, news, scholarly papers) over other web results.
There is no need to edit the article in question. Once the above code is added to the Talk page, a bot will automatically add the following notification at the top of the affected page:
A single template may be used to request multiple related moves. On one of the talk pages of the affected pages, create a request and format it as below. A sample request for three page moves is shown here (for two page moves, omit the lines for current3 and new3). For four page moves, add lines for current4 and new4, and so on. There is no technical limit on the number of multiple move requests, but before requesting very large multi-moves, consider whether a naming convention should be changed first. Discuss that change on the talk page for the naming convention, e.g., Wikipedia talk:Naming conventions (sportspeople).
To request a multiple page move, edit at the bottom of the talk page of the article you chose for your request, without adding a new header, inserting this code:
{{subst:requested move| current1 = Current title of page 1 (this parameter can be omitted for discussions hosted on a page that is proposed to be moved)
| new1 = New title for page 1 with the talk page hosting this discussion
| current2 = Current title of page 2
| new2 = New title for page 2
| current3 = Current title of page 3
| new3 = New title for page 3
| reason = Place here your rationale for the proposed page name change, referring to applicable naming convention policies and guidelines, and providing evidence in support. If your reasoning includes search engine results, please prioritize searches limited to reliable sources (e.g. books, news, scholarly papers) over other web results. You don't need to add your signature at the end, as this template will do so automatically.
}}
For example, to propose moving the articles Wikipedia and Wiki, put this template on Talk:Wikipedia with current1 set to Wikipedia and current2 set to Wiki. The discussion for all affected articles is held on the talk page of the article where the template is placed (Talk:Wikipedia). Do not sign the request with ~~~~, since the template does this automatically (so if you sign it yourself there will be two copies of your signature at the end of the request). Do not skip pairs of numbers.
RMCD bot automatically places a notice section on the talk page of all pages that are included in your request except the one hosting the discussion, to call attention to the move discussion that is in progress and to suggest that all discussion for all of the pages included in the request should take place at that one hosting location.
For multi-move discussions hosted on a page which is itself proposed to be moved, it is not necessary to include the |current1=Current title of page 1 for the page hosting the discussion, as its current title can be inferred automatically. Occasionally the discussions for significant multi-move requests may be hosted on WikiProject talk pages or other pages in Project namespace, in which case it is necessary to include |current1= to indicate the first article to be moved.
If you have to update a RM from a single move to multiple moves, you need to add the following parameters to the {{requested move/dated}} template call:
Please list every move that you wish to have made in your request. For example, if you wish to move Cricket (disambiguation) to Cricket because you do not believe the sport is the primary topic for the search term "Cricket", then you actually want to move two pages, both Cricket (disambiguation)andCricket. Thus you must list proposed titles for each page affected by your request. For example, you might propose:
If a new title is not proposed for the sport, it is more difficult to achieve consensus for a new title for that article. A move request that does not show what to do with the material at its proposed target, such as:
Use when the proposed new title is given. Do not sign this template—this tag is auto-signed when substituted. Be sure to use the subst:. This tag should be placed at the beginning of the section containing the relevant discussion.
Use when the proposed new title is not known. Do not sign this template—this tag is auto-signed when substituted. Be sure to use the subst:. This tag should be placed at the beginning of the section containing the relevant discussion.
This template adds subsections for survey and discussion. Do not sign this template—this tag is auto-signed when substituted. Be sure to use the subst: Click the "New Section" tab on the talk page and leave the Subject/headline blank, as the template by default automatically creates the heading.
Do not sign this template—this tag is auto-signed when substituted. Be sure to use the subst: and place this tag at the beginning of the section containing the relevant discussion. Add additional related move requests in pairs (|current3= and |new3=, |current4= and |new4=, etc.).
All editors are welcome to contribute to the discussion regarding a requested page move. There are a number of standards that Wikipedians should practice in such discussions:
When editors recommend a course of action, they write Support or Oppose in bold text, which is done by surrounding the word with three single quotes on each side, e.g. '''Support'''.
Comments or recommendations are added on a new bulleted line (that is, starting with *) and signed by adding ~~~~ to the end. Responses to another editor are threaded and indented using multiple bullets.
The article itself should be reviewed before any recommendation is made; do not base recommendations solely on the information supplied by other editors. It may also help to look at the article's edit history. However, please read the earlier comments and recommendations, as well as prior move requests. They may contain relevant arguments and useful information.
The debate is not a vote; please do not make recommendations that are not sustained by arguments.
Explain how the proposed article title meets or contravenes policy and guidelines rather than merely stating that it does so.
Nomination already implies that the nominator supports the name change, and nominators should refrain from repeating this recommendation on a separate bulleted line.[a]
Do not make conflicting recommendations. If you change your mind, use strike-through to retract your previous statement by enclosing it between <s> and </s> after the bullets, and de-bold the struck words, as in "• SupportOppose".
Please remember that reasonable editors will sometimes disagree, but that arguments based in policy, guidelines, and evidence have more weight than unsupported statements. When an editor offers an argument that does not explain how the move request is consistent with policies and guidelines, a reminder to engage in constructive, on-topic discussion may be useful. On the other hand, a pattern of responding to requests with groundless opinion, proof by assertion, and ignoring content guidelines may become disruptive. If a pattern of disruptive behavior persists after efforts are made to correct the situation through dialogue, please consider using a dispute resolution process.
Closing a requested move
Any uninvolved editor in good standing may close a move request. Please read the closing instructions for information on how to close a move request. The simple guide to closing RM discussions details how to actually close a requested move discussion. Most requested moves should be open for seven days (168 hours) but can be withdrawn under specific circumstances as per WP:RMEC.
Alternatively, the opener of a discussion can close it only if unanimous opposition is obvious, the requested move has not had any comments yet, or the request was initiated via block evasion. As per WP:WITHDRAW, an opener of a discussion should use strikethrough on the nomination statement when it is prematurely closed through withdrawal.
Relisting a discussion moves the request out of the backlog up to the current day in order to encourage further input. The decision to relist a discussion is best left to uninvolved experienced editors upon considering, but declining, to close the discussion. In general, discussions should not be relisted more than once before properly closing.[b] Users relisting a debate which has already been relisted, or relisting a debate with a substantial discussion, should write a short explanation on why they did not consider the debate sufficient to close. While there is no consensus forbidding participation in a requested move discussion after relisting it, many editors consider it an inadvisable form of supervote. If you want to relist a discussion and then participate in it, be prepared to explain why you think it was appropriate.
Relisting should be done using {{subst:RM relist}}, which automatically includes the relister's signature, and which must be placed at the very end of the initial request after the move requester's signature (and subsequent relisters' signatures).
When a relisted discussion reaches a resolution, it may be closed at any time according to the closing instructions; there is no required length of time to wait before closing a relisted discussion.
If discussion has become stale, or it seems that discussion would benefit from more input of editors versed in the subject area, consider more widely publicizing the discussion, such as by notifying WikiProjects of the discussion using the template {{RM notification}}. Banners placed at the top of the talk page hosting the move request can often be used to identify WikiProjects suitable for notification.
Notes
^A nominator making a procedural nomination with which they may not agree is free to add a bulleted line explaining their actual position. Additional detail, such as sources, may also be provided in an additional bullet point if its inclusion in the nomination statement would make the statement unwieldy. Please remember that the entire nomination statement appears on the list on this page.
^Despite this, discussions are occasionally relisted more than once.
(Discuss) – Septilici family → Șeptilici familyȘeptilici family – Author Revengetaker11 reverted [1] an undiscussed move to the proposed title I carried out two years ago [2] on the basis that the family's name was more commonly used in English without diacritics. Simply this family does not receive coverage in English-language sources [3][4]. Most of the coverage is, quite unsurprisingly, in Romanian. It is likely there is some in Russian and Serbian too. But this family had no links with English-speaking countries. Despite some titles having been translated, out of nine sources present in the article, only one is in English. Of course, the ones in Romanian use the diacritic, as it represents how the family's name is actually pronounced (ș=sh). The one in English does not [5], but then there's one Romanian-language source with an English summary which does use the diacritic [6]. The English source actually only makes one passing mention of a member of this family, it does not even discuss it (the Romanian-language one with an English summary does). I don't think this is proof of a deliberate choice to omit the diacritic in English but likely simply a detail that was forgotten on a 521-page book. I see no reason to exclude the diacritic. The vast coverage of this family seems to be in Romanian, with minimum English one. While the author's contributions are an obvious net positive, they've extended their practice to even more obscure (not meant as disparaging or insulting) figures such as Vasile Septilici, of whom I can find quite literally zero English-language coverage (5 out of 6 sources there are in Romanian, all use the diacritic). SuperΨDro01:51, 16 July 2026 (UTC)[reply]
(Discuss) – List of storms named Urmil → Cyclone UrmilCyclone Urmil – Sam Sailor reversed an admin move via their page mover rights as "undiscussed" and will obviously oppose this, so I'm bringing this RM up for you the community to decide. As stated in my request for the move, regardless of whatever and you can check both titles' page histories for that, is that speculation barely matters here on WP, because other than these notable cyclones, no other storm of this sort has ever been notable by this name enough to warrant an article, but will instead get redirected to the related parent broader storm season article. So as and when such at that arises, we can revisit this and deliberate the reverse/opposite, but for now, .... Intrisit (talk) 01:50, 16 July 2026 (UTC)[reply]
(Discuss) – Robinson list → Opt-out registry – The article should be moved from Robinson list to Opt-out registry. The current title appears to be region-specific and potentially unclear to readers who are not familiar with the term "Robinson list". The article itself defines the topic more generally as an opt-out list or register for people who do not wish to receive marketing communications by email, post, telephone, or fax. The examples in the article also show that many jurisdictions use other terms, such as "National Do Not Call List", "Do Not Call Register", "Do Not Call Registry", "Telephone Preference Service", and "Public Registry of Oppositions". Under WP:TITLE, article titles should generally be recognisable, natural, precise, concise, and consistent. I do not think "Robinson list" is the most recognisable or natural title for the broader international concept. It appears to be one regional or historical name for a wider class of opt-out registers. "Opt-out registry" would be a more descriptive and internationally understandable title. The proposed title may also better satisfy WP:PRECISE, because it describes the general subject of the article rather than one particular name used in some jurisdictions. It may also better reflect WP:COMMONNAME in a broad sense, as the article covers several national systems that are not commonly called Robinson lists. Even if individual schemes have specific names, the general concept is more clearly described as an opt-out registry. This move would also help with WP:CONSISTENT and WP:WORLDVIEW, because the article discusses systems in multiple countries. A title based on one regional term risks giving undue prominence to that terminology, whereas "Opt-out registry" is more neutral and descriptive across jurisdictions. This request is also relevant to the AfD discussion at Wikipedia:Articles for deletion/Do not call list, where editors are considering the relationship between Do not call list and Robinson list. If overlapping content is merged, the target article should ideally have a title that is clear, internationally understandable, and broad enough to cover telephone, postal, email, and fax marketing opt-out systems. For these reasons, I think Opt-out registry would be a better title than Robinson list. Kirbylegal (talk) 14:14, 29 June 2026 (UTC) — Relisting.Jeffrey34555 (talk) 05:57, 6 July 2026 (UTC) — Relisting.Squawk7700 (talk) 00:09, 16 July 2026 (UTC)[reply]
July 15, 2026
(Discuss) – Pratt's roundleaf bat → Swinhoe's roundleaf bat – While it is not always necessary to align common names with scientific names, the situation differs when a common name clearly corresponds to an obsolete scientific name. I believe that the current common name derived from Hipposideros pratti—a scientific name that should no longer be used—ought to be replaced by "Swinhoe's roundleaf bat," which is derived from the valid scientific name Hipposideros swinhoii (which holds priority). コロネン (talk) 22:21, 8 July 2026 (UTC) — Relisting.1isall (talk | contribs) 23:57, 15 July 2026 (UTC)[reply]
(Discuss) – She Chinese → Shanke dialectShanke dialect – Noting that many people may not be familiar with this language. I think it is necessary to explain the reason for the move. The study to the Hakka or Hakka-like variant spoken by the She (Shanke) people is the niche study of niche studies among existing studies to the Chinese language using English language as a medium. The study to this dialect in English is very uncommon, so it is very hard to have a uniform commonly known name in English. Different scholars used different names to call this dialect. Not to mention in English, the National Ethnic Affairs Commission AND other branches of the Chinese government has not even confirmed an official name for this dialect in Chinese. In another word, it doesn't even have an official standardised Chinese name. The language only has a widely acknowledged native endonym called "山客话 (shānkè huà)". According to the interlanguage links to this concept, there are three Wikipedia articles to this concept in three different languages, which are Chinese, Indonesian, and English. Both articles in Chinese and Indonesian Wikipedia use this language's native endonym by its native users, which is "山客 (Shanke / Shanha)" as the name for this concept. In Chinese Wikipedia, it is called "zh:山客话 (shānkè huà)". In Indonesian Wikipedia, it is called "id:Bahasa Shanha". In either way, they are based on this language's native endonym "山客话 (Shanke dialect)" called by its native speakers. Now, let me explain why it is appropriate to change the name of this article from "She Chinese" to "Shanke dialect" in English.1: The term "She Chinese" is never found in English to refer to this language. No matter whether you search "She Chinese" in Google Scholar or in other English databases, you will never find this two words "She Chinese" to be used to refer to this language. In some occasions, "She Chinese" may be used to refer to the She people, but "She Chinese" is never used to refer to this language in English. At the same time, you can find "Mandarin Chinese", "Xiang Chinese", "Yue Chinese", "Gan Chinese" everywhere in their studies. 2: "———— Chinese" is the fashion to name primary branches of the Chinese language, not varieties under primary branches. To be named "———— Chinese", the branch needs to be either large enough or distinct enough (if not large enough). "She Chinese" is neither large enough like "Mandarin Chinese" and other nine primary branches of Chinese, nor distinct enough like "Waxiang Chinese" as an ancient although tiny Chinese branch. This is quite important. For example, Huizhou dialect and Huizhou Chinese are entirely different Chinese varieties. Huizhou Chinese implies that this is a primary Chinese branch, but Huizhou dialect should be under a primary branch (although Huizhou dialect is still disputed regarding whether it should be under Hakka Chinese or Yue Chinese). "She Chinese" is apparently not large enough, and at the same time, it is not as distinct as Waxiang Chinese, because the mainstream linguists classify it as a dialect under Hakka Chinese. 3: "Shanke" as the English name for this language is not a new invention in English. It has already been used in academic journals for long to differentiate itself from other languages used by the She people, such as Dongjia language and Huonie language, and from the exonyms to this language. In 2021, in publication "Insights From Y-STRs: Forensic Characteristics, Genetic Affinities, and Linguistic Classifications of Guangdong Hakka and She Groups" on PubMed Central and PubMed, it says "She people speak the She language with different dialects such as Shanke, Dongjia, and Huonie. She language is a branch of Sino-Tibetan language families and is the primary language for the She group." In 2009, in publication "Languages of the She Minority: A Review of the Literature" on the UC Berkley's journal Journal of Chinese Linguistics collected in JSTOR, it says "The Han people call the language spoken by the She Shekehua 畲客话 or Sheminhua 畲民话 ('speech of the She guests' or 'speech of the She people'), but the She people call their own language Shankehua 山客话, or Shanhahua 山哈话 'speech of the mountain guests'." The name "Shanke" as the dialect's English name in its English spelling has been used and collected by academic authorities for a long time already. 4: According to the WP:COMMONNAME, it says "When there is no single, obvious name that is demonstrably the most frequently used for the topic by these sources, editors should reach a consensus as to which title is best by considering these criteria directly". All of the four names I have seen in English publications, which are the two native endonyms "Shanke dialect (山客话)" and "Shanha dialect (山哈话)", and two externally defined exonyms "She dialect (畲话)" and "She language (畲语)" referring to this same language, are uncommon, because the study to this language itself is uncommon. Scholars improvised different translations to the name of this language each time when they need to mention this language in English. There is no standardised name or widely known name. You can't even find an entry for this language in a Chinese dictionary, English dictionary, Chinese-English dictionary, or English-Chinese dictionary. There are in fact many Chinese topics that are rarely discussed or not at all discussed in English. For example, Younian dialect of Chinese spoken by ethnic Yao people is almost never discussed or mentioned in any English source (Google Scholar search result), but it still has an English Wikipedia article. Therefore without a common name (or without a pre-existing name at all) in English is never a real issue. As long as a good translation is created or selected. There is a policy in Chinese Wikipedia called zh:WP:名从主人 meaning the name needs to follow what is defined by its owner (主人). That is why "山客话 (Shanke dialect)" is used as the name in Chinese Wikipedia. When the Chinese government does not confirm a standardised name for this language, the native users of this Chinese dialect should be ranked the second to define how this language should be called. There are similar proposals in English Wikipedia in Wikipedia_talk:Article_titles/COMMONNAME sandbox, but not in official policies. Therefore I request to move the article from "She Chinese" to "Shanke dialect", following how this language is called in Chinese Wikipedia as "山客话 (Shanke dialect)" and in Indonesian Wikipedia as "Bahasa Shanha". "Shanke" should be preferred, because "Shanha (山哈)" represents the phonetic loan Chinese character for "Shanke (山客)". "Shanke" is like the true spelling of an English word. "Shanha" is like a common misspelling of an English word. We use the true spelling, not the misspelling. Sinowriter (talk) 21:30, 8 July 2026 (UTC) — Relisting.1isall (talk | contribs) 21:54, 15 July 2026 (UTC)[reply]
(Discuss) – Owings Mills Mall → Mill StationMill Station – There is a strong consensus that articles on redeveloped malls go by the current name if something still operates at the site. See Shingle Creek Crossing, not Brookdale Center; Wonderland Village, not Wonderland Mall; Maple Hill Pavilion, not Maple Hill Mall; The Loop (shopping center), not Methuen Mall; Silver Lake Village, not Apache Plaza; NetPark Tampa Bay, not East Lake Square Mall; etc. This allows the article to be more inclusive of both the former and current incarnations, even in cases like Wonderland Village where nothing remains of the original property. I think the mall, in both past and present forms, is more notable than an obscure transit station in Ontario (which IMO shouldn't even have an article) and the capital S enough per WP:SMALLDETAILS for "Mill Station" to unambiguously refer to the mall. Extensive searching shows no other content on Wikipedia called "Mill Station" with which this might be confused. Ten Pound Hammer (they/them) • (What did I screw up now?)16:21, 15 July 2026 (UTC)[reply]
Template names should be made of one or more words, and describe the template clearly, as in {{Math topics sidebar}}. Template names are easiest to remember if they follow standard English spelling, spacing, and capitalization. Avoid having templates whose names differ only in case, spacing, or punctuation.
Of course, the old title will still remain a redirect so people can keep using it as a shortcut. FaviFake (talk) 18:28, 21 June 2026 (UTC) — Relisting.1isall (talk | contribs) 18:48, 28 June 2026 (UTC) — Relisting.Squawk7700 (talk) 15:34, 15 July 2026 (UTC)[reply]
(Discuss) – Pine View School for the Gifted → Pine View School (Florida) – Pine View School is a disambiguation page. Reviewing WP:NCDAB, I see the use of option 1 for a more complete name, but for the Gifted does not remove ambiguity when multiple schools have similar names. The school does not use for the Gifted as its identification on social media, entrance signs, or school seal. I sometimes see the full name referenced in press releases. My request is based on option 3, using a parenthetical disambiguation. It seems most logical when reviewing articles with Pine View in their name [9], and the school is for grade 2 to 12 students. – The Grid (talk) 14:25, 15 July 2026 (UTC)[reply]
(Discuss) – Lutra → Lutra (Lutra) – Under the classification currently adopted by Wikipedia, Aonyx is a paraphyletic group that includes Lutrogale. Ferran et al. (2022) supports the inclusion of the subgenera Lutra, Aonyx, Amblonyx, and Lutrogale within an expanded Lutra. Mammal Diversity Database adopts this classification. I plan to convert the three existing articles into articles on subgenera, while repurposing the Lutra entry into an article covering the expanded genus. As this change in classification has previously been mentioned on the article's talk page and could be controversial, I am submitting this "Requested Move" proposal. コロネン (talk) 03:42, 1 July 2026 (UTC) — Relisting.1isall (talk | contribs) 04:52, 8 July 2026 (UTC) — Relisting. –Maltazarianᚾparleyinvestigateᛅ05:21, 15 July 2026 (UTC)[reply]
(Discuss) – Adelaide Eagles → Adelaide University Eagles American Football Club – The club is no longer affiliated with the former University of South Australia. Following the merger of the University of South Australia and the University of Adelaide, the club is now affiliated with Adelaide University and competes as the Adelaide University Eagles American Football Club. The current title does not reflect the club's present identity or official name. A move to "Adelaide University Eagles American Football Club" would better reflect the club's current status and distinguish it from the former UniSA Eagles and Adelaide Eagles identities. Rfwikip (talk) 04:35, 15 July 2026 (UTC)[reply]
(Discuss) – Francisco Cavalcanti Pontes de Miranda → Pontes de MirandaPontes de Miranda – WP:CONCISION/WP:RECOGNIZABILITY/WP:NATURALNESS: Pontes de Miranda is the widely used name form in both academic and general sources, as well as the form he used to sign and publish his works.[1][2][3] This is how his name appears in both English and Portuguese-language scholarship,[4][5][6][7][8] judicial decisions,[9] and legal treatises/textbooks/encyclopedias (e.g: NADER, Paulo. Introdução ao Estudo do Direito, 47. ed. Rio de Janeiro: Forense, 2025. p. XXI / Enciclopédia Jurídica da PUCSP: Tomo 10 - Direito Civil, Representação).[10] The title of the Portuguese-language entry is Pontes de Miranda, and he is frequently referred to by both students and professors as simply Pontes. Laptss (talk) 01:11, 15 July 2026 (UTC)Laptss Laptss (talk) 01:11, 15 July 2026 (UTC)[reply]
As you can see from the navbox above, most of this template family already lives at spelled-out names (Space+double, Double+space, Space+single, Space+parenthesis, Single+double+single, etc.) with the bare symbols kept only as shortcuts. However, {{'s}} and {{`s}} are the odd ones out, sitting at symbol-only names that do not describe what they do, which runs against WP:TPN: (emphasis supplied)
Template names should be made of one or more words, and describe the template clearly [...]. Avoid having templates whose names differ only in case, spacing, or punctuation.
The only other rule-breaker is {{'}}'s target, {{Apostrophe}}, which is actually the version with a small leading space for use right after italic markup, while the plain, unspaced version for use after bold markup is at {{`}} and has never had a spelled-out name. Going by how every other spacing template here is named, in theory the spaced {{Apostrophe}} apostrophe should be "Space+apostrophe" and {{`}} should be Apostrophe, but that would be too complicated. So, the simplest solution is to move {{`}} to {{Unspaced apostrophe}} to keep the names distinct but still intelligible per the policy. Of course none of this touches existing transclusions, since old names remain as working redirects like all the other {{Quotation mark templates}}FaviFake (talk) 17:58, 14 July 2026 (UTC)[reply]
(Discuss) – Teimuraz II of Kakheti → Teimuraz II – WP:PRIMARYTOPIC. Teimuraz II ruled both Kakheti and Kartli. He ruled Kartli until his death after Kakheti was given to his son, Heraclius. Unlike his reign in Kakheti, Teimuraz ruled Kartli independently from Persia. Teimuraz was also born in Tbilisi, Kingdom of Kartli, during the reign of his father in Kartli. Gergos10 (talk) 17:40, 14 July 2026 (UTC)[reply]
(Discuss) – Microsoft Gaming → Xbox (division)Xbox (division) – This is after the previous move yo this name was undone. "Xbox" is the new name of this division, no questions.l, and all sources since call this division as Xbox and not Microsoft Gaming. The claim that WP:NATURAL applies is misplaced because of this change (this is not like the X/Twitter situation) Masem (t) 14:46, 14 July 2026 (UTC)[reply]
(Discuss) – 2026 Golders Green attack → 2026 Golders Green stabbings – Per WP:PRECISE, the current title is inadequate because it does not unambiguously define the topical scope of the article. As it stands, readers might mistake this article title as referring to the 2026 Hatzola arson attack, which also took place in Golders Green and was widely referred to at the time as "the Golders Green attack" before this second incident occurred. A proposal of this type was previously made in May but was closed due to being active at the same time as another move proposal. TRCRF22 (talk) 11:51, 14 July 2026 (UTC)[reply]
(Discuss) – Licence to kill (concept) → Licence to killLicence to kill – I don't see why a James Bond movie should be considered the "default" licence to kill article and the article on actual licences to kill should have (concept) appended at the end. Similar proposals were attempted in the late 2000s, but they didn't get anywhere (see Talk:Licence to kill (concept)). Edit (July 14th): Multiple people have opposed this RM on account of the argument that licences to kill do not actually exist, or that the Licence to kill (concept) article fails to meet Wikipedia's content policies in some way. I would like to remind these people that RMs are requested moves, not AfD discussions. If you oppose the existence of the Licence to kill (concept) article altogether, please file an AfD instead of posting here. GrinningIodize (talk) 21:06, 6 July 2026 (UTC) — Relisting.Frost10:31, 14 July 2026 (UTC)[reply]
(Discuss) – Weather news → Weather channelWeather channel – When I created this disambiguation a few years ago, I sought to disambiguate different local, national, and international weather channels; but looking back the title I created might not have been the obvious term for this topic, and this topic is likely notable given the existence of many channels with weather-oriented programming so the next logical step would be to convert the disambiguation into a standalone article. Aasim (話す) 03:56, 7 July 2026 (UTC) — Relisting.Jeffrey34555 (talk) 03:00, 14 July 2026 (UTC)[reply]
(Discuss) – Riigikogu → Parliament of EstoniaParliament of Estonia – Hey editors. As of now it is is community consensus per WP:NCGAL that; "When writing articles on government bodies or offices with native titles not in English, an English translation should be favored, except when reliable sources in the English language commonly use the native title. For example, National Assembly of Bulgaria (not Narodno sabranie) but 2003 loya jirga (not 2003 Grand Assembly) and Bundestag (not Parliament of Germany)." I do not think this article is in line with that and should therefore be moved to Parliament of Estonia. On a quick search it is not easy to find news covering the parliament with "Riigikogu". When you do use "Parliament of Estonia news" you will find that reputable source Euronews uses "Riigikogu" but reputable sources BBC, AP news and PBS news do not. Further sourcing is scarce at best because of how rarely the body comes up. That is further reason to think that "Riikigoku" is not the common name used for this body in English. Finfixer (talk) 19:37, 13 July 2026 (UTC)[reply]
(Discuss) – Soldier Boy → Soldier Boy (The Boys) – Per WP:RECENTISM, I do not think Soldier Boy from The Boys should be WP:PRIMARY as the idea of a "Soldier Boy" dates back long before The Boys was ever created, and is probably how the character got his name in the first place. Soldier Boy from The Boys might currently be what most people think of when they hear "Soldier Boy", but this may not be the case in the future (again going back to how "Soldier Boy" is a historical term/phrase/idea/something). ThePoggingEditor (talk) 17:00, 24 June 2026 (UTC) — Relisting.Destinyokhiria(talk / cont) 17:51, 1 July 2026 (UTC) — Relisting.Squawk7700 (talk) 18:06, 13 July 2026 (UTC)[reply]
Out of those seven articles, there are only two Wikipedia articles where the main topic is "Dress to Impress"; "Dress to Impress" for Moving Moving On, Perfect Score, and Roseanne are all redirects to the season where the episode lands.
(Discuss) – Pira-tapuya → Waʼikhana – per WP:AUTONYM, The names an ethnic group or Indigenous government self-identifies should be considered. If their autonym is commonly used in English, it would be the best article title. Any terms regarded as derogatory by members of the ethnic group in question should be avoided. The Piratapuyo call themselves Waʼikhana and have expressed preference for others to use their self-designation (Stenzel 2013). 🪐Kepler-1229b | talk | contribs🪐00:53, 13 July 2026 (UTC)[reply]
(Discuss) – Two-Way Stretch → Two Way Stretch (1960 film) – There are currently three pages with almost no difference in title, and without a disambiguation page to distinguish them: * Two-way stretch, a redirect to Stretch fabric. * Two-Way Stretch, this 1960 film. * Two way stretch, a redirect to the film page. For the film, I think the title which should be used in WP should be Two Way Stretch, without the hyphen. WP:COMMONNAME says that articles should be titled with "the name that is most commonly used (as determined by its prevalence in a significant majority of independent, reliable, English-language sources)". Here are some sources for the two alternatives: Two Way Stretch (my preferred spelling): * BFI record * BBFC certification record * Film's on-screen opening credits * Leslie Halliwell Halliwell's Film GuideTwo-Way Stretch (the current title): * The original poster, shown in the infobox. However, this also uses all lower case, and film advertising posters are often unreliable records of titles * EIDR content record * Kine Weekly p. 9 in-article reference * Ephraim Katz The Film Encyclopedia A Google Books search here shows a roughly even split. I think the clinchers here should be the BFI and BBFC records, supported by the film's own credits. So, I suggest moving the current page to be titled Two Way Stretch (1960 film), and deleting the Two way Stretch redirect to it. Masato.harada (talk) 16:01, 5 July 2026 (UTC) — Relisting.1isall (talk | contribs) 21:35, 12 July 2026 (UTC)[reply]
(Discuss) – Northern League (British neo-Nazi organisation) → Northern League (neo-Nazi organisation) – The problem with the current title is that they were not even mostly British and functioned as a global network. It was technically founded in India and was simultaneously active in Europe and with multiple chapters in the USA. To quote Dreamer of the Day, pp. 469–470: Carto's connections in the segregationist right led him to join a mysterious organization called the Northern League for Pan-Nordic Friendship. [...] [William] Stephenson let the southern-U.S. branch of the Northern League operate out of The Virginian's office [...] the NL also published The Northlander out of its Scotland headquarters. After Carto joined, the League's West Coast headquarters became Right. [...] A Scotsman named Alastair Harper ran its European wing from League headquarters in Dunfermline, Scotland.22 The League's founder and Central Organizer was Roger Pearson, an Englishman who at the time of the League's creation was living in Calcutta, India.23 [...] The NL quickly established branches throughout the United States and Europe, including a cell for the western part of the United States created in 1958 through Right." PARAKANYAA (talk) 20:16, 5 July 2026 (UTC) — Relisting.Jeffrey34555 (talk) 20:09, 12 July 2026 (UTC)[reply]
(Discuss) – John Saul (prostitute) → John Saul (sex worker) – I don't have a strong opinion one way or another on this, but (per recent edits to the page) the term "sex worker" is preferred nowadays; however, I understand as this is discussing an historical figure, this may not be appropriate. Not sure if we need to mention in the disambiguation that he was a male sex worker who had sex with other men, as this is relevant to his historical significance. (Also, he seems to be more commonly known as "Jack" in the sources) – GnocchiFan (talk) 12:43, 12 July 2026 (UTC)[reply]
(Discuss) – 2000 England v Germany football match → October 2000 England v Germany football match – Ambiguous title. There were two football matches between England and Germany during 2000; one that took place in June 2000 as part of Euro 2000, and the one being described in this article. Both attracted significant media attention for different reasons (the June match was England's first win over Germany since the 1966 World Cup final, and a major upset which eliminated the tournament holders; the October match was the last match at the original Wembley Stadium and directly led to Kevin Keegan resigning as team manager), so with its current title someone could quite easily link to the page thinking it was referring to the June match. DaveJB (talk) 11:02, 12 July 2026 (UTC)[reply]
(Discuss) – January 2019 Louisiana shootings → 2019 Ascension–Livingston shootings – Alts: 2019 Louisiana shootings; Ernest–Theriot family murders (latter could imply hyphenated name, but I want to hear thoughts about it). A lack of other notable spree shootings across the parishes of Ascension and Livingston does not imply that a year is not necessary, factors such as how identifiable the incident does, and this incident does not appear to reach that level of notoriety. Please note that WP:NCWWW states that most events titles should say when, where, and what happened. Years are not WP:OVERPRECISION (please note that exceptions to the precision criterion are a result of the application of other naming criterion) or only usable for disambiguation (if this were the case, then part of NCWWW would be basically irrelevant, and guidelines and policies should work in harmony, not in opposition to one another). Readers should not be confused if there have been other notable spree shootings across Ascension and Livingston because if there had been, it should be mentioned and linked to in the article, like with the distinguish template. Please also note that for WP:NOYEAR to apply, you must establish that the event is as remotely as easily recognizable as the examples of no year events. Additionally, the sentence "The date is not needed when the article pertains to events that are unlikely to recur" refers to events involving individual people or persons. This is a situation where there is no clear and obvious WP:COMMONNAME, but having "January" in the title is unnecessary disambiguation as there was no other notable shooting in Louisiana in 2019 (and no, the year is not disambiguation). Because of this, I've suggested two other alternatives, and I encourage participants to try to think of other potential alternatives as well. The current title does not follow naming guidelines for events, and needs to change one way or another. Raskuly🐰07:18, 12 July 2026 (UTC)[reply]
(Discuss) – 1925 Tri-State tornado outbreak → Tornado outbreak of March 17–18, 1925Tornado outbreak of March 17–18, 1925 – While the Tri-State tornado was by far the most infamous tornado of the outbreak. The current name is not in-line with standards, an entire outbreak should not be named after a single tornado, even if one is the most notable by the long shot. This outbreak was significantly more than JUST the Tri-State tornado. You had violent and deadly tornadoes in Tennessee and Kentucky, as well as tornadoes in Kansas and Alabama. I saw a move to this name was attempted prior, but apparently it is considered controversial enough to warrant a revert. Quincy Gordon (talk) 20:42, 11 July 2026 (UTC)[reply]
(Discuss) – Voskopoja → VoskopojëVoskopojë – Of the 1022 articles of settlements in Albania, 1020 use the indefinite form in their article titles. The only 2 exceptions are Voskopoja and Tirana (I will open an RM for it as well). As such, for consistency, I think that this article should be moved to the indefinite form of the name, Voskopojë. Ktrimi991 (talk) 20:18, 11 July 2026 (UTC)[reply]
(Discuss) – Foreign relations of California → Intergovernmental relations of California – This page covers (1) Relations between California and tribal governments (2) Relations between California and other states and (3) Relations between California and foreign states (or their subdivisions). The current title only encompasses the third category. I use "intergovernmental" instead of "external" as many tribal nations are within California's borders and therefore not "external". CC: @RayneVanDunem:Benboy250 (talk) 19:40, 11 July 2026 (UTC)[reply]
(Discuss) – AOC (disambiguation) → AOCAOC – The use of AOC without a disambiguator to redirect to Alexandria Ocasio-Cortez is awfully America-centric, AOC has dozens of other meanings apart from this person's initials and is not used to refer to this person outside of the United States. In the previous RM discussion it was noted that approximately 90% of clickthroughs are to Cortez's page, however this is irrelevant purely because of the ridiculously large number of other uses of "AOC". Electricmemory (talk) In solidarity18:19, 11 July 2026 (UTC)[reply]
(Discuss) – Wikipedia:Deletion process → Wikipedia:Deletion processesWikipedia:Deletion processes – The title "Deletion process" implies there is a single unified process for deletion, while we actually have several distinct processes that operate independently of one another. Most obviously, CSD, PROP, and XfDs are three entirely separate mechanisms with different criteria, timescales, participants or lack thereof, and outcomes. A page that qualifies for speedy deletion bypasses discussion entirely; a PROD resolves in seven days without discussion; an XfD runs a 7-day discussion and requires a closure to close. Within XfDs alone, there are six separate venues, each with their own scope and instructions. These obviously aren't stages of one process, they're alternatives. The singular "process" might make sense if this page were just a step-by-step walkthrough of one procedure, or if the procedures were remotely similar. The plural reflects that in a clearer way. FaviFake (talk) 14:17, 21 June 2026 (UTC) — Relisting.Squawk7700 (talk) 15:16, 28 June 2026 (UTC) — Relisting.TarnishedPathtalk12:00, 11 July 2026 (UTC)[reply]
(Discuss) – Sam Phillips → Sam Phillips (record producer) – I somewhat recently closed the RM at Talk:Sam Phillips (musician, born 1962) § Requested move 28 June 2026 in which it was suggested that Sam Phillips might not be the primary topic based on the page view statistics. For simplicity's sake and in order to avoid a possible WP:TRAINWRECK with the many disambiguators I decided to close that RM and encourage the opening of a new one here. However since that has not happened I feel like it would be unjust to the editors who !voted to demote Sam Phillips from ptopic, so I am opening this RM so that it can be discussed nevertheless. I just started with record producer as disambiguator, but that is not set in stone, so feel free to propose a different one. I am quite indifferent to the result. Best, Squawk7700 (talk) 11:59, 11 July 2026 (UTC)[reply]
(Discuss) – 2025 Sumy offensive → Sumy offensive (2025–present) – Russian invaders are still in the oblast, so the offensive is still ongoing. Per the RM started here [39] and the title at Northeast Donetsk Oblast campaign, I also invite users to discuss including "Oblast" into the title ("Sumy Oblast offensive (2025–present)", as the offensive hasn't taken place in the city of Sumy nor has it had the aim to capture it) and the use of "campaign" over "offensive". I'd personally favor including "Oblast" while I have no opinion on the second issue (I honestly kind of don't know when should each word be used). Regards, SuperΨDro 00:45, 18 June 2026 (UTC) — Relisting.1isall (talk | contribs) 00:56, 25 June 2026 (UTC) — Relisting. –Maltazarianᚾparleyinvestigateᛅ 14:32, 3 July 2026 (UTC) — Relisting.TarnishedPathtalk11:54, 11 July 2026 (UTC)[reply]
(Discuss) – Donkey Kong (1981 video game) → Donkey Kong (video game)Donkey Kong (video game) – This article should be a shoe-in for WP:PARTIALDAB. The only other video game titled just Donkey Kong is Donkey Kong (1994 video game). One is a later Game Boy release that according to its article "was overshadowed by Donkey Kong Country, released later in 1994." The other is one of the most important video games of all time. Arguably the foundation for the entire platformer genre, the reason Mario exists, the foundation of Nintendo's transformation into a globally recognized brand, and one of the highest grossing arcade games of all time. This article typically gets about 5-6 times the daily page views of the Donkey Kong (1994) and not infrequently that jumps to 10-20 times. Donkey Kong (1981) is pretty clearly the primary topic here, and so should be partially disambiguated as such. It's not lost on me that this would revert the title back to what it was three years ago. In that discussion, the point was raised that there are lots of Donkey Kong games, so calling this "Donkey Kong (video game)" would be ambiguous. But this is quite frankly not how our disambiguation works, we don't title Final Fantasy (video game) as Final Fantasy (1987 video game) because someone might believe the article is actually about Final Fantasy VII or Final Fantasy XII. Other Donkey Kong games have well known, commonly used taglines and subtitles that readers can be expected to understand. On the other hand, readers may not be expected to have the release date of a 45-year-old video game memorized. Donkey Kong (video game) is the disambiguation that is most consistent with WP:NCVGDAB and WP:PDAB, which provides consistency for both readers and editors and makes it way easier to figure out which arbitrary parenthetical phrase gets you to the article you actually want. Whipmywillows (talk) 09:30, 4 July 2026 (UTC) — Relisting.TarnishedPathtalk11:50, 11 July 2026 (UTC)[reply]
(Discuss) – Unguja → Zanzibar IslandZanzibar Island – We have got these three articles: * Zanzibar, which is about the Zanzibar Archipelago, which by which it describes as consisting of two main islands: Zanzibar island (Unguja), Pemba island (but not Mafia island). * Zanzibar Archipelago, which is also about the Zanzibar Archipelago, which it describes as consisting of three main islands: Zanzibar island (Unguja), Pemba island, and Mafia island. * Unguja (this article) which refers to (what is basically always called) Zanzibar, the island. Unguja is by a very large margin called Zanzibar by native English speakers. Here is some evidence: * This google Ngram flat out proves it. There's not even the tiniest argument in the face of that. * This google Trends chart, same deal. Overwhelming. That's worldwide, but even in Tanzania it's the same deal. * And I mean, come on. Have you even heard the term "Unguja"? The title of John Brunner's Stand on Zanzibar, for instance, specifically references the island only. Because of course; he needed to use a term for the island that people understand. And so forth. I get that we would like to use endonyms instead of exonyms (Zanzibar is from Persian). It is polite and we do that often. But only if it's supported by a good percentage of English speakers worldwide, which Unguja isn't. We need to rename this article to "Zanzibar Island". The current article Zanzibar Archipelago should stay, but the article currently named "Zanzibar" needs to be folded into Zanzibar Archipelago (altho that article is much smaller... possibly fold the smaller article into the larger, delete Zanzibar Archipelago and rename Zanzibar to Zanzibar Archipelago, and make "Zanzibar" a redirect to this article. It'd take an admin to do all that. Herostratus (talk) 05:21, 11 July 2026 (UTC)[reply]
(Discuss) – 2026 California billionaire tax initiative → 2026 California Proposition 402026 California Proposition 40 – We usually name ballot measures with their official name, and there's no good reason to make an exception here. This was referred to as the "billionaire tax" in reliable sourcing mainly as a descriptive title, not as a proper name (and obviously they couldn't call it Proposition 40 before it was numbered as such). Now that it's been numbered, it's primarily being referred to as Proposition 40 (and while it's being called a "billionaire tax" to describe it, that isn't being used as its title, so WP:COMMONNAME does not apply; this is similar to how how Proposition 8 was described as a "gay marriage ban"--but that clearly shouldn't be that article's title either). Sources published after the measure's numbering confirm that Proposition 40 is the proper way to title this. For example, LA Times: Championed by California’s largest health workers union, Proposition 40 would levy a one-time, 5% tax on California’s roughly 200 billionaires.Elli (talk | contribs) 02:14, 11 July 2026 (UTC)[reply]
(Discuss) – History of Poonch district → Poonch JagirPoonch Jagir – The page is structured around and primarily focussed on the Jagir of Poonch, a semi-indepedent territory with hereditary rulers, that existed until the late 1940s. District is a modern administrative term, when the territory started being governed by elected representatives post the independence of India and Pakistan. Smart Sherlock (talk) 07:53, 4 July 2026 (UTC) — Relisting.Jeffrey34555 (talk) 01:35, 11 July 2026 (UTC)[reply]
(Discuss) – Topman → ? – As per my previous discussion above, the current title is a neologism and does not reflect the historical term of topman which has been reported in every Dictionary and Encyclopedia since the Age of Sail. Nicola Romani (talk) 04:23, 23 June 2026 (UTC) — Relisting.1isall (talk | contribs) 15:55, 30 June 2026 (UTC) — Relisting. –Maltazarianᚾparleyinvestigateᛅ01:32, 11 July 2026 (UTC)[reply]
(Discuss) – Steam Controller (1st generation) → Steam Controller (2015)Steam Controller (2015) – The articles fall under Wikipedia:WikiProject Video games. The convention is to use disambiguator in form of "category", e.g. (video game), (console); "year", e.g. (2000); or combination, e.g. (2012 video game). There are no results for articles featuring ordinal followed by the specifier "generation". Using combination/category may be too verbose, as the device already includes the word "controller" in its name. No WP:NC covers the subject. I propose to rename this article to use distinctor of the device used by the manufacturer, developers, and media.
(Discuss) – The Innocent (2001 miniseries) → The Innocent (serial) – WP:NCTV allows for (serial) to be used for British series/serials in line with British nomenclature. (TV serial) was the stable version for years, in line with the convention I would like to move The Innocent to a more appropriate title, as "common usage in reliable sources" for British programmes, as I have demonstrated here (2026) and here. Halbared (talk) 08:29, 1 July 2026 (UTC) — Relisting. –Maltazarianᚾparleyinvestigateᛅ01:21, 11 July 2026 (UTC)[reply]
(Discuss) – Vallow–Daybell doomsday murders → Vallow–Daybell murder caseVallow–Daybell murder case – Per the proposal made above, I suggest we give the article a less sensationalist title. While the "doomsday cult" aspect, the "doomsday mom" nickname, and the murderers' unusual religious beliefs attracted attention, it was never exactly clarified if their main motive was religious, financial, or romantic/sexual (one may speculate that it was all three). Anyway I have never seen the phrase "Vallow–Daybell doomsday murders" used elsewhere, so it might be a bit awkward to use a title that originated strictly on Wikipedia. Psychloppos (talk) 13:40, 3 July 2026 (UTC) — Relisting. –Maltazarianᚾparleyinvestigateᛅ23:58, 10 July 2026 (UTC)[reply]
(Discuss) – Meta Qureshi → Matwa Qureshi – The current title, "Meta Qureshi", appears inaccurate and inconsistent with the subject of the article. The article's lead identifies the community as "Matva Qureshi", also known as "Matwa Kureshi". Official Government of India and Government of Gujarat records list "Matwa or Matwa-Kureshi (Muslim)" separately from "Me or Meta". This indicates that "Meta" is a separate listed name and should not be used as the title of this community's article. The proposed title "Matwa Qureshi" is more precise and consistent with the available reliable sources under WP:TITLE and WP:PRECISION. Alternative spellings, including "Matva Qureshi", "Matwa Kureshi", and "Matva Kureshi", may be retained as redirects. I am a member of this community and disclose my personal connection to the subject. Sources: Government of India, Press Information Bureau and Government of Gujarat SEBC list. MDKURESHI (talk) 22:49, 10 July 2026 (UTC)[reply]
(Discuss) – 2011 St. Louis tornado → 2011 Good Friday tornado – This page was once named as such back then (specifically 2011 Good Friday Tornado), due to the event occurring on Good Friday, April 22, 2011. It was then moved on April 24, 2011 by @Cyclonebiskit to 2011 St. Louis tornado, because it was "less ambiguous" to name it for a single tornado event and that it immediately reflects the affected area (that being directly St. Louis, Missouri), and that naming it as such could refer to other tornadoes that have occurred that same day. Per WP:COMMONNAME, the local NWS office, but especially many press sources have referred this specific EF4 tornado as the Good Friday tornado in the wake of the event, and even as far as a decade or more after it happened. I personally do not find both names bad, but I am leaning more on the WP:COMMONNAME policy on renaming this article back to what it originally was named as by the creator, @Strikerforce. And despite literally being named by the media industry from in and around the St. Louis, Missouri metro as just the Good Friday tornado, it definitely would need the 2011 parenthesis to not conflict with another violent EF4 tornado (has a draft by @Lightbulb Noob) and outbreak that also occurred on Good Friday, on April 10, 2009 in Murfreesboro, Tennessee. Please share your thoughts on this. If any of the original editors from over 15 years ago are still present, it would be awesome to still have you around! Sharkeston (talk) 16:55, 10 July 2026 (UTC)[reply]
(Discuss) – WHX Dubai → ? – The full, official name of this international event is "World Health Expo Dubai". While the acronym "WHX Dubai" is used in branding, Wikipedia naming conventions (WP:ACROTITLE) strongly prefer the full, unabbreviated title for the main article to ensure encyclopedic clarity and accuracy. Moving it to the full name will better serve readers searching for the comprehensive expo title, while "WHX Dubai" will remain as a seamless redirect. Ezgiayoz (talk) 07:10, 10 July 2026 (UTC)[reply]
(Discuss) – Steam Machine → Steam MachinesSteam Machines – Steam Machines is a (discontinued) family of small form factor gaming computers, and a marketing term. The concept described by the article is plural, the article body already uses plural form. As it describes multiple devices, with differing names, some not including "Steam Machine" in their name moniker, using Steam Machine does not seem appropriate. I propose renaming it to Steam Machines, which will also align with marketing logotype used on the page and by Valve Corporation. There also exists Valve Steam Machine (prototype), from 2013, that was released in only 300 units (see section in the article of this talk page). 2026 Steam Machine's current Steam Machine (computer) title is also confusing. I'm not sure what it should be renamed to, I'm open to suggestions, and myself suggest Steam Machine (2026), or Steam Machine (2026 computer). I'm against using WP:DIFFCAPS title of just Steam Machine, as steam machine redirects to steam engine. Steam Machine (capitalized) should probably redirect to steam machine (disambiguation). It would also be helpful if we could agree on resolving it swifter than in 7 days. If you agree, please state so. Tracerneo (talk) 21:23, 24 June 2026 (UTC) — Relisting. –Maltazarianᚾparleyinvestigateᛅ 11:52, 2 July 2026 (UTC) — Relisting.TarnishedPathtalk06:49, 10 July 2026 (UTC)[reply]
(Discuss) – Saugus High School shooting → 2019 Saugus High School shooting2019 Saugus High School shooting – A lack of other notable shootings at Saugus High School does not imply that a year is not necessary, factors such as how identifiable the incident does, and this incident does not appear to reach that level of notoriety. Please note that WP:NCWWW states that most events titles should say when, where, and what happened. Years are not WP:OVERPRECISION (please note that exceptions to the precision criterion are a result of the application of other naming criterion) or only usable for disambiguation (if this were the case, then part of NCWWW would be basically irrelevant, and guidelines and policies should work in harmony, not in opposition to one another). Readers should not be confused if there have been other notable shootings at Saugus High School because if there had been, it should be mentioned and linked to in the article, like with the distinguish template. Please also note that for WP:NOYEAR to apply, you must establish that the event is as remotely as easily recognizable as the examples of no year events. Additionally, the sentence "The date is not needed when the article pertains to events that are unlikely to recur" refers to events involving individual people or persons. Regarding the previous RM, there was an apparent belief that this incident was similar to the Virginia Tech shooting, Parkland high school shooting, Uvalde school shooting, and Sandy Hook Elementary School shooting, but the key thing separating this shooting and those is how recognizable and impactful it was. Saugus pales in comparison to the massive impacts that those events had, some of whose repercussions are still being felt today across the United States and in some cases, elsewhere. With the thousands of shooting articles across Wikipedia, only a small number can manage without a year. Raskuly🐰 05:37, 3 July 2026 (UTC) — Relisting.TarnishedPathtalk06:30, 10 July 2026 (UTC)[reply]
(Discuss) – 2025 Prairieland ICE detention center incident → Prairieland casePrairieland case – Per WP:CONCISE and recent Talk page discussions. Although a clear WP:COMMONNAME has not emerged, the court cases (which continue as we speak) have eclipsed the original event in significance and WP:LASTING media coverage, and numerous media organizations refer to the event as some variation of "Prairieland _____ case". The most common (and, in my opinion, neutral) variation is "Prairieland shooting case"; "terrorism case" and "protest case" are also common, but each of these has WP:NPOV and MOS:LABEL issues. Other justifications: the name is consistent with other court cases in Category:2020s trials, all major search engines lead the reader to the correct topic if "Prairieland case" is used as a search term, and I think we can all agree that "incident" is too ambiguous and anodyne. Carguychris (talk) 20:47, 9 July 2026 (UTC)[reply]
(Discuss) – PennyMac Financial Services → Pennymac – The company rebranded in 2022 and is now referred to as "Pennymac" in independent reliable sources, (and not PennyMac with the capital M) making it the common name. Recent independent sources using this name include:[45][46][47][48][49] The company itself also uses "Pennymac" as its operative brand name, as seen on its official website.[50] Company entitities PennyMac Loan Services, LLC and PennyMac Mortgage Investment Trust do not follow the new branding with a lowercase 'M'. HomeWithAYard (talk) 20:24, 9 July 2026 (UTC)[reply]
(Discuss) – City of Manchester Stadium → Etihad StadiumEtihad Stadium – Clear WP:COMMONNAME. It simply isn't called City of Manchester Stadium by anyone anymore, with reliable sources having nearly exclusively used "Etihad Stadium" for years by now, to the point that finding a contemporary one that it genuinely takes effort to find contemporary ones that refer to it as "City of Manchester Stadium". This is about as clear-cut of a common name case as they come, and I was astounded to see the unrecognizable title we use for this article. –Maltazarianᚾparleyinvestigateᛅ 10:21, 2 July 2026 (UTC) — Relisting.Jeffrey34555 (talk) 19:37, 9 July 2026 (UTC)[reply]
(Discuss) – Wikipedia:Guide to deletion → Wikipedia:Guide to AfDWikipedia:Guide to AfD – The current title doesn't really match what the page covers. Right after the intro, the guide says outright that it deals with the process of addressing articles that contravene Verifiability and No original research, which are [...] nominated on Articles for deletion. Everything past that point, nomination, discussion, closure, behaviour, contesting the closure, and so on, is about how AfD specifically works. The other XfD venues for deleting non-article pages are only covered in one sentence which just links out to their own pages, not actually explained here. So, per WP:MOVE, the title is misleading or inaccurate, and the scope is effectively much narrower than the title suggests. "Guide to deletion" implies coverage of deletion as a whole, but the content has always been a guide to AfD specifically, not to the other XfD processes. One of the page's own shortcuts, WP:GAFD, already reads as "guide to AfD", so editors have been treating it that way informally for a while. Renaming it would just bring the title in line with the shortcut and the actual content. Also, note that we already have a guide to all the deletion processes as a whole at Wikipedia:Deletion process: speedy deletion, PROD, and the full set of XfD venues, along with the general closing procedures, consensus determination, relisting, and so on. That page covers the general "how deletion works across Wikipedia", and it already links out to venue-specific pages while trying to explain their common features. Renaming this page to Wikipedia:Guide to AfD would just stop this page from implying, by its title, that it's the general deletion guide, when we already have that at WP:Deletion process. FaviFake (talk) 14:41, 2 July 2026 (UTC) — Relisting.Jeffrey34555 (talk) 19:37, 9 July 2026 (UTC)[reply]
(Discuss) – Yay! (album) → Yay!Yay! – Nothing else that the disambiguation page at Yay seems to use an exclamation mark at the end. The other entries are an airport by IATA code, two languages (ISO 639-3 code and alternate name), and an acronym for Youth Assisting Youth. None of these could plausibly be referred to as "Yay!". Also, if moved, YAY! should be a redirect to Yay!. Mathguy2718 (talk) 19:30, 9 July 2026 (UTC)[reply]
(Discuss) – Harry Reid International Airport → Las Vegas AirportLas Vegas Airport – Primarily per WP:COMMONNAME: There are, from a bit of digging, many many more examples of coverage calling the airport “Las Vegas Airport” over “Harry Reid” - a search on Google Trends [51] reveals that when comparing “Las Vegas Airport”, “Las Vegas International Airport” and “Harry Reid International Airport”, the first of the three is by a massive margin the most searched for term. Additionally, the vast majority of news articles from the last 2 years or so use “Las Vegas Airport” or very similar in their titles, only using the full official title on occasion in the article body. Danners430tweaks made17:36, 9 July 2026 (UTC)[reply]
(Discuss) – Crocodilia → CrocodyliaCrocodylia – The article should be moved from Crocodilia to Crocodylia. Both spellings have historical usage, but modern systematic and taxonomic sources increasingly use Crocodylia, especially for the crown group containing living alligators, crocodiles, gharials, and their extinct descendants. Reptile Database uses Crocodylia, IUCN Red List taxonomic data also uses Crocodylia for species classifications, and recent phylogenetic literature commonly treats Crocodylia as the crown-group name. Since the article is about the taxonomic order/crown clade rather than a vernacular concept, Crocodylia is the better title, with Crocodilia retained as an alternative spelling redirect. コロネン (talk) 12:29, 2 July 2026 (UTC) — Relisting.1isall (talk | contribs) 13:38, 9 July 2026 (UTC)[reply]
The 7-day listing period has elapsed. Items below may be closed if there's a consensus, or if discussion has run its course and consensus could not be achieved.
(Discuss) – 2021 Qatari general election → 2021 Qatari Shura Council election – 1. Sources used in the article and sources overall overwhelmingly do not use the term "general election". 2. The official Qatar News Agency always calls it "Shura Council Elections", never "General", and Qatar has a "Media Support Committee for the Shura Council Elections" and a "Shura Council Elections Supervisory Committee".[12][13] 3. The term "general election" is ambiguous, and is often understood in English to mean elections that affect a government,[14] which is not the case here, nor in elections for similar bodies in other non-democratic countries, going against Precision from WP:CRITERIA. 4. WP:NCELECT does not have a specific guideline on "general election", and due to the particular nature of the Shura Council as a pseudo-legislature with limited powers, I believe that the appropriate guideline here is the following: "For elections to particular bodies or offices, default to the form "[date] [country name or adjectival form] [body/office] election"." Thanks and good tidings, غوّاص العلم (Ghawwas) (talk) 08:11, 1 July 2026 (UTC) غوّاص العلم (Ghawwas) (talk) 08:11, 1 July 2026 (UTC) — Relisting.Jeffrey34555 (talk) 03:57, 9 July 2026 (UTC)[reply]
Elapsed listings fall into the backlog after 24 hours. Consider relisting 8-day-old discussions with minimal participation.
(Discuss) – Novopavlivka offensive → Dnipropetrovsk Oblast offensive (2025–present) – I had already expressed concerns over this article's scope at Talk:Novopavlivka offensive#Scope (I'll be pinging some users from that discussion). Essentially I expressed some doubt over the decision to focus this article on the settlement of Novopavlivka. To me it seemed back then, and still does, that this article focused more simply on Russian advances into Dnipropetrovsk Oblast than on this little settlement. The article itself currently states the following: The locality itself [Novopavlivka] is not particularly strategic, though its location just over the border of the Dnipropetrovsk region makes it significant as Russia has not entered this oblast in the first three years of their full-scale invasion. Therefore, it would mainly mark a moral blow for Ukraine, should Russia cross into the Dnipropetrovsk region and seize Novopavlivka. It puts more weight on the simple fact that Russia has reentered this oblast than on the advances towards this particular settlement, and I would argue WP:RS coverage has focused more on this too. Novopavlivka is a small settlement of 3,439 people (2001). Typically we've had articles on offensives on specific settlements for small towns, larger than this one. I Know I'm Not Alone, the author of much of this article, did make some fair defense on the use of Novopavlivka as the article's focus at the aforementioned discussion. Nonetheless, as you can see on the map (outdated by the way), most of the territory taken during the offensive covered in this article is located in a different part of Dnipropetrovsk Oblast, near Velykomykhailivka. IiSmxyzXX also made some argumentation on this point and on the notion that this offensive being focused on Novopavlivka specifically might be WP:OR. I believe sources have focused more on the simple fact that Russia has achieved advances in a different oblast beyond Donetsk Oblast. This article is notable in my opinion largely due to this psychological and PR effect. Sources cited in this article seem to struggle giving this offensive a particular strategic sense, and I don't think there's many capable of doing this among the sources not already cited. Thus, I would like to propose renaming this article to better reflect its focus on, simply, Russian advances into this oblast beyond the Donbas region. It is necessary to differentiate these advances from the ones that took place in 2022 (see more at Russian occupation of Dnipropetrovsk Oblast#2022) and also to note the fact that this offensive is apparently still ongoing (though this article should be updated after the events of the 2026 Southern Ukraine counteroffensive). Such a format title is already employed in this topic area (e.g. Russo-Ukrainian war (2022–present), Dnieper campaign (2022–present)) and it suggests treating the topic in a similar fashion to other in my opinion comparable cases, such as the 2025 Sumy offensive. We could still mention Novopavlivka in some section header, it would be completely fair in my view to divide this article into two axes, one for Novopavlivka and another for Velykomykhailivka (we've already done stuff like this, see the sections at 2023 Ukrainian counteroffensive). "Dnipropetrovsk offensive (2025–present)" could also be an alternative WP:CONSISTENT with the aforementioned Sumy offensive that has taken place in the oblast and not the city, and in this particular case it would be unambiguous as the capital is not called Dnipropetrovsk but Dnipro. But then we also have Northeast Donetsk Oblast campaign for example. And given the apparent lack of a strategic single focus, with this article focusing more on military engagements taking place on a specific defined area, "campaign" might be a better choice over "offensive". I invite editors to discuss all possible options. Regards, SuperΨDro 00:21, 18 June 2026 (UTC) — Relisting.Jeffrey34555 (talk) 21:02, 25 June 2026 (UTC) — Relisting.BilledMammal (talk) 02:44, 8 July 2026 (UTC)[reply]
(Discuss) – Model Farms → Model Farms, New South WalesModel Farms, New South Wales – This page was recently moved from the target on the grounds that it was WP:PRIMARYTOPIC with no prior discussion. However, there is already a page called Model farms (lower case "f") that redirects to Demonstration farm. This has created an issue where the search result will differ depending on whether the term is input with uppercase or lowercase letters. There are also no hat notes on either page to account for this. The lifetime pageviews for Demonstration farm is over 39,000. The lead at Demonstration farm includes "model farm" as a bolded alternative name in the first sentence (although the redirect from "model farms" itself has only a bit over 100 pageviews). Model Farms, New South Wales had only 4766 lifetime pageviews at the time of the move. Determining WP:PRIMARYTOPIC is generally determined by consensus and requires us to consider a term with respect to usage if it is highly likely—much more likely than any other single topic, and more likely than all the other topics combined—to be the topic sought when a reader searches for that term. Based on the page view numbers, it is difficult to conclude that a reader searching the term "model farms" is seeking information on a relatively obscure locality within the Sydney suburb of Winston Hills as opposed to the much more likely alternative term for demostration farms. In the absence of a consensus around primary topic, disambiguation is required per WP:NCAUST. Dfadden (talk) 09:45, 24 June 2026 (UTC) — Relisting. –Maltazarianᚾparleyinvestigateᛅ14:11, 3 July 2026 (UTC)[reply]
(Discuss) – The Deep (character) → The Deep (The Boys) – I think it makes sense to have the DB be the franchise where this character comes from instead of (character). The current DB was probably done to match what most DBs are for pages on comic book characters, but characters from The Boys were written specifically for The Boys and not for the publisher to use in other works (a counter-example of this would be Kingpin (character) from Marvel Comics). ThePoggingEditor (talk) 17:11, 24 June 2026 (UTC) — Relisting.Destinyokhiria(talk / cont)17:47, 1 July 2026 (UTC)[reply]
(Discuss) – Operation Kikusui I → Operation Ten-Ichi-Go – I hate to open another move request so soon after the last one closed, but it looks like the previous move was done without reference to sources. Unfortunately, I believe the new name chosen was incorrect. The Japanese plan for resisting the American invasion of Okinawa was named Ten-Go Sakusen (Operation Heaven). In the initial planning, Ten-Go did not include a naval component. It only included ground force elements and a series of aerial kamikaze attacks designated Kikusui Sakusen (Operation Floating Chrysanthemum). After the Emperor noted the lack of the Navy's participation, the attack by the Yamato and company was added at the last minute. This was designated Ten-Ichi-Go Sakusen (Operation Heaven 1). The Japanese Wikipedia helpfully includes the actual text of the order, with source: 「航空攻撃有利なる場合、1YBは特令により出撃し敵攻略部隊を撃滅す。本作戦を天一号作戦と呼称す」 "Should conditions for an aerial offensive prove favorable, the 1st Surface Attack Unit shall sortie under special orders to annihilate the enemy invasion force. This operation shall be designated Operation Heaven 1." Source: Official Japanese war history (Senshi Sōsho), Vol 93, pg 258-259 Each of the ten Kikusui attacks was numbered one through ten, i.e. Kikusui I, Kikusui II. Note they do not include the word Sakusen (Operation). The aerial attacks are distinguished in reliable sources from the attack by the Yamato. For example, 'Chronology of the War at Sea, 1939-1945 : the Naval History of World War II' mentions the two separately (pg. 407). Tagging original requestor: @Palm Dogg, relisters: @Bunnypranav, @Sophisticatedevening, @Jeffery34964, and closer: @FOARPVoteins (talk) 02:44, 4 June 2026 (UTC) — Relisting. {{GearsDatapacks|talk|contribs|in solidarity}} 07:56, 11 June 2026 (UTC) — Relisting.BilledMammal (talk) 00:27, 24 June 2026 (UTC) — Relisting. –Maltazarianᚾparleyinvestigateᛅ06:34, 1 July 2026 (UTC)[reply]
