doc: various fixes to eliminate sphinx warnings

Author: adamgeorge309

doc/src/developers-guide/ch-mobility.rst

@@ -33,7 +33,7 @@ component has to prevent the node from exiting. It can call the
 torus, random placement, and error.
 
 MovingMobilityBase class
-~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~
 
 The abstract :cpp:`MovingMobilityBase` class can be used to model mobilities
 when the node moves on a continuous trajectory and updates its position

doc/src/developers-guide/ch-tags.rst

@@ -76,7 +76,7 @@ enqueued/dequeued, encapsulated/decapsulated, cloned, buffered, or stored for la
 the tags remain unchanged.
 
 Specifying the Protocol of a Packet
-----------------------------------
+-----------------------------------
 
 The most important packet tag is the :cpp:`PacketProtocolTag`. It specifies the
 outermost protocol of the packet. This tag should always be present because the
@@ -101,7 +101,7 @@ the packet protocol tag can only specify the inner protocol that is being encaps
 into an Ethernet MAC frame.
 
 Dispatching Packets to Protocol Modules
---------------------------------------
+---------------------------------------
 
 Inside a network node, protocol modules interact with one another by sending
 :cpp:`Packet` or :cpp:`Message` objects. INET provides great flexibility in terms

doc/src/users-guide/ch-apps.rst

@@ -387,7 +387,7 @@ this can be zero (zero is not allowed for :par:`sendInterval`). The zero
 :par:`burstDuration` is interpreted as infinity.
 
 Operation as a sink
-^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^
 
 When the :par:`destAddresses` parameter is empty, the module receives
 packets and makes statistics only.

showcases/emulation/babel/doc/index.rst

@@ -175,7 +175,7 @@ This can be worked around with ``nsenter``, as will be shown later. Here is the
    :end-at: unshare-
 
 The :ned:`ExternalEnvironment` module deals with preparing the host OS environment
-for running the emulation, then cleaning up afterwards. Specifically, the module's :par:`setupCommand` is executed at module creation, and :ned:`teardownCommand` at module destruction.
+for running the emulation, then cleaning up afterwards. Specifically, the module's :par:`setupCommand` is executed at module creation, and :par:`teardownCommand` at module destruction.
 We use these parameters to create and destroy network namespaces and virtual network interfaces in the host OS for each network node.
 We include an :ned:`ExternalEnvironment` module in hosts by setting the :par:`hasEnvironment` parameter to ``true``:
 

showcases/emulation/voip/doc/index.rst

@@ -154,7 +154,7 @@ This section presents various configurations for running the VoIP simulation.
 It includes a setup for running the experiment over a real network, and
 various configurations for running it in a virtual network on the local computer.
 
-.. note:: A different showcase (:doc:`mininet`) is dedicated to showing the use of
+.. note:: A different showcase (:doc:`/showcases/emulation/mininet/doc/index`) is dedicated to showing the use of
    Mininet for setting up the virtual network.
 
 Over a Real Network

showcases/general/pcaprecording/doc/index.rst

@@ -161,7 +161,7 @@ PCAP recorder modules, because ``router1`` has two interfaces.
 .. literalinclude:: ../omnetpp.ini
    :language: ini
    :start-at: router1.numPcapRecorders
-   :end-before: moduleNamePatterns = "eth[*]
+   :end-at: moduleNamePatterns = "eth[0]
 
 In ``router2``, we'll record only packets carrying TCP data on the ``eth0``
 interface. ``router2`` has two interfaces, so the :par:`moduleNamePatters`

showcases/index.rst

@@ -18,7 +18,7 @@ the simulations (NED, ini, and other files) and the web pages are in the
 
 Latest changes:
 
-- :doc:`emulation/voip/doc/mininet` added (2024-02-26)
+- :doc:`emulation/mininet/doc/index` added (2024-02-26)
 - :doc:`tsn/trafficshaping/underthehood/doc/index` updated (2023-07-28)
 - :doc:`tsn/trafficshaping/cbsandtas/doc/index` released (2023-07-28)
 - :doc:`tsn/trafficshaping/cbsandats/doc/index` updated (2023-07-28)

showcases/visualizer/canvas/spectrum/doc/index.rst

@@ -121,8 +121,8 @@ shape in frequency (the spectral mask in the 802.11 standard):
    :align: center
 
 .. literalinclude:: ../omnetpp.ini
-   :start-at: radio.typename
-   :end-at: transmitter.frequencyGains
+   :start-at: radio.signalAnalogRepresentation
+   :end-at: transmitter.analogModel.frequencyGains
    :language: ini
 
 .. note:: We're using linear interpolation instead of log-linear when defining the signal

showcases/visualizer/canvas/transportpathactivity/doc/index.rst

@@ -67,8 +67,8 @@ In this simulation, the ``pathVisualizer's`` type is
 :par:`displayRoutes` parameter to true.
 
 .. literalinclude:: ../omnetpp.ini
-   :start-at: pathVisualizer.*.displayRoutes
-   :end-at: pathVisualizer.*.displayRoutes
+   :start-at: pathVisualizer.displayRoutes
+   :end-at: pathVisualizer.displayRoutes
    :language: ini
 
 The following video shows what happens when the simulation is run.
@@ -146,8 +146,8 @@ does not fade out completely before the next ``UDPBasicAppData`` packet
 arrives.
 
 .. literalinclude:: ../omnetpp.ini
-   :start-at: TransportRouteCanvasVisualizer.displayRoutes
-   :end-at: TransportRouteCanvasVisualizer.packetFilter
+   :start-at: transportRouteVisualizer.displayRoutes
+   :end-at: transportRouteVisualizer.packetFilter
    :language: ini
 
 The following video has been captured from the simulation and shows