URL updates, naming conventions, remove extra spaces

Behind-the-scene-network-requests.md

@@ -1,10 +1,10 @@
 **Important notes:**
 
-When this documentation was created, the behind-the-scene network requests uBlock Origin was able to see and filter, originated from many places, such as those from other extensions or from various browser operations (ex.: real-time search suggestions).
+When this documentation was created, the behind-the-scene network requests uBlock Origin (uBO) was able to see and filter, originated from many places, such as those from other extensions or from various browser operations (ex.: real-time search suggestions).
 
 Since then things have changed: uBO no longer can see network requests from other extensions, and behind-the-scene network requests are now quite less frequent. Furthermore, the webRequest API now provides more context to event listeners, such that it is often possible to still filter properly even when it's not possible to know from which exact tab a network request originates. Such requests, not assigned to specific tab, but with known context, are categorized now as "Tabless".
 
-Because of this (and other reasons which will eventually come to light - the ["Who Left Open The Cookie Jar?"](https://github.com/ghacksuserjs/ghacks-user.js/issues/489) vulnerability), starting with uBO 1.15.20, the `behind-the-scene` scope will no longer be on the _Trusted sites_ list by default, meaning network requests from the behind-the-scene scope will be subject to filtering by default.
+Because of this (and other reasons which will eventually come to light - the ["Who Left Open The Cookie Jar?"](https://github.com/arkenfox/user.js/issues/489) vulnerability), starting with uBO 1.15.20, the `behind-the-scene` scope will no longer be on the _Trusted sites_ list by default, meaning network requests from the behind-the-scene scope will be subject to filtering by default.
 
 ***
 
@@ -12,7 +12,7 @@ Because of this (and other reasons which will eventually come to light - the ["W
 
 Warning: following text is out of date and in need of revision.
 
-_Behind-the-scene_ network requests are network requests which uBlock Origin cannot associate with a specific tab in your browser: these requests come from _somewhere_, but uBO is missing information to report exactly from where.
+_Behind-the-scene_ network requests are network requests which uBO cannot associate with a specific tab in your browser: these requests come from _somewhere_, but uBO is missing information to report exactly from where.
 
 All network requests without a specific origin are classified as _behind-the-scene_. Typically, all blockers will ignore and automatically allow behind-the-scene network requests.
 
@@ -20,8 +20,8 @@ For the Chromium browser, examples of _behind-the-scene_ network requests:
 
 - made by the browser to update extensions
 - made by the browser because of specific functionality, like the setting _"Use a prediction service to help complete searches and URLs typed in the address bar"_
-- made by web pages using [`navigator.sendBeacon()`](https://developer.mozilla.org/en-US/docs/Web/API/navigator.sendBeacon), [hyperlink auditing](http://www.wilderssecurity.com/threads/hyperlink-auditing-aka-a-ping-and-beacon-aka-navigator-sendbeacon.364904/), et al.
-- made by installed extensions for not-so-good or good reasons (uBlock makes _behind-the-scene_ requests to fetch the filter lists when they need to be updated)
+- made by web pages using [`navigator.sendBeacon()`](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/sendBeacon), [hyperlink auditing](https://www.wilderssecurity.com/threads/hyperlink-auditing-aka-a-ping-and-beacon-aka-navigator-sendbeacon.364904/), et al.
+- made by installed extensions for not-so-good or good reasons (uBO makes _behind-the-scene_ requests to fetch the filter lists when they need to be updated)
 
 ### How to inspect the behind-the-scene popup panel
 
@@ -33,7 +33,7 @@ For Chromium-based browsers, if you install uBO manually, you will have to repla
 
 ### How to inspect behind-the-scene network requests
 
-Starting with uBlock version 0.8.6.0, you can inspect _behind-the-scene_ network requests using the network request logger. Simply select the _"Behind the scene"_ entry in the drop down list.
+Starting with uBO version 0.8.6.0, you can inspect _behind-the-scene_ network requests using the network request logger. Simply select the _"Behind the scene"_ entry in the drop down list.
 
 ![c](https://cloud.githubusercontent.com/assets/585534/5888630/0691e7ee-a3d5-11e4-8510-ed0955f39deb.png)<br><sup>Various extensions installed to show that that these too make behind-the-scene requests</sup>
 
@@ -45,22 +45,22 @@ The ability to inspect behind-the-scene network requests is available to all use
 
 **Important:** The blocking of behind-the-scene network requests can cripple important functionality of your browser or installed extensions. **If you decide to block some behind-the-scene network requests, you are entirely responsible for the consequences.**
 
-The ability to filter _behind-the-scene_ network requests is only available when _"Advanced user"_ is enabled in the uBlock options.
+The ability to filter _behind-the-scene_ network requests is only available when _"Advanced user"_ is enabled in the uBO options.
 
-The _behind-the-scene_ virtual tab is on the _Trusted sites_ list by default.  No filtering will occur even after you enable _"Advanced user"_ mode.
+The _behind-the-scene_ virtual tab is on the _Trusted sites_ list by default. No filtering will occur even after you enable _"Advanced user"_ mode.
 
 To access the filtering settings for _behind-the-scene_ network requests, simply open the popup UI in the network request logger while the _"Behind the scene"_ entry is selected:
 
 ![Behind-the-scene popup](https://raw.githubusercontent.com/gorhill/uBlock/master/doc/img/behind-the-scene-popup.gif)<br><sup>The popup UI will be filled with the settings/data of whatever tab is being currently inspected in the request logger.</sup>
 
-The image above shows what happens when you navigate through Github: Github makes use of `navigator.sendBeacon()` to send data to Google Analytics, which results in the firing of _behind-the-scene_ requests in the Chromium browser.
+The image above shows what happens when you navigate through GitHub: GitHub makes use of `navigator.sendBeacon()` to send data to Google Analytics, which results in the firing of _behind-the-scene_ requests in the Chromium browser.
 
 **Important:** Filter behind-the-scene requests at your own risk. I will close without further comment any reported issue which is a direct consequence of blocking behind-the-scene network requests.
 
-Remember that if you block indiscriminately, you could cripple the ability of your browser to update parts of itself or update extensions as well as the ability of extensions to work properly.  This is why this is an advanced user feature.
- 
+Remember that if you block indiscriminately, you could cripple the ability of your browser to update parts of itself or update extensions as well as the ability of extensions to work properly. This is why this is an advanced user feature.
+
 To turn off the filtering of _behind-the-scene_ requests, allow the _"Behind the scene"_ scope or turn off _"Advanced user"_ mode.
 
-To allow the _behind-the-scene_ scope, add `behind-the-scene` as a trusted site directive in the _Trusted sites_ tab of the uBlock dashboard.
+To allow the _behind-the-scene_ scope, add `behind-the-scene` as a trusted site directive in the _Trusted sites_ tab of the uBO dashboard.
 
-If there are only very specific behind-the-scene network requests you would like to filter, a good approach to minimize potential problems is to use dynamic filtering: set a local rule for the `all` cell to _allow_ (green) (i.e. `behind-the-scene * * allow`). This will ensure nothing is blocked in the _behind-the-scene scope_, just as if uBlock is disabled for that scope. Then create _block_ rules for the specific hostnames for which you want to block all network requests, or `noop` if you want to subject those hostnames to static filtering only.
+If there are only very specific behind-the-scene network requests you would like to filter, a good approach to minimize potential problems is to use dynamic filtering: set a local rule for the `all` cell to _allow_ (green) (i.e. `behind-the-scene * * allow`). This will ensure nothing is blocked in the _behind-the-scene scope_, just as if uBO is disabled for that scope. Then create _block_ rules for the specific hostnames for which you want to block all network requests, or `noop` if you want to subject those hostnames to static filtering only.