F5/unison
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc, wifi: Fix rendering of RST code blocks

Browse Source
This commit is contained in:
Eduardo Almeida
2024-02-09 16:55:04 +00:00
parent 1aeb2a53e7
commit 2d04193b54
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/tutorial/source/tracing.rst
View File

@@ -589,7 +589,7 @@ One of the predefined namespaces in the config system is "NodeList"
which is a list of all of the nodes in the simulation. Items in the
list are referred to by indices into the list, so "/NodeList/7" refers
to the eighth Node in the list of nodes created during the simulation
(recall indices start at `0'). This reference is actually a
(recall indices start at '0'). This reference is actually a
``Ptr<Node>`` and so is a subclass of an ``ns3::Object``.
As described in the Object Model section of the |ns3| Manual, we make

2
src/wifi/doc/source/wifi-design.rst
View File

@@ -1516,7 +1516,7 @@ Depending on your goal, the common tasks are (in no particular order):
``frame-exchange-manager.*`` or its subclasses to accomplish this.
Handling of control frames is performed in ``FrameExchangeManager::ReceiveMpdu``.
* MAC high modification. For example, handling new management frames (think beacon/probe),
beacon/probe generation. Users usually make changes to ``wifi-mac.*``,``sta-wifi-mac.*``, ``ap-wifi-mac.*``, or ``adhoc-wifi-mac.*`` to accomplish this.
beacon/probe generation. Users usually make changes to ``wifi-mac.*``, ``sta-wifi-mac.*``, ``ap-wifi-mac.*``, or ``adhoc-wifi-mac.*`` to accomplish this.
* Wi-Fi queue management. The files ``txop.*`` and ``qos-txop.*`` are of interest for this task.
* Channel access management. Users should modify the files ``channel-access-manager.*``, which grant access to
``Txop`` and ``QosTxop``.