Use consistent terminology when referring to the MongoDB shell in docs

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Trivial - P5
    • 1.16.0
    • Affects Version/s: None
    • Component/s: Docs
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The docs refers to the MongoDB shell inconsistently. Consider:

      ~/workspace/mongodb/phplib/docs/upgrade.txt:
        337  
        338  While the ``save`` method does have its uses for interactive environments, such
        339: as the ``mongo`` shell, it was intentionally excluded from the
        340  `CRUD specification <https://github.com/mongodb/specifications/blob/master/source/crud/crud.rst>`_
        341  for language drivers. Generally, application code should know if the document
      
      ~/workspace/mongodb/phplib/docs/reference/method/MongoDBDatabase-createCollection.txt:
         27     using the :phpmethod:`MongoDB\\Database::createCollection()` method, or using
         28     :manual:`db.createCollection() </reference/method/db.createCollection>` in
         29:    the :program:`mongo` shell.
         30  
         31     Explicitly creating collections enables you to create
      
      ~/workspace/mongodb/phplib/docs/tutorial/modeling-bson-data.txt:
        141     }
        142  
        143: The same document in the MongoDB shell might display as:
        144  
        145  .. code-block:: js
      

      We should use consistent terminology, such as "MongoDB shell".

              Assignee:
              Jérôme Tamarelle
              Reporter:
              Jeremy Mikola
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: