diff --git a/blog/2024-11-14-devcon.md b/blog/2024-11-14-devcon.md
index e40426a..a3559df 100644
--- a/blog/2024-11-14-devcon.md
+++ b/blog/2024-11-14-devcon.md
@@ -202,7 +202,6 @@ Try either the Twitter or Discord plugin and follow the steps in UI. If everythi
 #### Extra items (optional)
 
 - [ ] Instead of using a plugin, try to manually notarize a page as documented on https://docs.tlsnotary.org/quick_start/browser_extension.html
-- [ ] Instead of using the plugin's presentation preview tool, download the presentation (called proof in the UI) and render it with https://explorer.tlsnotary.org instead.
 
 ## Notarize in teams
 
diff --git a/docs/faq.md b/docs/faq.md
index 234f751..f4e6e3c 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -38,7 +38,7 @@ Yes, but for public data, a less-resource-intensive man-in-the-middle approach i
 
 ### How can I inspect and verify a TLSNotary proof?
 
-The easiest way is to use the proof-of-concept [TLSNotary Explorer](https://explorer.tlsnotary.org).
+The easiest way is to use the browser extension.
 
 ### Which TLS versions are supported?
 
diff --git a/docs/quick_start/browser_extension.md b/docs/quick_start/browser_extension.md
index a2e55df..575082d 100644
--- a/docs/quick_start/browser_extension.md
+++ b/docs/quick_start/browser_extension.md
@@ -106,9 +106,6 @@ When the notarization is ready, you can click the **View** button. If you closed
   <img width="477" src="./images/extension_history_new.png" />
   ![](./images/extension_history_new.png)
 
-<!-- TODO -->
-<!-- You also have the option to download the proof. You can view this proof later by using the **Verify** button or via <https://explorer.tlsnotary.org/>. You can get the Notary public key by visiting the Notary API specified [above](#notary-server). -->
-
 
 ## Write your own Extension Plugins