Compare Revisions

Learn about the review process at Mozilla Support, when you submit an edit to a Knowledge Base article

All edits to the Mozilla Support Knowledge Base go through a [[Article review guidelines for KB reviewers|review process]] before they are published. This helps ensure that our support content stays accurate, up to date, and easy for users to understand. This article explains what to expect after you submit a KB revision. __TOC__ =What happens after you submit a revision?= Once you successfully submit a revision, that revision will be visible on the History page of the article where you can check the review status from the Status column. Here’s what the status means: * '''Unreviewed:''' Revision has not been reviewed. * '''Current:''' Indicates a revision with the current approved content. * '''Approved:''' The revision has been approved in the past but the article has a more recent update. * '''Reviewed:''' Has been reviewed in the past but not approved. Reviewers are usually community volunteers or Mozilla staff who have been trained to maintain the quality and consistency of SUMO content. =Review criteria= When reviewing your edit, here are the criteria that the reviewers are checking for: * Accuracy: Is the content technically correct and up to date? * Clarity: Is the language simple and clear for non-technical users? * Style: Does it follow SUMO’s writing, tone, and formatting conventions? * Scope: Does the change match the purpose of the article? ==If revisions are deferred== Sometimes, reviewers will defer a revision instead of approving it. Here are some potential reasons for deferral: * Your edit does not meet the criteria listed above * The steps or information in the revision is incomplete * The revision is inaccurate or not applicable to the article’s scope What happens with a deferred revision: * The reviewer may leave feedback asking for changes or clarification * Your revision will stay in the reviewed and unapproved state until a new version is submitted * You can make edits and resubmit your revision for review. However, don’t be discouraged! Deferral is a normal part of the process and a great way to learn! =How long does it take to get a revision reviewed?= All submitted changes to SUMO content are reviewed by Mozilla staff and contributors with KB Review access through the [/contributors/unreviewed unreviewed changes queue]. ==Turnaround expectations== For revisions that require Mozilla staff approval, here are a few things to expect: * Mozilla’s Content staff review the unreviewed list at least once per week. * However, in a case of high volume, approval of revisions may take up to 2–3 weeks. * Timelines are subject to change based on internal workload and staffing. * If an unreviewed revision has not been approved after 4 weeks, contributors can escalate the review process by contacting the [[Meet the Team|Community Managers]] directly or by submitting a Bugzilla ticket that includes the following: ** Article title ** Article URL ** Original date of the revision ==Escalation== If your revision has not been reviewed within the [[#w_turnaround-expectations|standard turnaround time]] or tied to a specific product release and requires a faster turnaround, you may contact the KB reviewers by sending an email to [mailto:kb-reviewers@mozilla.com kb-reviewers@mozilla.com]. You may also review the [[Contributor access, communication and escalation channels]] article to learn more about other escalation channels. =Tips for successful edits= * Only make minor fixes unless you’ve [[How to submit a SUMO Knowledge Base content request|submitted a content request]] for a major update. Mozilla staff may not review revisions with major changes unless a Bugzilla content request has been submitted. * Be clear in the revision summary so reviewers understand your intent. * Follow the [[Markup chart|KB markup guide]] and our [[Writing guide for Knowledge Base articles#w_style-guide-and-copy-rules|content style guide]].