From 93cb169e8c75db8b4cc178666e4f938e6533a4b1 Mon Sep 17 00:00:00 2001 From: Valentin Lorentz Date: Sun, 24 Apr 2022 10:57:58 +0200 Subject: [PATCH] architecture: Fix references --- develop/architecture.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/develop/architecture.rst b/develop/architecture.rst index 8ed18da..a786a65 100644 --- a/develop/architecture.rst +++ b/develop/architecture.rst @@ -59,10 +59,10 @@ Network drivers have a reference to a :class:`irclib.Irc` object, and do three things in their ``run()`` method: 1. check the connection is still alive (and schedule a reconnect if not) -2. get new messages from their :class:`irclib.Irc` instance (using - :meth:`irclib.Irc.takeMsg`) and send them to the network -3. get new messages from the network and pass them to their :class:`irclib.Irc` - (using :meth:`irclib.Irc.feedMsg`) +2. get new messages from their :class:`supybot.irclib.Irc` instance (using + :meth:`supybot.irclib.Irc.takeMsg`) and send them to the network +3. get new messages from the network and pass them to their :class:`supybot.irclib.Irc` + (using :meth:`supybot.irclib.Irc.feedMsg`) The actual implementation of the current ``Socket`` driver is actually a little more complex than this, as all ``Socket`` driver instances cooperate