Some URL fixes

[senf.git] / senf / PPI / Mainpage.dox

diff --git a/senf/PPI/Mainpage.dox b/senf/PPI/Mainpage.dox
index 1675621..dca7b8c 100644 (file)
--- a/senf/PPI/Mainpage.dox
+++ b/senf/PPI/Mainpage.dox
@@ -64,10 +64,10 @@
 
     \section ppi_packets Packets
 
-    The PPI processes packets and uses the <a href="@TOPDIR@/Packets/doc/html/index.html">Packet
-    library</a> to handle them. All packets are internally passed around as generic \ref
-    senf::Packet references, however connectors may optionally be defined as sending or receiving
-    packets of a specific type only.
+    The PPI processes packets and uses the <a
+    href="@TOPDIR@/senf/Packets/doc/html/index.html">Packet library</a> to handle them. All packets
+    are internally passed around as generic \ref senf::Packet references, however connectors may
+    optionally be defined as sending or receiving packets of a specific type only.
 
     \section ppi_modules Modules
 
@@ -216,10 +216,10 @@
     It is possible to connect two active or passive connectors with each other using a special
     adaptor module (senf::ppi::module::PassiveQueue or senf::ppi::module::ActiveFeeder
     respectively).
-    
+
     Additionally, the connectors must be type-compatible: Either one (or both) of the connectors
     must be untyped (they accept arbitrary senf::Packet's, the optional tempalte argument is empty),
-    or they both accept the same type of packet. This check is performed at runtime. 
+    or they both accept the same type of packet. This check is performed at runtime.
 
     To complete our simplified example: Lets connect senf::ppi::module::ActiveSocketReader and
     senf::ppi::module::PassiveSocketWriter to our example module:
@@ -324,7 +324,7 @@
 
     The PPI really is not concerned, how the events are called and what information is needed to
     perform the call. This is handled by the <a
-    href="@TOPDIR@/Scheduler/doc/html/index.html">Scheduler</a>, which is wrapped by the event
+    href="@TOPDIR@/senf/Scheduler/doc/html/index.html">Scheduler</a>, which is wrapped by the event
     classes.
 
     All events are derived from senf::ppi::EventDescriptor. The base class allows to enable and