DOCSP-20482: TypeScript Benefits (#663)

* DOCSP-20482: TypeScript Benefits

(cherry picked from commit f2dc3ee)

Author: Chris Cho

source/fundamentals/typescript.txt

@@ -1,9 +1,9 @@
+.. node-fundamentals-typescript:
+
 ==========
 TypeScript
 ==========
 
-.. default-domain:: mongodb
-
 .. contents:: On this page
    :local:
    :backlinks: none
@@ -17,6 +17,10 @@ In this guide, you can learn about the **TypeScript** features and limitations
 of the MongoDB Node.js driver. TypeScript is a strongly typed programming
 language that compiles to JavaScript.
 
+The TypeScript compiler offers type checking in real time. Code editors that
+support TypeScript can provide autocomplete suggestions, display documentation
+inline, and identify type-related errors.
+
 All TypeScript features of the driver are optional. All valid JavaScript
 code written with the driver is also valid TypeScript code.
 
@@ -140,7 +144,7 @@ each of which includes a ``time`` field:
      name: string;
      mealtimes: Mealtime[];
    }
-   
+
    interface Mealtime{
      time: string;
      amount: number;
@@ -155,7 +159,7 @@ updates the nested ``time`` field of the ``Mealtime`` instance at index
    :emphasize-lines: 5
 
    const mealCounter = 1;
-   
+
    await collection.findOneAndUpdate(
      { name: "Lassie" },
      { $set: { [`mealtimes.${mealCounter}.time` as const]: '4:00 PM' } },
@@ -175,9 +179,9 @@ section.
 Working with the _id Field
 --------------------------
 
-MongoDB does not recommend specifying the ``_id`` as a part of your model. 
-Omitting the ``_id`` field makes the model more generic and reusable and more accurately 
-models the data important to an application. The Node driver’s TypeScript integration 
+MongoDB does not recommend specifying the ``_id`` as a part of your model.
+Omitting the ``_id`` field makes the model more generic and reusable and more accurately
+models the data important to an application. The Node driver’s TypeScript integration
 takes care of adding the ``_id`` field to the return types for relevant methods.
 
 If you need to work with the ``_id`` field in your models, see the below sections for
@@ -203,12 +207,12 @@ of insert operations. The following table describes how different
    * - | Unspecified
      - | Not applicable
      - | No
-     - | The driver creates an 
+     - | The driver creates an
          :manual:`ObjectId </reference/method/ObjectId/>`
          value for each inserted document.
 
    * - | Specified
-     - | ``{ _id: number };`` 
+     - | ``{ _id: number };``
      - | Yes
      - | If you do not specify a value for the ``_id`` field in an insert operation,
          the driver raises an error.
@@ -245,7 +249,7 @@ The following code uses the preceding interface along with the
 
    const database = client.db("<your database>");
    const collection = db.collection<OptionalId<IdPet>>("<your collection>");
-   
+
    collection.insertOne({
      name: "Spot",
      age: 2
@@ -276,7 +280,7 @@ from the method is of the type specified in the schema.
 
 However, if the type parameter you passed to your ``Collection`` instance does not
 include the ``_id`` field in its schema, the driver infers that the type of the
-``_id`` field returned from the method is ``ObjectId``. 
+``_id`` field returned from the method is ``ObjectId``.
 
 .. tip::
 
@@ -293,7 +297,7 @@ interface to return a document with an ``_id`` inferred to be of type ``ObjectId
 
    const database = client.db("<your database>");
    const collection = db.collection<Pet>("<your collection>");
-   
+
    const document = await collection.findOne({
      name: "Spot",
    });
@@ -352,7 +356,7 @@ document with an ``_id`` inferred to be of type ``number``:
       );
       // Compile time error: Property '_id' does not exist on type 'ProjectedDocument'.
       console.log(doc._id.generationTime);
-   
+
    To view a runnable TypeScript example that includes a find method applying a
    projection, see the
    :ref:`Find a Document <node-driver-findone-usage-example-code-snippet>` page.