From 6333fb500685479359dbda54c4a43f9b847f36c2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Micha=C5=82=20Krassowski?=
 <5832902+krassowski@users.noreply.github.com>
Date: Fri, 6 Sep 2024 20:42:38 +0100
Subject: [PATCH] Clarify that `.bash_profile` does work in terminals in
 JupyterLab (#516)

---
 docs/docs/faq.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docs/faq.md b/docs/docs/faq.md
index 834b1596..9f5cfba6 100644
--- a/docs/docs/faq.md
+++ b/docs/docs/faq.md
@@ -26,7 +26,7 @@ It's important to note that packages installed this way aren't available to the
 Nebari automatically creates and manages `.bashrc` and `.profile`. Therefore, end users do not have write permissions to modify this file. However, by default Nebari _will_ source `.bash_profile`. Users may use this file to populate environment variables or set up alias, etc. However, there are some important things to note:
 
 - The `.bash_profile` is sourced _after_ the `.bashrc` - be aware of the implications, one of which is that you will lose changes to the prompt syntax. To avoid this, you can always source the `.bashrc` inside the .`bash_profile`.
-- JupyterLab does _not_ source `.bash_profile`.
+- JupyterLab kernels do _not_ source `.bash_profile` but the Jupyter terminal does.
 - The VS Code terminal does _not_ source `.bash_profile` by default.
 
 ## What if I can't see the active conda environment in the terminal?