Prior to submitting a review of a page move's close, please attempt to resolve any issues on the closer's talk page. See step one below.

While the page move close is under review, any involved editor is free to revert any undiscussed moves of a nominated page without those actions being considered a violation of Wikipedia:No wheel warring.

This review process should be focused on the move discussion and the subsequent results of the move discussion, not on the person who closed the discussion. If you have ongoing concerns about a closer, please consult with the closer or post at Wikipedia:Administrators' noticeboard/Incidents. Move review requests which cast aspersions or otherwise attack other editors may be speedily closed.

Do not request a move review if someone has boldly moved a page and you disagree. Instead, attempt to discuss it with the editor, and if the matter continues to be unresolved, start a formal WP:RM discussion on the article's talk page.

Do not request a move review simply because you disagree with the outcome of a page move discussion. While the comments in the move discussion may be discussed in order to assess the rough consensus of a close, this is not a forum to re-argue a closed discussion.

Disagreements with Wikipedia:Requested moves/Closing instructions (WP:RMCI), WP:Article titles, the Manual of Style, a naming convention or the community norm of consensus should be raised at the appropriate corresponding talk page.

CfDs and RfDs can only be reviewed here if the relevant discussion was limited in scope to renaming; CfDs or RfDs involving deletion should be reviewed at Wikipedia:Deletion review.

Editors desiring to initiate a move review should follow the steps listed below. In the reason parameter, editors should limit their requests to one or both of the following reasons:

• [Closer] did not follow the spirit and intent of WP:RMCI because [explain rationale here] in closing this requested move discussion.
• [Closer] was unaware of significant additional information not discussed in the page move discussion: [identify information here] and the discussion should be reopened and relisted.

Editors initiating a move review discussion should be familiar with the closing instructions provided in WP:RMCI.

Copy this template skeleton for most pages:

{{subst:move review list
|page=
|rm_page= <!--Not needed if the move discussion is on the talk page of the page-->
|rm_section= <!--Name of the section with the move request-->
|closer= <!--User name of editor who closed the move request-->
|closer_section= <!--Name of the section of closer's talk page where discussion took place-->
|reason=
}}  ~~~~

In general, commenters should prefix their comments with either Endorse or Overturn (optionally stating an alternative close) followed by their reasoning. Generally, the rationale should be an analysis of whether the closer properly followed Wikipedia:Requested moves/Closing instructions, whether it was within closer's discretion and reasonably interpreted consensus in the discussion, while keeping in mind the spirit of Wikipedia policy, precedent and project goal. Commenters should be familiar with WP:RMCI, which sets forth community norms for closers of page move discussions.

If the close is considered premature because of on-going discussion or if significant relevant information was not considered during the discussion, commenters should suggest Relist followed by their rationale.

Commenters should identify whether or not they were involved or uninvolved in the RM discussion under review.

The closer of the page move under discussion should feel free to provide additional rationale as to why they closed the RM in the manner they did and why they believe the close followed the spirit and intent of WP:RMCI.

Remember that move review is not an opportunity to rehash, expand upon or first offer your opinion on the proper title of the page in question – move review is not a do-over of the WP:RM discussion but is an opportunity to correct errors in the closing process (in the absence of significant new information). Thus, the action specified should be the editor's analysis of whether the close of the discussion was reasonable or unreasonable based on the debate and applicable policy and guidelines. Providing evidence such as page views, ghits, ngrams, challenging sourcing and naming conventions, etc. to defend a specific title choice is not within the purview of a move review. Evidence should be limited to demonstrating that the RM closer did or did not follow the spirit and intent of WP:RMCI in closing the page move discussion.

A nominated page should remain on move review for at least seven days. After seven days, an uninvolved editor will determine whether a consensus exists to either endorse the close or overturn the close. If that consensus is to Overturn Close, the MRV closer should take the appropriate actions to revert any title changes resulting from the RM close. If the consensus was to relist, the page should be relisted at Wikipedia:Requested moves, Wikipedia:Categories for discussion, or Wikipedia:Redirects for discussion. If the consensus is to Endorse Close, no further action is required on the article title. If the MRV closer finds that there is no consensus in the move review, then in most cases this has the same effect as Endorse Close and no action is required on the article title. However, in some cases, it may be more appropriate to treat a finding of "no consensus" as equivalent to a "relist"; MRV closers may use their discretion to determine which outcome is more appropriate.

