diff --git a/docs/source/admin/upgrading.rst b/docs/source/admin/upgrading.rst index efe98c27..5b7cc988 100644 --- a/docs/source/admin/upgrading.rst +++ b/docs/source/admin/upgrading.rst @@ -6,9 +6,8 @@ JupyterHub offers easy upgrade pathways between minor versions. This document describes how to do these upgrades. If you are using :ref:`a JupyterHub distribution `, you -should consult the distribution's documentation on how to upgrade. This -document is if you have set up your own JupyterHub without using a -distribution. +should consult the distribution's documentation on how to upgrade. This documentation is +for those who have set up their JupyterHub without using a distribution. It is long because is pretty detailed! Most likely, upgrading JupyterHub is painless, quick and with minimal user interruption. diff --git a/docs/source/getting-started/security-basics.rst b/docs/source/getting-started/security-basics.rst index 661b3832..8f5aec11 100644 --- a/docs/source/getting-started/security-basics.rst +++ b/docs/source/getting-started/security-basics.rst @@ -31,7 +31,7 @@ Using an SSL certificate This will require you to obtain an official, trusted SSL certificate or create a self-signed certificate. Once you have obtained and installed a key and -certificate you need to specify their locations in the ``jupyterhub_config.py`` +certificate, you need to specify their locations in the ``jupyterhub_config.py`` configuration file as follows: .. code-block:: python @@ -233,7 +233,7 @@ jupyterhub-session-id This is a random string, meaningless in itself, and the only cookie shared by the Hub and single-user servers. -Its sole purpose is to coordinate logout of the multiple OAuth cookies. +Its sole purpose is to coordinate the logout of multiple OAuth cookies. This cookie is set to ``/`` so all endpoints can receive it, or clear it, etc.