doc: removed/renamed/fixed stale or incorrect references in documentation

rhornig · rhornig · commit 0d63dc669d47 · 2026-02-11T16:21:40.000+01:00
diff --git a/doc/src/developers-guide/ch-ipv4.rst b/doc/src/developers-guide/ch-ipv4.rst
@@ -198,8 +198,8 @@ a multicast address or not.
 When the datagram is decided to be sent up, it is processed as described
 in the previous subsection (Receiving packets). If it is decided to be
 sent out through some interface, it is actually sent to the :ned:`Arp`
-module through the ``queueOut`` gate. An :msg:`IPv4RoutingDecision`
-control info is attached to the outgoing packet, containing the outgoing
+module through the ``queueOut`` gate. An :msg:`NextHopAddressReq` and a :msg:`InterfaceReq`
+tag is attached to the outgoing packet, containing the outgoing
 interface id and the IP address of the next hop. The :ned:`Arp` module
 resolves the IP address to a hardware address if needed and forwards the
 datagram to the next hop.
@@ -418,8 +418,7 @@ calling :fun:`ICMPAccess::get()`.
 When an incoming ICMP error message is received, the :ned:`Icmp` module
 sends it out on the ``errorOut`` gate unchanged. It is assumed that
 an external module is connected to ``errOut`` that can process the
-error packet. There is a simple module (:ned:`ErrorHandling`) that
-simply logs the error and drops the message. Note that the :ned:`Ipv4`
+error packet.  Note that the :ned:`Ipv4`
 module does not send REDIRECT, DESTINATION_UNREACHABLE, TIME_EXCEEDED,
 and PARAMETER_PROBLEM messages to the :ned:`Icmp` module; it will send
 them to the transport layer module that sent the bogus packet
diff --git a/doc/src/developers-guide/ch-tags.rst b/doc/src/developers-guide/ch-tags.rst
@@ -188,7 +188,7 @@ service primitives; the other two are only present for completeness. The request
 service primitive is used when a higher layer protocol module (e.g., :ned:`Tcp`)
 wants to deliver a packet to a lower layer protocol module (e.g., :ned:`Ipv4`).
 Similarly, the :cpp:`SP_INDICATION` service primitive is used when a lower layer
-protocol module (e.g., :ned:`Ethernet`) wants to deliver a packet to a higher layer
+protocol module (e.g., Ethernet) wants to deliver a packet to a higher layer
 protocol module (e.g., :ned:`Ipv4`).
 
 Determining the Next Protocol
diff --git a/doc/src/developers-guide/ch-tcp.rst b/doc/src/developers-guide/ch-tcp.rst
@@ -177,8 +177,7 @@ messages they communicate with. Sometimes it is enough to simulate the
 amount of data transmitted (“200 MB”), and contents do not matter. In
 other scenarios, contents matter a lot. The messages can be represented
 as a stream of bytes, but sometimes it is easier for the applications to
-pass message objects to each other (e.g. HTTP request represented by a
-:msg:`HTTPRequest` message class).
+pass message objects to each other.
 
 The TCP modules in the INET framework support 3 data transfer modes:
 
diff --git a/doc/src/users-guide/ch-diffserv.rst b/doc/src/users-guide/ch-diffserv.rst
@@ -221,7 +221,7 @@ packet. It can be used to discard excess traffic, i.e. packets whose
 arrival rate exceeds the allowed maximum. In INET, the :ned:`Sink` module
 can be used as an absolute dropper.
 
-The algorithmic droppers in INET are :ned:`ThresholdDropper` and
+The algorithmic droppers in INET are :ned:`OrdinalBasedDropper` and
 :ned:`RedDropper`. These modules have multiple input and multiple output
 gates. Packets that arrive on gate :gate:`in[i]` are forwarded to gate
 :gate:`out[i]` (unless they are dropped). However, the queues attached to
@@ -230,23 +230,7 @@ of the dropping algorithm is the sum of the individual queue lengths.
 This way, we can emulate shared buffers of the queues. Note that it is
 also possible to connect each output to the same queue module.
 
-.. _ug:sec:diffserv:threshold-dropper:
-
-Threshold Dropper
-^^^^^^^^^^^^^^^^^
-
-The :ned:`ThresholdDropper` module selectively drops packets based on
-the available buffer space of the queues attached to its output. The
-buffer space can be specified as the count of packets or as the size in
-bytes.
-
-The module sums the buffer lengths of its outputs, and if enqueuing a
-packet would exceed the configured capacities, then the packet will be
-dropped instead.
-
-By attaching a :ned:`ThresholdDropper` to the input of a FIFO queue, you
-can compose a drop tail queue. Shared buffer space can be modeled by
-attaching more FIFO queues to the output.
+.. _ug:sec:diffserv:red-dropper:
 
 RED Dropper
 ^^^^^^^^^^^
diff --git a/showcases/measurement/relationships/doc/index.rst.todo b/showcases/measurement/relationships/doc/index.rst.todo
diff --git a/showcases/tsn/trafficshaping/htbshaper/doc/index.rst.todo b/showcases/tsn/trafficshaping/htbshaper/doc/index.rst.todo
diff --git a/showcases/tsn/trafficshaping/tokenbucketshaper/doc/index.rst.todo b/showcases/tsn/trafficshaping/tokenbucketshaper/doc/index.rst.todo
diff --git a/showcases/wireless/directionalantennas/doc/index.rst b/showcases/wireless/directionalantennas/doc/index.rst
@@ -86,8 +86,6 @@ By default, the cross-section plane is perpendicular to the current
 viewing angle (however, one can specify other
 planes in the antenna's local coordinate system).
 
-For a more in-depth overview of antenna lobe visualization, read the :ref:`corresponding section <ug:sec:visualization:radio-state>`
-in the INET User's Guide.
 For the description of all parameters of the visualizer, check the NED documentation
 of :ned:`RadioVisualizerBase`.
 
diff --git a/tutorials/ospf/omnetpp.ini b/tutorials/ospf/omnetpp.ini
@@ -762,3 +762,4 @@ extends = Step1
 *.R4.pcapRecorder[0].pcapNetwork = 1        # ethernet
 *.R4.pcapRecorder[0].pcapFile = "results/R4.eth0.pcap"
 
+# ---------------------------------------------------------------

Original file line number	Diff line number	Diff line change
`@@ -762,3 +762,4 @@ extends = Step1`
`762`	`762`	`*.R4.pcapRecorder[0].pcapNetwork = 1 # ethernet`
`763`	`763`	`*.R4.pcapRecorder[0].pcapFile = "results/R4.eth0.pcap"`
`764`	`764`
	`765`	`+# ---------------------------------------------------------------`