Use {{subst:move review top}} and {{subst:move review bottom}} to close such discussions.

Also, add a result to the {{move review talk}} template on the talk page where the original discussion took place, e.g. {{move review talk|date=April 24 2015|result=Closure endorsed}}.

The following set of options represent the typical results of a move review decision, although complex page move discussions involving multiple title changes may require a combination of these options based on the specific details of the RM and MRV discussions.

Perspiration (talk|edit|history|logs|links|archive|watch) (RM) (Discussion with closer)

When including all comments from the initial discussion, regardless of whether they were directly about the proposal, the vote was evenly split at 50/50 (4:4). The closing message was 'no consensus', which is accurate based on the numbers alone. However, since WP:RMCI requires evaluating arguments as well as numbers, I will briefly summarize these: opposers preferred 'perspiration', feeling it sounded more encyclopedic (WP:TONE) and less ambiguous than 'sweat', referring to both the fluid and the process, thereby avoiding confusion about the article's focus. Supporters, on the other hand, emphasized the statistical prevalence of 'sweat' over 'perspiration' (WP:COMMONNAME, WP:MEDTITLE), refuted the claim that 'sweat' describes a different phenomenon than 'perspiration' when referring to the fluid, and advocated for a clear focus on either the fluid or the process. Overall, this decision appears to contrast factual arguments (statistics) with personal preferences. –Tobias (talk) 13:00, 4 November 2024 (UTC)[reply]

(Closer comment): while !votes with rationales like seems more encyclopedic are not especially helpful, there was a key argument on the "oppose" side that lead me to mark it "no consensus". (That said, WP:TONE plays some role and should not be entirely discarded. A formal tone is important.) Basically, the argument put forward by WhatamIdoing: Also, it's not clear to me whether this article ought to be about "the fluid" or about "the process of excreting the fluid". "Perspiration" works for both, but with the proposed name, it would have to be either sweat (the wet stuff itself, as a collection of water and some other chemicals) or sweating (the process of making the wet stuff; Diaphoresis). As this article currently covers both (and that seems fine to me), then having a name that covers both in the same grammatical form seems convenient. This argument is just as valid and as strong as the COMMONNAME-based one; we shouldn't be swayed into thinking that numbers-based rationales are somehow more worthy or more powerful. (I would also like to note: I did not make the close based on the numbers alone.) Sweat is a bit too ambiguous a term, and does not cover the entirety of the article subject. Therefore I think the arguments are equally matched. (Remember I don't have to defend the ambiguity argument as better than the other one, and I don't think it is. I just have to show it has equal weight). I would not characterize that argument as a personal preference.

If this response is unsatisfactory, I'm happy to elaborate further on why I think my close is appropriate. Cremastra (u — c) 13:31, 4 November 2024 (UTC)[reply]

• Relist. This discussion wasn't that well attended and since its especially controversial (otherwise we wouldn't be here), it could use more input from the community.VR _{(Please ping on reply)} 18:16, 4 November 2024 (UTC)[reply]
• Endorse (uninvolved): WP:TONE / WP:SLANG is a legitimate reason to oppose this proposed move, and that is basically what people mean by saying the current title "seems more encyclopedic". "Sweating" was also mentioned as a possibility, which also seems like a good candidate, but didn't gain clear traction. The RM was relisted and was open for more than two weeks. No consensus was evident, so the RM was closed as "no consensus", which seems fine. Less formal terminology is often avoided in Wikipedia article titles (Defecation, Feces, Urine, Sexual intercourse, etc.). —⁠ ⁠BarrelProof (talk) 13:00, 5 November 2024 (UTC)[reply]

Israel–Hamas war (talk|edit|history|logs|links|archive|watch) (RM) (Discussion with closer)

See also other post-move discussions here, here, here and here.

There was a broad consensus for a move of the title away from Hamas and towards Gaza based on increasing and converging use of Gaza by RS. While initially a move to Israel-Gaza war found mixed support, I proposed a compromise for a move to Gaza War, which found great support among editors as a middle ground solution. Despite this the move was closed as no consensus, and there were attempts by several editors to discuss a rereview with the closing editor, to which they did not agree with. To add to that, three editors who had voted against were found to be sockpuppets. This really needs a rereview to accurately reflect the established consensus. Makeandtoss (talk) 10:44, 4 November 2024 (UTC)[reply]

