avoid infinite recursion for richtooltops, (hopefully) fixes #15070

[wxWidgets.git] / interface / wx / dialup.h

diff --git a/interface/wx/dialup.h b/interface/wx/dialup.h
index 1db8388a544a998276744ff67bbfd939ff6c6375..4bf33e33c850742bc2fbbe2ac9f31711222a7a8a 100644 (file)
--- a/interface/wx/dialup.h
+++ b/interface/wx/dialup.h
@@ -3,7 +3,7 @@
 // Purpose:     interface of wxDialUpManager
 // Author:      wxWidgets team
 // RCS-ID:      $Id$
-// Licence:     wxWindows license
+// Licence:     wxWindows licence
 /////////////////////////////////////////////////////////////////////////////
 
 /**
@@ -93,7 +93,7 @@ public:
 
     /**
         Enable automatic checks for the connection status and sending of
-        wxEVT_DIALUP_CONNECTED/wxEVT_DIALUP_DISCONNECTED events. The interval
+        @c wxEVT_DIALUP_CONNECTED/wxEVT_DIALUP_DISCONNECTED events. The interval
         parameter is only for Unix where we do the check manually and specifies
         how often should we repeat the check (each minute by default). Under
         Windows, the notification about the change of connection status is sent
@@ -119,7 +119,7 @@ public:
     virtual bool HangUp() = 0;
 
     /**
-        Returns @true if the computer has a permanent network connection (i.e.
+        Returns @true if the computer has a permanent network connection (i.e.\
         is on a LAN) and so there is no need to use Dial() function to go
         online.
 
@@ -207,7 +207,7 @@ public:
     bool IsConnectedEvent() const;
 
     /**
-        Does this event come from wxDialUpManager::Dial() or from some extrenal
+        Does this event come from wxDialUpManager::Dial() or from some external
         process (i.e. does it result from our own attempt to establish the
         connection)?
     */