diff --git a/Quick-guide:-popup-user-interface.md b/Quick-guide:-popup-user-interface.md
index 97bf17d..7337cd7 100644
--- a/Quick-guide:-popup-user-interface.md
+++ b/Quick-guide:-popup-user-interface.md
@@ -48,7 +48,7 @@ This shows the number of network requests uBlock blocked on the current page. Al
 
 Click the _eye-dropper_ icon to enter [element picker mode](https://github.com/gorhill/uBlock/wiki/Element-picker), which allows you to create a filter by interactively picking an element on a page, thus permanently removing it from the page.
 
-Click the _list_ icon to open the [network request logger](Quick-guide:-network-request-logger) in a separate tab. This allows you to inspect real-time network traffic within the browser.
+Click the _list_ icon to open the [network request logger](https://github.com/gorhill/uBlock/wiki/The-logger) in a separate tab. This allows you to inspect real-time network traffic within the browser.
 
 ***
 
@@ -161,4 +161,4 @@ Because of security and privacy concerns, many prefer to block all web fonts by
 
 This will block all web fonts everywhere by default, and in this case you can toggle off the switch to allow web fonts on a per-site basis.
 
-**Caveat for Chromium-based browsers:** Chromium's webRequest API [does not specifically report requests of type `font`](https://developer.chrome.com/extensions/webRequest#type-ResourceType), fonts are reported as type `other`. Whether a request is for a font resource is inferred by uBlock using the "extension" of the path part of a URL. However a URL can be anything really, regardless of request type, so for Chromium-based browsers, uBlock **may** have to block a font **after** the request is made, when the response headers are received from the remote server -- as the response headers allow to identify for sure the type of a resource.
+**Caveat for Chromium-based browsers:** Chromium's webRequest API [does not specifically report requests of type `font`](https://developer.chrome.com/extensions/webRequest#type-ResourceType), fonts are reported as type `other`. Whether a request is for a font resource is inferred by uBlock using the "extension" of the path part of a URL. However a URL can be anything really, regardless of request type, so for Chromium-based browsers, uBlock **may** have to block a font **after** the request is made, when the response headers are received from the remote server -- as the response headers allow to identify for sure the type of a resource.
\ No newline at end of file