• Endorse (involved). Most editors didn’t participate in the alternative proposal, and their silence cannot be interpreted as endorsement of it. This is particularly the case because Gaza War has previously been considered and rejected. BilledMammal (talk) 13:27, 4 November 2024 (UTC)[reply]

  No one has claimed that their silence was an endorsement. As for the prior consensus argument, it is irrelevant given the passage of time and new sources. Makeandtoss (talk) 14:39, 4 November 2024 (UTC)[reply]

• There were two proposals. Here is a tally of the !vote count of each one:

Note some users !voted in both sections but most only !voted in one section.VR _{(Please ping on reply)} 17:48, 4 November 2024 (UTC)[reply]

• Endorse - Discussions of this size and time length are often incredibly hard to judge and more often than not both sides have equally strong policy arguments, even if one has more !votes behind it. In most cases, no consensus is the only possible and responsible close. I'd agree with the closer, give it a few more months (or less, as always if something changes more clearly), and maybe propose Gaza war or some variation of it next time around, but I don't see how a close in favor of any particular opinion could've been anything but a WP:SUPERVOTE.estar8806 (talk) ★ 20:25, 4 November 2024 (UTC)[reply]

AIM-174B (talk|edit|history|logs|links|archive|watch) (RM) (Discussion with closer)

For clarity, this request was ultimately closed by USER:Vpab15. It was initially closed (in good-faith) by USER:Asukite, and re-opened at my request. USER:Vpab15 ultimately closed it (in good-faith) ostensibly on-behalf of USER:Asukite, with a consensus of 3 (three) in-favor of KEEPING "AIM-174B" and 2 (two) in-favor of moving to "AIM-174." (full disclosure, I am the original author of the AIM-174 article) My position is that the article should be MOVED/REVERTED to “AIM-174.” My rationale for a MR:


1. "AIM-174 air-to-air missile" was moved to "AIM-174B", in good-faith, but without discussion, as per WP:RM. WP:BOLD does not exempt one from WP. At the very least the page should be reverted, per WP:RMUM. This was my rationale for attempting to move it on my own, originally, but was unable to do so for technical reasons, and ultimately began this move discussion. I recognize that "air-to-air missile" is unneeded due to WP:CONCISE.

2. The term “AIM-174” is freely-used -- admittedly alongside "AIM-174B" -- among sources and is easily recognizable.

3. WP:CONCISE and WP:PRECISE emphasize titles should be concise and precise, obviously. The title “AIM-174” is sufficiently precise to cover the entire missile family, including the AIM-174B variant. It avoids unnecessary complexity and redundancy.

4. WP:CONSISTENT, virtually all missiles -- and ALL U.S. air-to-air-missiles -- use the base model as their article title. While the AIM-174B is the only known operational variant, does that mean we should change the AIM-54 Phoenix article to "AIM-54C," given that, at the end of the Phoenix's life, it was the only operational variant? Per WP:CONSISTENT, see: AIM-4 Falcon, AIM-26 Falcon, AIM-47 Falcon, AIM-9 Sidewinder, AIM-7 Sparrow, AIM-54 Phoenix, AIM-68 Big Q, AIM-82, AIM-95 Agile, AIM-97 Seekbat, AIM-120 AMRAAM, AIM-132, AIM-152 AAAM, AIM-260

5. WP:DISAMBIG, WP:PRECISE; the current title “AIM-174B” may imply that there are multiple significant variants that require disambiguation. However, the primary subject of the article is the AIM-174 missile as a whole, with the AIM-174B being a variant, in-line with US missile naming conventions. Using “AIM-174” as the title encompasses all possible variants without the need for additional disambiguation or future discussion. FOR EXAMPLE: All AIM-9Xs are AIM-9s. All AIM-7Cs are AIM-7s. etc.

6. No one has made any attempt at editing the body or lead, which opens with "AIM-174." Indeed, as it stands currently, "AIM-174B" is not mentioned until the end of the intro. (and intro which, in full disclosure, I wrote) Indeed, I would argue that as a compromise, we could move the mention of the "AIM-174B" up to within the first sentence or two.
MWFwiki (talk) 23:40, 30 October 2024 (UTC)[reply]

Involved editor comment - I just want to note that I regret reverting my closure in this case as it has likely made the situation worse and now involved another editor who was inevitably dragged into this - thanks, in any case, and sorry for that.

