From ef2075ccbe2db0e436f22b9e60d4e46f2e052cb9 Mon Sep 17 00:00:00 2001
From: Hendrik Eeckhaut <hendrik@eeckhaut.org>
Date: Mon, 11 Nov 2024 14:55:19 +0700
Subject: [PATCH] doc: FAQ logging in browser extension (#105)

---
 src/faq.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/faq.md b/src/faq.md
index 4ce54b5..ca20f9d 100644
--- a/src/faq.md
+++ b/src/faq.md
@@ -80,6 +80,8 @@ To get deeper insights into what TLSNotary is doing, you can enable extra loggin
 RUST_LOG=trace,yamux=info,uid_mux=info cargo run  --release
 ```
 
+In the Browser Extension you change the logging level via **Options > Advanced > Logging Level**
+
 ### How do I troubleshoot connection issues? { #faq11 }
 
 If a TLSNotary request fails, first ensure that the request works independently of TLSNotary by testing it with tools like `curl`, Postman, or another HTTP client. This helps rule out any server or network issues unrelated to TLSNotary.