From d65e2daa157e22ae86a3b75b229277413528be15 Mon Sep 17 00:00:00 2001 From: Min RK Date: Thu, 1 Jun 2023 12:55:07 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Simon Li --- docs/source/howto/rest.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/source/howto/rest.md b/docs/source/howto/rest.md index 66f8595d..886acdc5 100644 --- a/docs/source/howto/rest.md +++ b/docs/source/howto/rest.md @@ -64,7 +64,7 @@ A good way of generating an API token is by running: openssl rand -hex 32 ``` -This `openssl` command generates a potential token that can then be added to JupyterHub configuration in `jupyterhub_config.py`. +This `openssl` command generates a random token that can be added to the JupyterHub configuration in `jupyterhub_config.py`. For external services, this would be registered with JupyterHub via configuration: @@ -82,7 +82,7 @@ At this point, requests authenticated with the token will be associated with The ```{note} You can also load additional tokens for users via the `JupyterHub.api_tokens` configuration. -However, this option has been softly deprecated since the introduction of services. +However, this option has been deprecated since the introduction of services. ``` ## Assigning permissions to a token