Fix minor typos

docs/using/custom-images.md

@@ -55,7 +55,7 @@ FROM $BASE_IMAGE
 ...
 ```
 
-Include the below file in your project:
+Include the file below in your project:
 
 ```{literalinclude} recipe_code/docker-bake.python312.hcl
 :force:

docs/using/faq.md

@@ -2,7 +2,7 @@
 
 ## How to persist user data
 
-There are two types of data, which you might want to persist.
+There are two types of data you might want to persist.
 
 1. If you want to persist your environment (i.e. packages installed by `mamba`, `conda`, `pip`, `apt-get`, and so on),
    then you should create an inherited image and install packages only once while building your Dockerfile.
@@ -12,7 +12,7 @@ There are two types of data, which you might want to persist.
    ```{note}
    If you install a package inside a running container (for example you run `pip install <package>` in a terminal),
    it won't be preserved when you next run your image.
-   To make it work, install this package in your inherited image and rerun `docker build` command.
+   To make it work, install this package in your inherited image and rerun the `docker build` command.
    ```
 
 2. If you want to persist user data (files created by you, like `Python` scripts, notebooks, text files, and so on),
@@ -26,7 +26,7 @@ There are two types of data, which you might want to persist.
 
 We have lots of users with different packages they want to use.
 Adding them all is impossible, so we have several images to choose from.
-[Choose the image](selecting.md), that is closest to your needs, and feel free to [add your package on top of our images](recipes.md#using-mamba-install-recommended-or-pip-install-in-a-child-docker-image).
+[Choose the image](selecting.md) that is closest to your needs, and feel free to [add your package on top of our images](recipes.md#using-mamba-install-recommended-or-pip-install-in-a-child-docker-image).
 
 ## Who is `jovyan`
 

docs/using/running.md

@@ -16,7 +16,7 @@ The following are some common patterns.
 ### Example 1
 
 This command pulls the `jupyter/scipy-notebook` image tagged `2025-02-12` from Quay.io if it is not already present on the local host.
-It then starts a container running Jupyter Server with the JupyterLab frontend and exposes the server on host port 8888.
+It then starts a container running a Jupyter Server with the JupyterLab frontend and exposes the server on host port 8888.
 The server logs appear in the terminal and include a URL to the server.
 
 ```bash
@@ -54,7 +54,7 @@ docker rm eca4aa01751c
 ### Example 2
 
 This command pulls the `jupyter/r-notebook` image tagged `2025-02-12` from Quay.io if it is not already present on the local host.
-It then starts a container running Server and exposes the server on host port 10000.
+It then starts a container running a Jupyter Server and exposes the server on host port 10000.
 The server logs appear in the terminal and include a URL to the Server but with the internal container port (8888) instead of the correct host port (10000).
 
 ```bash
@@ -179,7 +179,7 @@ See the
 
 ## Using JupyterHub
 
-You can configure JupyterHub to launcher Docker containers from the Jupyter Docker Stacks images.
+You can configure JupyterHub to launch Docker containers from the Jupyter Docker Stacks images.
 If you've been following the [Zero to JupyterHub with Kubernetes](https://z2jh.jupyter.org/en/latest/) guide,
 see the [Use an existing Docker image](https://z2jh.jupyter.org/en/latest/jupyterhub/customizing/user-environment.html#choose-and-use-an-existing-docker-image) section for details.
 If you have a custom JupyterHub deployment, see the [Picking or building a Docker image](https://jupyterhub-dockerspawner.readthedocs.io/en/latest/docker-image.html)