Minor cleaning of code highlighting

* Most of text blocks are in fact output blocks
* On qubes-iso-building.rst, try to get something correct for console
  lines starting with a comment
* Fixing a wrong :menuselection: item.

Statistics:

    685 console
     79 text
     44 bash
     35 output
     16 yaml
      9 systemd
      9 c
      8 python
      4 ini
      4 doscon
      2 markdown
      2 desktop
      1 xorg.conf
      1 xml+jinja
      1 xml
      1 kconfig
      1 html
This commit is contained in:
parulin 2025-07-31 02:09:34 -04:00
parent 4212c5eda8
commit 6f4370f793
No known key found for this signature in database
GPG key ID: BC3830B42F4BF1F5
23 changed files with 61 additions and 49 deletions

View file

@ -175,7 +175,7 @@ Once the package is installed:
Examine the terminal output for warnings or errors. You may see the following warning:
.. code:: text
.. code:: output
WARNING: UEFI capsule updates not available or enabled

View file

@ -144,7 +144,7 @@ First, find out which USB bus the device is connected to (note that these steps
For example, I want to attach a broadband modem to the NetVM. In the output of ``lsusb`` it may be listed as something like:
.. code:: text
.. code:: output
Bus 003 Device 003: ID 413c:818d Dell Computer Corp.
@ -164,7 +164,7 @@ To find the right controller, follow the usb bus:
This should output something like:
.. code:: text
.. code:: output
../../../devices/pci-0/pci0000:00/0000:00:1a.0/usb3
@ -180,7 +180,7 @@ Now you see the path: the text between ``/pci0000:00/0000:`` and ``/usb3`` i.e.
It is possible that on some system configurations the readlink method produces output which is different from the example above, For example, you might see output like this:
.. code:: text
.. code:: output
../../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/usb1