DOCSP-45255-mongosh-compatibility-changes-clarification (#365)

* DOCSP-45255-mongosh-compatibility-changes-clarification

* remove mongosh and legacy mongo shell links for consistency

* clarification

Author: amalhotra-mdb

source/reference/compatibility.txt

@@ -205,27 +205,31 @@ in ``mongosh`` better align with the types used by the MongoDB Drivers.
 Undefined Values
 ----------------
 
-The undefined BSON type is `deprecated <https://bsonspec.org/spec.html>`__ in
-:binary:`bin.mongosh`. If you insert a document with the undefined JS type in
-:binary:`bin.mongosh`, your deployment replaces the undefined value in your 
+The undefined BSON type is `deprecated <https://bsonspec.org/spec.html>`__. 
+If you try to insert a document with the undefined JS type in
+``mongosh``, your deployment replaces the undefined value in your 
 document with the BSON null value. There is no supported way of inserting undefined
-values into your database using :binary:`bin.mongosh`.
+values into your database using ``mongosh``.
 
 For example, consider running the following code to insert a document in
-:binary:`bin.mongosh`:
+``mongosh``:
 
 .. code-block:: javascript
 
    db.people.insertOne( { name : "Sally", age : undefined } )
 
-When you run this code in :binary:`bin.mongosh`, the shell inserts 
+When you run this code in ``mongosh``, the shell inserts 
 the following document: 
 
 .. code-block:: javascript
    "copyable: false
 
    { name : "Sally", age : null }
 
+``mongosh`` represents any BSON undefined values stored using other tools, such as 
+the `Go Driver <https://www.mongodb.com/docs/drivers/go/current/>`__ or the 
+legacy ``mongo`` shell, as null.
+
 Object Quoting Behavior
 -----------------------