docs: Apply style guide edits (#8134)

docs/interfaces/notebooks.rst

@@ -8,7 +8,7 @@ You can use `Jupyter Notebooks <https://jupyter.org/>`__ to conveniently develop
 learning models, visualize the behavior of trained models, and manage the training lifecycle of a
 model manually. Determined makes launching and managing notebooks easy.
 
-Determined Notebooks provide the following benefits:
+Determined notebooks provide the following benefits:
 
 -  Jupyter Notebooks run in containerized environments on the cluster. This makes it easy to manage
    dependencies using images and virtual environments. The HTTP requests are passed through the
@@ -21,7 +21,7 @@ Determined Notebooks provide the following benefits:
    set ``notebook_timeout`` :ref:`option in your master config <master-config-notebook-timeout>`. To
    enable it for a particular notebook, set ``idle_timeout`` option in the notebook config.
 
-After a Notebook is terminated, it is not possible to restore the files that are not stored in the
+After a notebook is terminated, it is not possible to restore the files that are not stored in the
 persistent directories. **It is important to configure the cluster to mount persistent directories
 into the container and save files in the persistent directories in the container.** See
 :ref:`notebook-state` for more information.

docs/reference/deploy/config/master-config-reference.rst

@@ -242,7 +242,7 @@ behavior specified here. For more on scheduling behavior in Determined, see :ref
 ^^^^^^^^
 
    The scheduling policy to use when allocating resources between different tasks (experiments,
-   Notebooks, etc.). Defaults to ``fair_share``.
+   notebooks, etc.). Defaults to ``fair_share``.
 
    -  ``fair_share``: Tasks receive a proportional amount of the available resources depending on
       the resource they require and their weight.
@@ -252,7 +252,7 @@ behavior specified here. For more on scheduling behavior in Determined, see :ref
    -  ``priority``: Tasks are scheduled based on their priority, which can range from the values 1
       to 99 inclusive. Lower priority numbers indicate higher-priority tasks. A lower-priority task
       will never be scheduled while a higher-priority task is pending. Zero-slot tasks (e.g.,
-      CPU-only Notebooks, TensorBoards) are prioritized separately from tasks requiring slots (e.g.,
+      CPU-only notebooks, TensorBoards) are prioritized separately from tasks requiring slots (e.g.,
       experiments running on GPUs). Task priority can be assigned using the ``resources.priority``
       field. If a task does not specify a priority it is assigned the ``default_priority``.
 
@@ -751,7 +751,7 @@ Notebooks, etc.). Defaults to ``fair_share``.
 
    Tasks are scheduled based on their priority, which can range from the values 1 to 99 inclusive.
    Lower priority numbers indicate higher-priority tasks. A lower-priority task will never be
-   scheduled while a higher-priority task is pending. Zero-slot tasks (e.g., CPU-only Notebooks,
+   scheduled while a higher-priority task is pending. Zero-slot tasks (e.g., CPU-only notebooks,
    TensorBoards) are prioritized separately from tasks requiring slots (e.g., experiments running on
    GPUs). Task priority can be assigned using the ``resources.priority`` field. If a task does not
    specify a priority it is assigned the ``default_priority``.