no bug - fx doc - Fix some rst warnings

Depends on D90832

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

build/docs/glossary.rst

@@ -1,6 +1,5 @@
-========
-Glossary
-========
+Build Glossary
+==============
 
 .. glossary::
    :sorted:

docs/setup/configuring_build_options.rst

@@ -158,7 +158,7 @@ application to build. Firefox is the default.
 Choose one of the following options to add to your ``mozconfig`` file:
 
 Browser (Firefox)
-   .. code:: eval
+   .. code::
 
       ac_add_options --enable-application=browser
 
@@ -167,17 +167,17 @@ Browser (Firefox)
       **Note**: This is the default
 
 Mail (Thunderbird)
-   .. code:: eval
+   .. code::
 
       ac_add_options --enable-application=comm/mail
 
 Mozilla Suite (SeaMonkey)
-   .. code:: eval
+   .. code::
 
       ac_add_options --enable-application=suite
 
 Calendar (Lightning Extension, uses Thunderbird)
-   .. code:: eval
+   .. code::
 
       ac_add_options --enable-application=comm/mail
       ac_add_options --enable-calendar
@@ -347,7 +347,7 @@ applications in each object directory.
 
 For example:
 
-.. code:: eval
+.. code::
 
     ac_add_options --disable-optimize --enable-debug
     mk_add_options MOZ_OBJDIR=/mozilla/src/obj-@CONFIG_GUESS@
@@ -358,7 +358,7 @@ For example:
 If you want to build only one project using this ``mozconfig``, use the
 following command line:
 
-.. code:: eval
+.. code::
 
    MOZ_CURRENT_PROJECT=browser ./mach build
 
@@ -374,7 +374,7 @@ Thunderbird. You should first create three ``mozconfig`` files.
 
 ``mozconfig-common``:
 
-.. code:: eval
+.. code::
 
    # add common options here, such as making an optimized release build
    mk_add_options MOZ_MAKE_FLAGS="-j4"
@@ -382,7 +382,7 @@ Thunderbird. You should first create three ``mozconfig`` files.
 
 ``mozconfig-firefox``:
 
-.. code:: eval
+.. code::
 
    # include the common mozconfig
    . ./mozconfig-common
@@ -393,7 +393,7 @@ Thunderbird. You should first create three ``mozconfig`` files.
 
 ``mozconfig-thunderbird``:
 
-.. code:: eval
+.. code::
 
    # include the common mozconfig
    . ./mozconfig-common
@@ -404,14 +404,14 @@ Thunderbird. You should first create three ``mozconfig`` files.
 
 To build Firefox, run the following commands:
 
-.. code:: eval
+.. code::
 
    export MOZCONFIG=/path/to/mozilla/mozconfig-firefox
    ./mach build
 
 To build Thunderbird, run the following commands:
 
-.. code:: eval
+.. code::
 
    export MOZCONFIG=/path/to/mozilla/mozconfig-thunderbird
    ./mach build

intl/l10n/docs/glossary.rst

@@ -1,6 +1,5 @@
-========
-Glossary
-========
+L10N Glossary
+=============
 
 .. glossary::
     :sorted:

toolkit/components/extensions/docs/lifecycle.rst

@@ -38,7 +38,7 @@ Handling lifecycle events
 To be notified of update and uninstall events, an extension lists these
 events in the API manifest:
 
-.. code-block:: json
+.. code-block:: js
 
    "myapi": {
      "schema": "...",

toolkit/components/extensions/docs/manifest.rst

@@ -11,7 +11,7 @@ The first step when adding a new property is to extend the schema so
 that manifests containing the new property pass validation.
 This is done with the ``"$extend"`` property as follows:
 
-.. code-block:: json
+.. code-block:: js
 
    [
      "namespace": "manifest",
@@ -37,7 +37,7 @@ in the API manifest (e.g., ``ext-toolkit.json``).
 Note that this property is an array so an extension can implement
 multiple properties:
 
-.. code-block:: json
+.. code-block:: js
 
    "myapi": {
      "schema": "...",

toolkit/components/extensions/docs/schema.rst

@@ -79,7 +79,7 @@ Implementing a fixed Javascript property
 A static property is made available to extensions via Javascript
 entirely from the schema, using a fragment like this one:
 
-.. code-block:: json
+.. code-block:: js
 
    [
      "namespace": "myapi",