MongoDB Documentation, Release 3.0.4 Consistency Review This occurs post-publication and is content focused. The goals of consistency reviews are to increase the internal consistency of the documentation as a whole. Insert relevant cross-references, update the style as needed, and provide background fact-checking. When possible, consistency reviews should be as systematic as possible and we should avoid encouraging stylistic and information drift by editing only small sections at a time. Subsequent Technical Review If the documentation needs to be updated following a change in functionality of the server or following the resolution of a user issue, changes may be significant enough to warrant additional technical review. These reviews follow the same form as the “initial technical review,” but is often less involved and covers a smaller area. Review Methods If you’re not a usual contributor to the documentation and would like to review something, you can submit reviews in any of the following methods: https://github.com/mongodb/docs/pull/[pull-request-id]/files Replace [pull-request-id] with the identifier of the pull request. Make all comments inline, using GitHub’s comment system. You may also provide comments directly on commits, or on the pull request itself but these commit-comments are archived in less coherent ways and generate less useful emails, while comments on the pull request lead to less specific changes to the document. If you insert lines that begin with any of the following annotations: followed by your comments, it will be easier for the original writer to locate your comments. The two dots .. format is a comment in reStructured Text, which will hide your comments from Sphinx and publication if you’re worried about that. This format is often easier for reviewers with larger portions of content to review. This document provides an overview of the global organization of the documentation resource. Refer to the notes below if you are having trouble understanding the reasoning behind a file’s current location, or if you want to add new documentation but aren’t sure how to integrate it into the existing resource. If you have questions, don’t hesitate to open a ticket in the Documentation Jira Project 42 or contact the documentation team$^{43}$. $^{41}$http://jira.mongodb.org/browse/DOCS $^{42}$https://jira.mongodb.org/browse/DOCS $^{43}$docs@mongodb.com .. TODO: TODO: .. TODO TODO • If you’re reviewing an open pull request in GitHub, the best way to comment is on the “overview diff,” which you can find by clicking on the “diff” button in the upper left portion of the screen. You can also use the following URL to reach this interface: • Leave feedback on Jira cases in the DOCS 41 project. These are better for more general changes that aren’t necessarily tied to a specific line, or affect multiple files. • Create a fork of the repository in your GitHub account, make any required changes and then create a pull request with your changes. MongoDB Manual Organization 939 13.5. Contribute to the Documentation