Fix doxygen references to EAP server/peer module

diff --git a/doc/code_structure.doxygen b/doc/code_structure.doxygen
index 6398ff3..96f6160 100644 (file)
--- a/doc/code_structure.doxygen
+++ b/doc/code_structure.doxygen
@@ -243,7 +243,7 @@ wpa_i.h
 
 \section eap_peer EAP peer
 
-\ref eap_module "EAP peer implementation" is a separate module that
+\ref eap_peer_module "EAP peer implementation" is a separate module that
 can be used by other programs than just %wpa_supplicant.
 
 eap.c and eap.h

diff --git a/doc/mainpage.doxygen b/doc/mainpage.doxygen
index 9b6e3db..690b7d6 100644 (file)
--- a/doc/mainpage.doxygen
+++ b/doc/mainpage.doxygen
@@ -39,7 +39,7 @@ to different target boards and operating systems is available on
 the \ref porting "porting page".
 
 EAPOL (IEEE 802.1X) state machines are implemented as a separate
-module that interacts with \ref eap_module "EAP peer implementation".
+module that interacts with \ref eap_peer_module "EAP peer implementation".
 In addition to programs aimed at normal production use,
 %wpa_supplicant source tree includes number of \ref testing_tools
 "testing and development tools" that make it easier to test the
@@ -77,7 +77,7 @@ to different target boards and operating systems is available on
 the \ref porting "porting page".
 
 EAPOL (IEEE 802.1X) state machines are implemented as a separate
-module that interacts with \ref eap_module "EAP server implementation".
+module that interacts with \ref eap_server_module "EAP server implementation".
 Similarly, RADIUS authentication server is in its own separate module.
 Both IEEE 802.1X and RADIUS authentication server can use EAP server
 functionality.