Bug 1845804 - Put WebExtensions under Gecko in the overview r=mossop,perftest-reviewers,devtools-reviewers,afinder

... and rename "web extensions" to "WebExtensions".

Differential Revision: https://phabricator.services.mozilla.com/D184765

browser/docs/overview.rst

@@ -86,13 +86,6 @@ The Firefox Profiler is the way to measure the performance of your code. Go to
 performance profile. These profiles can be uploaded and shared. It can identify slow parts of the
 code, and reveal the underlying behavior of how code runs.
 
-Web Extensions
---------------
-
-The Web Extensions APIs allow extensions to interact with the rest of the browser.
-
-:ref:`Read more <WebExtensions API Development>`
-
 Installer
 ---------
 

devtools/docs/user/about_colon_debugging/index.rst

@@ -136,7 +136,7 @@ Extensions
 Loading a temporary extension
 -----------------------------
 
-With the **Load Temporary Add-on** button you can temporarily load a web extension from a directory on disk. Click the button, navigate to the directory containing the add-on and select its manifest file. The temporary extension is then displayed under the **Temporary Extensions** header.
+With the **Load Temporary Add-on** button you can temporarily load a WebExtension from a directory on disk. Click the button, navigate to the directory containing the add-on and select its manifest file. The temporary extension is then displayed under the **Temporary Extensions** header.
 
 You don't have to package or sign the extension before loading it, and it stays installed until you restart Firefox.
 
@@ -211,7 +211,7 @@ Just as it does with temporarily loaded extensions, the link next to **Manifest
   It's recommended that you use the Browser Toolbox, not the Add-on Debugger, for debugging WebExtensions. See `Debugging WebExtensions <https://extensionworkshop.com/documentation/develop/debugging/>`_ for all the details.
 
 
-The Add-ons section in about:debugging lists all web extensions that are currently installed. Next to each entry is a button labeled **Inspect**.
+The Add-ons section in about:debugging lists all WebExtensions that are currently installed. Next to each entry is a button labeled **Inspect**.
 
 .. note::
 

devtools/docs/user/debugger/source_map_errors/index.rst

@@ -69,7 +69,7 @@ In this case, the error will also be displayed in the source tab in the debugger
 NetworkError when attempting to fetch resource
 **********************************************
 
-A bug in Firefox prevents it from loading source maps for web extensions.
+A bug in Firefox prevents it from loading source maps for WebExtensions.
 
 See `Bug 1437937: WebExtensions Doesn't Find Source Maps <https://bugzilla.mozilla.org/show_bug.cgi?id=1437937>`_ for details.
 

devtools/docs/user/debugger/ui_tour/index.rst

@@ -34,7 +34,7 @@ The source list pane lists all the JavaScript source files loaded into the page
 
 You can :ref:`search for a file <debugger-how-to-search-searching-for-files>` using :kbd:`Ctrl` + :kbd:`P` (:kbd:`Cmd` + :kbd:`P` on a Mac).
 
-Web Extensions are listed in the Source List pane using the extension's name.
+WebExtensions are listed in the Source List pane using the extension's name.
 
 .. image:: source_list_pane.png
   :class: border

devtools/docs/user/deprecated_tools/index.rst

@@ -125,7 +125,7 @@ More details about the :doc:`Web Audio Editor <../web_audio_editor/index>`
 Alternatives
 ------------
 
-Alternatives include `AudioN <https://github.com/google/audion>`_ and https://github.com/spite/WebAudioExtension web extensions.
+Alternatives include the `AudioN <https://github.com/google/audion>`_ and https://github.com/spite/WebAudioExtension WebExtensions.
 
 
 Shader editor

docs/overview/gecko.rst

@@ -285,3 +285,10 @@ Details about :ref:`automated tests may be found here <Automated Testing>`. The
 tests are :ref:`XPCShell <XPCShell tests>` for testing backend components,
 :ref:`Browser Chrome Tests <Browser chrome mochitests>` for testing the frontend UI and
 :ref:`Web Platform Tests <web-platform-tests>` for testing web APIs.
+
+WebExtensions
+--------------
+
+The WebExtensions APIs allow extensions to interact with the rest of the browser.
+
+:ref:`Read more <WebExtensions API Development>`

intl/docs/locale.rst

@@ -323,7 +323,7 @@ Available Locales
 =================
 
 In Gecko, available locales come from the `Packaged Locales` and the installed
-`language packs`. Language packs are a variant of web extensions providing just
+`language packs`. Language packs are a variant of WebExtensions providing just
 localized resources for one or more languages.
 
 The primary notion of which locales are available is based on which locales Gecko has

testing/perfdocs/generated/talos.rst

@@ -168,7 +168,7 @@ There are two different species of Talos tests:
 In addition we have some variations on existing tests:
 
 -  Heavy_: Run tests with the heavy user profile instead of a blank one
--  `Web extension`_: Run tests with a web extension to see the perf impact extension have
+-  WebExtension_: Run tests with a WebExtension to see the perf impact extension have
 -  `Real-world WebExtensions`_: Run tests with a set of 5 popular real-world WebExtensions installed and enabled.
 
 Some tests measure different things:
@@ -251,14 +251,14 @@ Currently we have issues with this on windows (takes too long to unpack
 the files from the profile), so we have turned this off there. Our goal
 is to run this on basic pageload and startup tests.
 
-Web extension
+WebExtension
 =============
 
-Web Extensions are what Firefox has switched to and there are different
+WebExtensions are what Firefox has switched to and there are different
 code paths and APIs used vs addons. Historically we don't test with
 addons (other than our test addons) and are missing out on common
 slowdowns. In 2017 we started running some startup and basic pageload
-tests with a web extension in the profile (`bug
+tests with a WebExtension in the profile (`bug
 1398974 <https://bugzilla.mozilla.org/show_bug.cgi?id=1398974>`__). We
 have updated the Extension to be more real world and will continue to do
 that.

testing/talos/perfdocs/index.rst

@@ -168,7 +168,7 @@ There are two different species of Talos tests:
 In addition we have some variations on existing tests:
 
 -  Heavy_: Run tests with the heavy user profile instead of a blank one
--  `Web extension`_: Run tests with a web extension to see the perf impact extension have
+-  WebExtension_: Run tests with a WebExtension to see the perf impact extension have
 -  `Real-world WebExtensions`_: Run tests with a set of 5 popular real-world WebExtensions installed and enabled.
 
 Some tests measure different things:
@@ -251,14 +251,14 @@ Currently we have issues with this on windows (takes too long to unpack
 the files from the profile), so we have turned this off there. Our goal
 is to run this on basic pageload and startup tests.
 
-Web extension
+WebExtension
 =============
 
-Web Extensions are what Firefox has switched to and there are different
+WebExtensions are what Firefox has switched to and there are different
 code paths and APIs used vs addons. Historically we don't test with
 addons (other than our test addons) and are missing out on common
 slowdowns. In 2017 we started running some startup and basic pageload
-tests with a web extension in the profile (`bug
+tests with a WebExtension in the profile (`bug
 1398974 <https://bugzilla.mozilla.org/show_bug.cgi?id=1398974>`__). We
 have updated the Extension to be more real world and will continue to do
 that.