From 8371609cf8bf1b96826527652e699a15e630d4ab Mon Sep 17 00:00:00 2001
From: "pre-commit-ci[bot]"
 <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Date: Thu, 3 Feb 2022 13:29:17 +0000
Subject: [PATCH] [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci
---
 docs/using/troubleshooting.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/using/troubleshooting.md b/docs/using/troubleshooting.md
index 63b990cc..77b4dcd2 100644
--- a/docs/using/troubleshooting.md
+++ b/docs/using/troubleshooting.md
@@ -106,7 +106,7 @@ The following sections cover a few of these scenarios and how to fix them.
    - `NB_IUD` and `NB_GID` should match the local user's UID and GID.
    - You must use `--user root` to ensure that the `UID` and `GID` are updated at runtime.
 
-   ```{admonition} Additional notes
+   ````{admonition} Additional notes
    - The caveat with this approach is that since these changes are applied at runtime, you will need to re-run the same command
      with the appropriate flags and environment variables if you need to recreate the container (i.e. after removing/destroying it).
    - If you pass a numeric UID, it must be in the range of 0-2147483647
@@ -114,7 +114,7 @@ The following sections cover a few of these scenarios and how to fix them.
      ```bash
      $ id
      uid=1234(jovyan) gid=1234(jovyan) groups=1234(jovyan),100(users)
-     ```
+   ````
 
 ## Permission issues after changing the UID/GIU and USER in the container