I won't offer any opinion as to the close, but will note that of the prevalent voices in the discussion, there was an imbalance in civility and a clear lack of consensus. ASUKITE 03:34, 31 October 2024 (UTC)[reply]

• Overturn to no consensus, move to AIM-174 This is a very tricky discussion, because the original page was "AIM-174 air-to-air missile", it was moved unilaterally to "AIM-174B" recently in September (note the suffix), and the move discussion was to move it from "AIM-174B" to "AIM-174." In short, we have two different moves here: whether to remove "air-to-air missile" and whether the suffix should be used. In terms of dropping the "missile" part, I think there's clear consensus in that discussion to shorten the name. I do not see any consensus as to whether it should be AIM-174 or AIM-174B, though, but rather two opposing arguments without a clear policy winner. As a result, it should revert to whatever the status quo is, which in this case would be "AIM-174" without the "missile" part. If anything, I'm not sure discussion doesn't favour the shorter title - one opposer wants to maintain the status quo, but there isn't a status quo, and one of the non-specifically-voting commenters says it's unnecessary without being completely supportive of it. SportingFlyer T·C 05:08, 31 October 2024 (UTC)[reply]

  I think your analysis of the separation of the problems with the RM identifies the issue I have parsing the RM and this MRV. I do think that there are two issues that may have individually been separated and could be read as consensus against the longer disambiguator but no consensus for B/no B. I take issue with the participating mover's interpretation of policy "Unfortunately for you, a no consensus decision will result in this article staying here" in the RM, and would instead endorse your idea that aligns with policy, that a no consensus would take us back the original title, sans extra disambiguatotr. This is definitely a policy argument that is splitting hairs, but I think you've correctly identified the issues at play here. Bobby Cohn (talk) 14:52, 31 October 2024 (UTC)[reply]

  Yes, I saw that and completely disagree that a "no consensus" result would validate a recent page move. SportingFlyer T·C 17:26, 1 November 2024 (UTC)[reply]

• Endorse. The RM starter was not happy with a certain element of a bold move, while the other part was non-contentious. He contested said element of the move and failed, as the consensus was to keep the specific contested change made to the name. The bold move was therefore taken over by a consensus at RM: implicit consensus concerning the non-contentious element + explicit consensus concerning the remaining contentious element = consensus for the entire thing. The closer correctly recognized this.—Alalch E. 23:39, 3 November 2024 (UTC)[reply]
• Endorse. It's easy to see both sides of this issue, and I tend to agree with Alalch E. that the closer correctly read the RM survey and discussion. This closure was reasonable and in line with the closing instructions. P.I. Ellsworth , ed.  05:00, 4 November 2024 (UTC)[reply]

Nationality law of North Macedonia (talk|edit|history|logs|links|archive|watch) (RM) (Discussion with closer)

The move request for renaming Nationality law of North Macedonia to "North Macedonian nationality law" was closed as not move, (although with votes 3-2 in favour of my proposal), and the closer relied the decision on a statement of WP:MOSMAC that is not part of the community consensus reached in the 2019-RFC. This statement tells us Article names, categories, and templates should avoid adjectival use altogether.

There are two main problems with this statement and the closure of the move request:

1) A recent move request for renaming Macedonian denar to "Denar of North Macedonia" was rejected, and the followed-up move review was rejected unanimously, and none of the editors was convinced about the above statement, which I include in the move review. The two different decisions made in these two recent move requests tell us that decisions are made without considering wikipedia policies WP:NC and guidelines WP:MOSMAC. If there is a guideline that tells us to avoid adjectives in article titles, then Macedonian denar should be renamed to "Denar of North Macedonia". If this is not true, then Nationality law of North Macedonia should be renamed to "North Macedonian nationality law". Either way is okay, but my brain cannot accept double standards by pointing to the same guideline/exception/statement. One of the participants in the two move requests opposed Denar of North Macedonia but then strongly defended Nationality law of North Macedonia, pushing double standards in a non-scientific way.

2) I will share here some research that I did and already discussed with the closer and shows that the closer was trapped (me too as well a few weeks ago) by a statement, the validity of which has been raised in Talk:2019 North Macedonian presidential election#Article title move and includes a discussion about the statement: Article names, categories, and templates should avoid adjectival use altogether started by an editor, FlavrSavr, who was involved in the RFC 2019 and who opposed "North" in all cases (shown in the votes in all questions).

Editors Teratix and Number 57 participated in the long discussion with FlavrSavr.

