[libbsd 13/22] libbsd.txt: Move network interface driver hints

[Sebastian Huber]

---
 CONTRIBUTING.rst | 14 ++++++++++++++
 libbsd.txt       | 11 -----------
 2 files changed, 14 insertions(+), 11 deletions(-)

diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst
index 1d45f0ef..1113136c 100644
--- a/CONTRIBUTING.rst
+++ b/CONTRIBUTING.rst
@@ -416,3 +416,17 @@ within interrupt context is not allowed, so the Board Support Package (BSP)
 should support the
 `Interrupt Manager <https://docs.rtems.org/branches/master/c-user/interrupt/directives.html#rtems-interrupt-server-handler-install>`_
 in general.
+
+Network Interface Drivers Hints
+===============================
+
+Link Up/Down Events
+-------------------
+
+You can notifiy the application space of link up/down events in your network
+interface driver via the
+``if_link_state_change(LINK_STATE_UP/LINK_STATE_DOWN)`` function.  The
+DHCPCD(8) client is a consumer of these events for example.  Make sure that the
+interface flag ``IFF_UP`` and the interface driver flag ``IFF_DRV_RUNNING`` is
+set in case the link is up, otherwise ``ether_output()`` will return the error
+status ``ENETDOWN``.
diff --git a/libbsd.txt b/libbsd.txt
index 384a2f6b..8987cfa3 100644
--- a/libbsd.txt
+++ b/libbsd.txt
@@ -7,17 +7,6 @@ RTEMS BSD Library Guide
 
 == Getting Started
 
-== Network Interface Drivers
-
-=== Link Up/Down Events
-
-You can notifiy the application space of link up/down events in your network
-interface driver via the if_link_state_change(LINK_STATE_UP/LINK_STATE_DOWN)
-function.  The DHCPCD(8) client is a consumer of these events for example.
-Make sure that the interface flag IFF_UP and the interface driver flag
-IFF_DRV_RUNNING is set in case the link is up, otherwise ether_output() will
-return the error status ENETDOWN.
-
 == Qemu
 
 Use the following script to set up a virtual network with three tap devices
-- 
2.35.3