sentence case

Author: hamelsmu

nbs/tutorials/blogging.ipynb

@@ -50,7 +50,7 @@
    "id": "0b71025a-455d-4cd7-a196-6ebd5cc4f519",
    "metadata": {},
    "source": [
-    "## Migrating From fastpages\n",
+    "## Migrating from fastpages\n",
     "\n",
     "If you previously had a fastpages site, we offer some utilities to help migrate you to Quarto.  **The migration is not holistic: you will likely have to manually correct some things that we are not able to automate.**\n",
     "\n",
@@ -136,11 +136,11 @@
    "id": "3f00ffc1-295a-4de5-b71f-92cde47d3a84",
    "metadata": {},
    "source": [
-    "### Configuration Options: fastpages vs. Quarto\n",
+    "### Configuration options: fastpages vs. Quarto\n",
     "\n",
     "fastpages (which was based on Jekyll) and Quarto offer different kinds of options and configurations for individual posts and at a site level.  Below are some tables that organize some of the most important features of fastpages and how it maps to Quarto.  Each link in the last column is specific to the relevant feature.\n",
     "\n",
-    "#### Post Level Front Matter\n",
+    "#### Post-level options\n",
     "\n",
     "Jekyll Front Matter | Quarto | Notes\n",
     "-- | -- | --\n",
@@ -158,7 +158,7 @@
     "\n",
     "\n",
     "\n",
-    "#### Site Level Options\n",
+    "#### Site-level options\n",
     "\n",
     "Jekyll site config | Quarto | Notes\n",
     "-- | -- | --\n",
@@ -181,7 +181,7 @@
    "id": "8ee5b80e-7931-4d03-8f3e-c8010c36279c",
    "metadata": {},
    "source": [
-    "## Publishing Your Blog\n",
+    "## Publishing your blog\n",
     "\n",
     "::: {.callout-warning}\n",
     "_This section is for stand-alone blogs that are not part of a nbdev documentation site.  If you want to create a blog within a nbdev documentation site, see [this section](#creating-a-blog-within-a-nbdev-project)._\n",
@@ -198,7 +198,7 @@
     ":::\n",
     "\n",
     "\n",
-    "## Creating A Blog Within A nbdev Project\n",
+    "## Creating a blog within a nbdev project\n",
     "\n",
     "In addition to a stand-alone blog that you might build with Quarto, you might want to include a blogging site in your nbdev project. This website has [a blog](../blog/) as well!  The easiest way to implement a blog is to emulate the directory structure of [this folder](https://github.com/fastai/nbdev/tree/master/nbs/blog).  The general steps are:\n",
     "\n",
@@ -243,7 +243,7 @@
     "5. **Create your first blog post**: You can emulate our example or create your own.  In each folder, create a `index.qmd` or `index.ipynb` file.  You can also put images and related assets in the same folder.\n",
     "\n",
     "\n",
-    "### Folder Structure\n",
+    "### Folder structure\n",
     "\n",
     "Below is an overview of the general folder structure for a blog within a nbdev site:\n",
     "\n",
@@ -267,7 +267,7 @@
     "- `posts/`: this a subdirectory for each blog post.\n",
     "- `YYYY-MM-DD-.../index.{qmd,ipynb}`: this is where you author the content of each individual blog post.\n",
     "\n",
-    "### Special Considerations For nbdev blogs\n",
+    "### Special considerations for nbdev blogs\n",
     "\n",
     "In contrast to standalone Quarto blogs, when you embed a blog in a nbdev website there are the following differences:\n",
     "\n",
@@ -280,7 +280,7 @@
    "id": "700589e2-aca4-44a4-b82d-167f63f55758",
    "metadata": {},
    "source": [
-    "## Using nbdev Features in Blogs Outside nbdev Projects\n",
+    "## Using nbdev features in blogs outside nbdev projects\n",
     "\n",
     "::: {.callout-warning}\n",
     "_This section is for stand-alone blogs that are not part of a nbdev documentation site.  If you create a blog within a nbdev documentation site, all nbdev features will automatically work._\n",

nbs/tutorials/modular_nbdev.ipynb

@@ -25,7 +25,7 @@
    "id": "b838f2c9-c24a-457c-9401-40708c5bfba0",
    "metadata": {},
    "source": [
-    "## Document Existing Code: `show_doc`\n",
+    "## Document existing code: `show_doc`\n",
     "\n",
     "nbdev allows you to document existing code, even code that is not written in nbdev! `nbdev.showdoc.show_doc` allows you to render beautiful API documentation in notebooks and on Quarto sites.  For example, you can render API documentation for `numpy.all` like this:  \n",
     "\n",
@@ -110,7 +110,7 @@
    "id": "5de0e130",
    "metadata": {},
    "source": [
-    "## Testing Notebooks: `nbdev_test`\n",
+    "## Testing notebooks: `nbdev_test`\n",
     "\n",
     "Testing notebooks can be very useful outside of nbdev, especially if you are documenting an existing code base and want to incorporate tests for your docs. The `nbdev_test` CLI utility allows you to accomplish this:"
    ]
@@ -138,7 +138,7 @@
    "id": "a2a38c4e",
    "metadata": {},
    "source": [
-    "## Export Code To Modules: `nb_export`"
+    "## Export code to modules: `nb_export`"
    ]
   },
   {
@@ -160,7 +160,7 @@
    "id": "77673b03",
    "metadata": {},
    "source": [
-    "## Jupyter-Git Integration\n",
+    "## Jupyter-git integration\n",
     "\n",
     "Jupyter and Git don't normally play well together, especially for things like merge conflicts.  We have outlined all of these problems, and our solutions in [this blog post](../blog/posts/2022-08-25-jupyter-git/index.qmd).  You can install our merge driver and hooks with the following command: \n",
     "\n",
@@ -197,7 +197,7 @@
    "id": "7f6c261f-d47f-4d1a-a695-05370f81a9c9",
    "metadata": {},
    "source": [
-    "## Python Packaging"
+    "## Python packaging"
    ]
   },
   {