Fix grammar.

Author: guzman-raphael

docs/src/tutorials/json.ipynb

@@ -51,7 +51,7 @@
    "source": [
     "For this exercise, let's imagine we work for an awesome company that is organizing a fun RC car race across various teams in the company. Let's see which team has the fastest car! 🏎️\n",
     "\n",
-    "This establishes 2 important entities: a `Team` and a `Car`. Normally we'd map this to their own dedicated table, however, let's assume that `Team` is well-structured but `Car` here is less structured then we'd prefer. In other words, the structure for what makes up a *car* is varing too much between entries (perhaps because users of the pipeline haven't agreed yet on the definition? 🤷).\n",
+    "This establishes 2 important entities: a `Team` and a `Car`. Normally we'd map this to their own dedicated table, however, let's assume that `Team` is well-structured but `Car` is less structured then we'd prefer. In other words, the structure for what makes up a *car* is varing too much between entries (perhaps because users of the pipeline haven't agreed yet on the definition? 🤷).\n",
     "\n",
     "This would make it a good use-case to keep `Team` as a table but make `Car` actually a `json` type defined within the `Team` table.\n",
     "\n",
@@ -145,9 +145,9 @@
    "id": "ee5e4dcf",
    "metadata": {},
    "source": [
-    "Next, business and marketing teams are up for registering their car.\n",
+    "Next, business and marketing teams are up and register their cars.\n",
     "\n",
-    "A few points to notice:\n",
+    "A few points to notice below:\n",
     "- The person signing up on behalf of marketing does not know the specifics of the car during registration but another team member will be updating this soon before the race.\n",
     "- Notice how the `business` and `engineering` teams appear to specify the same property but refer to it as `safety_inspected` and `inspected` respectfully."
    ]