FlavrSavr said: The actual policy clearly states that Article names, categories, and templates should avoid adjectival use altogether. and specifies in which cases "North Macedonian" may be used.

Number57 said: Then whoever has formulated the policy has ignored the outcome of the RfC. Perhaps this needs to be flagged up at WP:AN or somewhere, as it's not really acceptable for a clear outcome from a community discussion to be ignored when translating it into policy.

FlavrSavr then responded to Number 57 with a long message that includes: The sentence in question was proposed by me and inspired by Argean's and other comments in the RfC - this really was a no-brainer for most of us as it seems to be a natural and neutral resolution, and this wasn't opposed by anyone.

MJL (main contributor of WP:MOSMAC) joined the discussion and added: Actually, on a second read through, I have become very concerned by Number 57's comments.

Future Perfect at Sunrise joined the discussion and added: The sentence in question ... was not covered by the original RfC but was written into the draft unilaterally by MJL – certainly with the best of intentions. and ... And if there are groups of articles where local editors consider adjectival titles preferable for WP:CONSISTENCY reasons, we definitely have a problem and I'm not sure at all we should treat that WP:NCMAC sentence as authoritative.

qedk (one of the three editors in the closing of RFC 2019) commented: Since, the LOCALCONSENSUS surrounding the inclusion of that singular sentence has certainly changed, either it should be removed, or reframed in a manner, where it doesn't sound like policy. And given, WP:LOCALCONSENSUS explicity states — Consensus among a limited group of editors, at one place and time, cannot override community consensus on a wider scale, this particular statement cannot be held above the policy formed at the behest of the community. With thanks.

Argean joined the discussion and said: This particular sentence was proposed by FlavrSavr to be added in Future Perfect at Sunrise's first draft and was never questioned by anybody until now.

To remind you that FlavrSavr was involved in the RFC 2019 and opposed "North", so the idea of adding this special statement to WP:MOSMAC was a way to avoid the community consensus as much as possible and was proposed by an editor who disagrees with "North Macedonian", and this was done only after the RFC 2019. Not fair at all in my opinion.

One of the last comments of this discussion was by qedk, who is one of the three closers of the RFC 2019.

qedk said: To note for posterity's sake, the post-RfC drafting was mostly done by FPaS and MJL, and with SilentResident, Argean, Khajidha, FlavrSavr chipping in. Now, if out of those we already have two editors (FPaS and Khajidha in contention, on different things), you cannot say that the LOCALCONSENSUS persists. Noting again, that Teratix and Number 57 do not see it as an accurate summarization as well. I do not mean to question it when you say that it's in good intent and that it's meant to prevent conflicts but what I am saying is, you cannot have it override community consensus, which in this case, was clear and not a LOCALCONSENSUS.

All these prove that the statement about articles has been disputed by multiple editors already, but was not removed from WP:MOSMAC although suggested by the closing panel of the RFC 2019. The argument of the closer of this move request about this statement that doesn't allow adjectives in titles is incorrect, and couldn't be correct because WP:LOCALCONSENSUS cannot override community consensus achieved in 2019-RFC, in which The closing panel agrees that there is consensus for Both "North Macedonian" and "... of North Macedonia", where a similar form would be used for other countries. e.g. the North Macedonian Government or the Government of North Macedonia. for State-associated and other public entities.

The second argument of the closer about implicit consensus on the WP:MOSMAC guidelines (discussed in the talk page) because nobody removed this incorrect sentence against community consensus is also incorrect because we have multiple examples of article titles that use the adjective, see North Macedonian passport, 2019 North Macedonian presidential election, 2020 North Macedonian parliamentary election, 2024 North Macedonian presidential election, and 2024 North Macedonian parliamentary election. As already mentioned in the move review for Macedonian denar, the reason WP:MOSMAC was used in these examples but not in Macedonian denar and Nationality law of North Macedonia is the lack of experienced editors and the law participation that are eliminated by editors with double standards.

The experienced editors @Number 57 and @Teratix have been consistently using WP:MOSMAC for years in pages of North Macedonian elections, and I don't understand why we need to use double standards enforced by a single editor in other pages.

Nationality law of North Macedonia is completely inconsistent with all other pages of Category:Nationality_law and should be moved all in line with WP:CONSISTENT and WP:MOSMAC and 2019-RFC community consensus.

