This article walks you through the steps to submit a minor correction or update to a Mozilla Support Knowledge Base (KB) article.

Before you start

Before making any edits, it's important to know what qualifies as a minor change. Please check out Minor vs major changes to learn more about what qualifies as minor vs major changes.

Steps to submit a minor update

Navigate to the article’s editor

1. Find an article you want to edit and navigate to the article page.
2. Check the revision history by clicking on the Show History menu from the right sidebar to see recent edits. Make sure that there’s no pending revisions that may have the fix you’re trying to make to avoid duplicate work.
3. If you find another pending revision and you want to make sure your fix won’t conflict with it, you may submit a new revision based on that revision by clicking the pencil icon from the History page.
4. If you don’t want to base your edit on the previous revision, simply click on the Edit Article menu from the same sidebar to display the article’s editor.

Make your edit and submit your revision

1. Make your changes in the Content text box. Remember that KB uses a custom wiki syntax (not Markdown). Take a moment to familiarize yourself with the formatting rules before editing.

   

2. Click Preview Content or Preview Changes at the bottom of the page if you wish, then click Submit for Review.
3. In the Submit Your Changes dialog box that appears, describe your changes in 1-2 sentences and click Submit. Please refer to the next section to learn more about providing a description of your proposed changes.
4. You’re basically done! Once your revision is submitted, you’ll be redirected to the History page, where your revision will appear at the top marked as Unreviewed. At this point, you just need to wait for a reviewer to approve your changes.

Revision comment

All KB editors are required to use the revision comment box when submitting new articles or revisions. This comment provides essential context to reviewers and other stakeholders.

Required uses for revision comments:

• Describing the nature and purpose of the changes.
• Explaining the scope of impact of the revision, such as feature availability or release readiness.
• Associating the edit with a Bugzilla ticket (e.g., “Related to Bugzilla #1234567”).
• Indicating a specific approval requirement (e.g., “Staff approval is needed”).
• Indicating additional information that the community needs to know (e.g., "Do not localize - internal translation in progress").

What happens after you submit a revision?

Once you submit a revision, your revision will show up in the Unreviewed Changes page. Mozilla staff and KB reviewers review this queue at least once per week.

If your revision is tied to a specific product release and requires a faster turnaround, you may email kb-reviewers@mozilla.com to request an expedited review.

Discover other articles to edit

Looking for more ways to contribute? Here are some great places to find articles that may need improvements:

• Need Changes list – this list can be sorted by product. Clicking a link will open the article's History page. From there, click Article under Editing Tools to view the article, click Edit Article to update the article or click Discussion to discuss needed changes.
• Knowledge Base Overview – this list can be sorted by product and category. It includes a Status column for pending reviews and a Needs Update column for needed changes.

For more guidelines on Knowledge Base contribution, see these articles.