Fix: Use HTTPS in docs and correct formatting typo in troubleshooting guide (#2762)

Co-authored-by: Seth Troisi <[email protected]>

1 files changed, 2 insertions, 2 deletions

diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
index 0d54afde..3b7fd8f5 100644
--- a/docs/troubleshooting.md
+++ b/docs/troubleshooting.md
@@ -11,7 +11,7 @@ This guide provides solutions to common issues and debugging tips.
   - For Google Cloud accounts, you can work around this by setting
     `GOOGLE_CLOUD_PROJECT` to your project ID.
   - You can also grab an API key from [AI
-    Studio](http://aistudio.google.com/app/apikey), which also includes a
+    Studio](https://aistudio.google.com/app/apikey), which also includes a
     separate free tier.
 
 ## Frequently asked questions (FAQs)
@@ -52,7 +52,7 @@ This guide provides solutions to common issues and debugging tips.
 - **CLI is not interactive in "CI" environments**
   - **Issue:** The CLI does not enter interactive mode (no prompt appears) if an environment variable starting with `CI_` (e.g., `CI_TOKEN`) is set. This is because the `is-in-ci` package, used by the underlying UI framework, detects these variables and assumes a non-interactive CI environment.
   - **Cause:** The `is-in-ci` package checks for the presence of `CI`, `CONTINUOUS_INTEGRATION`, or any environment variable with a `CI_` prefix. When any of these are found, it signals that the environment is non-interactive, which prevents the CLI from starting in its interactive mode.
-  - **Solution:**: If the `CI_` prefixed variable is not needed for the CLI to function, you can temporarily unset it for the command. e.g., `env -u CI_TOKEN gemini`
+  - **Solution:** If the `CI_` prefixed variable is not needed for the CLI to function, you can temporarily unset it for the command. e.g., `env -u CI_TOKEN gemini`
 
 ## Debugging Tips