[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

docs/howto/user-env/notebook-interfaces.md

@@ -19,8 +19,8 @@ When you log in & start your server, by default the URL in your browser
 will be something like `/user/<username>/tree`. The `/tree` is what
 tells the notebook server to give you the classic notebook interface.
 
--   **For the JupyterLab interface**: change `/tree` to `/lab`.
--   **For the nteract interface**: change `/tree` to `/nteract`
+- **For the JupyterLab interface**: change `/tree` to `/lab`.
+- **For the nteract interface**: change `/tree` to `/nteract`
 
 You can play around with them and see what fits your use cases best.
 

docs/howto/user-env/server-resources.md

@@ -4,5 +4,5 @@
 
 To configure the resources that are available to your users (such as
 RAM, CPU and Disk Space), see the section [](#tljh-set-user-limits).
-For information on **resizing** the environment available to users *after* you\'ve created
+For information on **resizing** the environment available to users _after_ you\'ve created
 your JupyterHub, see [](#howto-admin-resize).

docs/howto/user-env/user-environment.md

@@ -167,48 +167,48 @@ miniconda 4.5.4, which meant a Python 3.6 environment.
 
 To upgrade the Python version of the user environment, one can:
 
--   **Start fresh on a machine that doesn\'t have TLJH already
-    installed.**
+- **Start fresh on a machine that doesn\'t have TLJH already
+  installed.**
 
-    See the [](#install-installing) section about how to install TLJH.
+  See the [](#install-installing) section about how to install TLJH.
 
--   **Upgrade Python manually.**
+- **Upgrade Python manually.**
 
-    Because upgrading Python for existing installs can break packages
-    already installed under the old Python, upgrading your current TLJH
-    installation, will NOT upgrade the Python version of the user
-    environment, but you may do so manually.
+  Because upgrading Python for existing installs can break packages
+  already installed under the old Python, upgrading your current TLJH
+  installation, will NOT upgrade the Python version of the user
+  environment, but you may do so manually.
 
-    **Steps:**
+  **Steps:**
 
-    1.  Activate the user environment, if using ssh. If the terminal was
-        started with JupyterHub, this step can be skipped:
+  1.  Activate the user environment, if using ssh. If the terminal was
+      started with JupyterHub, this step can be skipped:
 
-        ```bash
-        source /opt/tljh/user/bin/activate
-        ```
+      ```bash
+      source /opt/tljh/user/bin/activate
+      ```
 
-    2.  Get the list of currently installed pip packages (so you can
-        later install them under the new Python):
+  2.  Get the list of currently installed pip packages (so you can
+      later install them under the new Python):
 
-        ```bash
-        pip freeze > pip_pkgs.txt
-        ```
+      ```bash
+      pip freeze > pip_pkgs.txt
+      ```
 
-    3.  Update all conda installed packages in the environment:
+  3.  Update all conda installed packages in the environment:
 
-        ```bash
-        sudo PATH=${PATH} conda update --all
-        ```
+      ```bash
+      sudo PATH=${PATH} conda update --all
+      ```
 
-    4.  Update Python version:
+  4.  Update Python version:
 
-        ```bash
-        sudo PATH=${PATH} conda install python=3.7
-        ```
+      ```bash
+      sudo PATH=${PATH} conda install python=3.7
+      ```
 
-    5.  Install the pip packages previously saved:
+  5.  Install the pip packages previously saved:
 
-        ```bash
-        pip install -r pip_pkgs.txt
-        ```
+      ```bash
+      pip install -r pip_pkgs.txt
+      ```