Cleanup README.md

Author: mathbunnyru

README.md

@@ -10,7 +10,7 @@ Possible **use cases** include:
 - Creating a JupyterHub demo environment that you can spin up relatively
   quickly.
 - Providing a multi-user Jupyter Notebook environment for small classes,
-  teams, or departments.
+  teams or departments.
 
 ## Disclaimer
 
@@ -31,7 +31,7 @@ Key components of this reference deployment are:
   in a Docker container on the host.
 
 - **Authenticator**: Uses [Native Authenticator](https://github.com/jupyterhub/nativeauthenticator) to authenticate users.
-  Any user will be allowed to sign-up
+  Any user will be allowed to sign up.
 
 - **Spawner**:Uses [DockerSpawner](https://github.com/jupyter/dockerspawner)
   to spawn single-user Jupyter Notebook servers in separate Docker
@@ -56,7 +56,7 @@ This deployment uses Docker, via [Docker Compose](https://docs.docker.com/compos
 
 This deployment uses [JupyterHub Native Authenticator](https://native-authenticator.readthedocs.io/en/latest/) to authenticate users.
 
-1. An single `admin` user will be enabled be default. Any user will be allowed to signup.
+1. An single `admin` user will be enabled by default. Any user will be allowed to sign up.
 
 ## Build the JupyterHub Docker image
 
@@ -79,7 +79,7 @@ To specify which Notebook image to spawn for users, you set the value of the
 Whether you build a custom Notebook image or pull an image from a public or
 private Docker registry, the image must reside on the host.
 
-If the Notebook image does not exist on host, Docker will attempt to pull the
+If the Notebook image does not exist on the host, Docker will attempt to pull the
 image the first time a user attempts to start his or her server. In such cases,
 JupyterHub may timeout if the image being pulled is large, so it is better to
 pull the image to the host before running JupyterHub.
@@ -142,7 +142,7 @@ c.DockerSpawner.image = os.environ['DOCKER_NOTEBOOK_IMAGE']
 
 ### If I change the name of the Notebook server image to spawn, do I need to restart JupyterHub?
 
-Yes. JupyterHub reads its configuration which includes the container image
+Yes. JupyterHub reads its configuration, which includes the container image
 name for DockerSpawner. JupyterHub uses this configuration to determine the
 Notebook server image to spawn during startup.
 
@@ -156,9 +156,9 @@ again to their individual notebook servers. However, users may need to
 refresh their browser to re-establish connections to the running Notebook
 kernels.
 
-### How can I backup a user's notebook directory?
+### How can I back up a user's notebook directory?
 
-There are multiple ways to [backup and restore](https://docs.docker.com/engine/userguide/containers/dockervolumes/#backup-restore-or-migrate-data-volumes) data in Docker containers.
+There are multiple ways to [Back up and restore data](https://docs.docker.com/desktop/backup-and-restore/) in Docker containers.
 
 Suppose you have the following running containers:
 
@@ -178,7 +178,7 @@ In this deployment, the user's notebook directories (`/home/jovyan/work`) are ba
     [{jtyberg /var/lib/docker/volumes/jtyberg/_data /home/jovyan/work local rw true rprivate}]
 ```
 
-We can backup the user's notebook directory by running a separate container that mounts the user's volume and creates a tarball of the directory.
+We can back up the user's notebook directory by running a separate container that mounts the user's volume and creates a tarball of the directory.
 
 ```bash
 docker run --rm \