Thank you all for your time. Cheers! Open Free Eye (talk) 22:44, 30 October 2024 (UTC)[reply]

Comment from closer - First off, the move request was closed as no consensus, not as not moved. Additionally, I’m slightly unsure if the nominator is aware about WP:NOTAVOTE, as part of their opening statement here explicitly mentions a vote count: although with votes 3-2 in favour of my proposal. estar8806 (talk) ★ 23:38, 30 October 2024 (UTC)[reply]

• Endorse. As long as WP:MOSMAC says what it does, no consensus is the only possible closure; it's a classic case of "If the discussion shows that some people think one policy is controlling, and some another, the closer is expected to close by judging which view has the predominant number of responsible Wikipedians supporting it, not personally select which is the better policy". The main concern here seems to be that MOSMAC itself doesn't reflect consensus, but that's not an issue for move review: it should be raised on the guideline's talk page and/or in a new RfC. Extraordinary Writ (talk) 01:25, 31 October 2024 (UTC)[reply]
• Endorse two distinct policy interpretations without any majority in favour of one or the other, there's no other way to close this. SportingFlyer T·C 02:12, 31 October 2024 (UTC)[reply]
• Endorse (uninvolved). Appropriate closure of no consensus, two appropriately argued policies that neither may be discounted. Bobby Cohn (talk) 14:34, 31 October 2024 (UTC)[reply]
• Endorse - On the one hand, the close of No Consensus correctly summarizes a lengthy and inconclusive discussion. On the other hand, the appellant's statement, at 1183 words, is also lengthy and inconclusive. Should our instructions for opening a Move Review include a statement that concise statements are usually more effective? Robert McClenon (talk) 17:15, 31 October 2024 (UTC)[reply]
• Comment by nominator Thank you everybody for your comments, very appreciated! One question though: votes don't count, arguments count, and WP:LOCALCONSENSUS cannot override community consensus as correctly or incorrectly written in WP:MOSMAC. So far so good. Then who can explain me why "Denar of North Macedonia" was rejected in the move request and the move review, and now "North Macedonian nationality law" is also rejected in the move request and move review by using the opposite argument? Both the denar and nationality law fall into the same category of WP:MOSMAC -- State-associated and other public entities -- I really want to know. I see double standards here. You look at the problem locally by focusing on the tree but you miss the whole forest. Cheers! Open Free Eye (talk) 19:09, 31 October 2024 (UTC)[reply]

  Both moves were closed as "no consensus" which shouldn't be taken as acknowledgement that either of the current titles are the "correct" ones. It just means that there wasn't consensus for or against the moves, which means the end result is maintaining the status quo. RachelTensions (talk) 20:29, 2 November 2024 (UTC)[reply]

Consensus on Wikipedia neither requires unanimity (which is ideal but rarely achievable), nor is it the result of a vote.

editors open a section on the associated talk page and try to work out the dispute through discussion, using reasons based in policy, sources, and common sense; they can also suggest alternative solutions or compromises that may satisfy all concerns.

However, in line with the reliable sources, adjectives may still be used when referring to such institutions in generic terms (e.g. the Greek and North Macedonian prime ministers), especially where the possessive form would be grammatically cumbersome or unnatural. While reliable sources continue to use both plain "Macedonian" and "North Macedonian" in such contexts, the majority opinion in the RfC favored the fuller form, "North Macedonian".

Article names, categories, and templates should avoid adjectival use altogether. The use of neutral formulations such as "of North Macedonia", "in North Macedonia," etc. is preferred.

List of Reliable Sources (North Macedonian denar: 135 findings, North Macedonia denar: 57 findings, Macedonian denar: 89 findings)

Generally, article titles are based on what the subject is called in reliable sources. When this offers multiple possibilities, editors choose among them by considering several principles: the ideal article title precisely identifies the subject; it is short, natural, distinguishable and recognizable; and resembles titles for similar articles.

In the absence of a clearer consensus on which of the two to prefer, it is recommended to use the longer form where ambiguity might be an issue (especially on first introducing the topic).

Consensus among a limited group of editors, at one place and time, cannot override community consensus on a wider scale. For instance, unless they can convince the broader community that such action is right, participants in a WikiProject cannot decide that some generally accepted policy or guideline does not apply to articles within its scope

Search Move review archives Wikipedia:Move review

• Category:Pages at move review
• Category:Closed move reviews
• Wikipedia:Deletion review
• Subpages of this page