update for feedback

Author: sungchun12

docs/guides/vscode.md

@@ -155,12 +155,11 @@ The VSCode extension is based on a [language server](https://en.wikipedia.org/wi
 
 If you have environment variables that are needed by the context and the language server, you can use one of these approaches to pass variables to the language server:
 
-- Open VSCode from a terminal that has the variables set (e.g. `.zshrc` or `.bashrc`). This will automatically be picked up by the language server only if you have `export ENV_VAR=value` in your shell configuration file when initializing the terminal.
-- Use environment variables pulled from somewhere else dynamically (e.g. a `.env` file) in your root project directory. This will automatically be picked up by the language server.
+- Open VSCode from a terminal that has the variables set already. 
+  - If you have `export ENV_VAR=value` in your shell configuration file (e.g. `.zshrc` or `.bashrc`) when initializing the terminal by default, the variables will be picked up by the language server if opened from that terminal.
+- Use environment variables pulled from somewhere else dynamically (e.g. a `.env` file) in your root project directory. This will automatically be picked up by the language server through the python environment that the extension uses.
 - Set the environment variables in the python environment that the extension uses. You can find detailed instructions [here](https://code.visualstudio.com/docs/python/environments#_environment-variables)
 
-#### Troubleshooting Environment Variables
-
 You can verify that the environment variables are being passed to the language server by printing them in your terminal. 
 
 1. `Cmd +Shift + P` (`Ctrl + Shift + P` in case of Windows) to start the VSCode command bar
@@ -180,7 +179,7 @@ If you change your environment variables in the terminal during development(e.g.
 
 3. Print the environment variables based on the instructions above to verify the changes have taken effect.
 
-### Python environment troubleshooting
+### Python environment issues
 
 The most common problem is the extension not using the correct Python interpreter.