diff --git a/examples/adhoc_provider.py b/examples/adhoc_provider.py index cfe7275..a72158c 100755 --- a/examples/adhoc_provider.py +++ b/examples/adhoc_provider.py @@ -40,7 +40,7 @@ class CommandBot(sleekxmpp.ClientXMPP): # The session_start event will be triggered when # the bot establishes its connection with the server # and the XML streams are ready for use. We want to - # listen for this event so that we we can intialize + # listen for this event so that we we can initialize # our roster. self.add_event_handler("session_start", self.start) @@ -49,7 +49,7 @@ class CommandBot(sleekxmpp.ClientXMPP): Process the session_start event. Typical actions for the session_start event are - requesting the roster and broadcasting an intial + requesting the roster and broadcasting an initial presence stanza. Arguments: @@ -71,7 +71,7 @@ class CommandBot(sleekxmpp.ClientXMPP): def _handle_command(self, iq, session): """ - Respond to the intial request for a command. + Respond to the initial request for a command. Arguments: iq -- The iq stanza containing the command request. diff --git a/examples/adhoc_user.py b/examples/adhoc_user.py index c155d4b..bbd42d8 100755 --- a/examples/adhoc_user.py +++ b/examples/adhoc_user.py @@ -43,7 +43,7 @@ class CommandUserBot(sleekxmpp.ClientXMPP): # The session_start event will be triggered when # the bot establishes its connection with the server # and the XML streams are ready for use. We want to - # listen for this event so that we we can intialize + # listen for this event so that we we can initialize # our roster. self.add_event_handler("session_start", self.start) self.add_event_handler("message", self.message) @@ -53,7 +53,7 @@ class CommandUserBot(sleekxmpp.ClientXMPP): Process the session_start event. Typical actions for the session_start event are - requesting the roster and broadcasting an intial + requesting the roster and broadcasting an initial presence stanza. Arguments: diff --git a/examples/disco_browser.py b/examples/disco_browser.py index 20d012b..0d282d7 100755 --- a/examples/disco_browser.py +++ b/examples/disco_browser.py @@ -60,7 +60,7 @@ class Disco(sleekxmpp.ClientXMPP): # The session_start event will be triggered when # the bot establishes its connection with the server # and the XML streams are ready for use. We want to - # listen for this event so that we we can intialize + # listen for this event so that we we can initialize # our roster. self.add_event_handler("session_start", self.start) @@ -69,7 +69,7 @@ class Disco(sleekxmpp.ClientXMPP): Process the session_start event. Typical actions for the session_start event are - requesting the roster and broadcasting an intial + requesting the roster and broadcasting an initial presence stanza. In this case, we send disco#info and disco#items diff --git a/examples/echo_client.py b/examples/echo_client.py index db0064f..7e553c4 100755 --- a/examples/echo_client.py +++ b/examples/echo_client.py @@ -40,7 +40,7 @@ class EchoBot(sleekxmpp.ClientXMPP): # The session_start event will be triggered when # the bot establishes its connection with the server # and the XML streams are ready for use. We want to - # listen for this event so that we we can intialize + # listen for this event so that we we can initialize # our roster. self.add_event_handler("session_start", self.start) @@ -54,7 +54,7 @@ class EchoBot(sleekxmpp.ClientXMPP): Process the session_start event. Typical actions for the session_start event are - requesting the roster and broadcasting an intial + requesting the roster and broadcasting an initial presence stanza. Arguments: diff --git a/examples/muc.py b/examples/muc.py index 7586c61..8fe2eb4 100755 --- a/examples/muc.py +++ b/examples/muc.py @@ -44,7 +44,7 @@ class MUCBot(sleekxmpp.ClientXMPP): # The session_start event will be triggered when # the bot establishes its connection with the server # and the XML streams are ready for use. We want to - # listen for this event so that we we can intialize + # listen for this event so that we we can initialize # our roster. self.add_event_handler("session_start", self.start) @@ -68,7 +68,7 @@ class MUCBot(sleekxmpp.ClientXMPP): Process the session_start event. Typical actions for the session_start event are - requesting the roster and broadcasting an intial + requesting the roster and broadcasting an initial presence stanza. Arguments: diff --git a/examples/ping.py b/examples/ping.py index 8630b32..258fd76 100755 --- a/examples/ping.py +++ b/examples/ping.py @@ -43,7 +43,7 @@ class PingTest(sleekxmpp.ClientXMPP): # The session_start event will be triggered when # the bot establishes its connection with the server # and the XML streams are ready for use. We want to - # listen for this event so that we we can intialize + # listen for this event so that we we can initialize # our roster. self.add_event_handler("session_start", self.start) @@ -52,7 +52,7 @@ class PingTest(sleekxmpp.ClientXMPP): Process the session_start event. Typical actions for the session_start event are - requesting the roster and broadcasting an intial + requesting the roster and broadcasting an initial presence stanza. Arguments: diff --git a/examples/proxy_echo_client.py b/examples/proxy_echo_client.py index 6655ec5..25bfc89 100755 --- a/examples/proxy_echo_client.py +++ b/examples/proxy_echo_client.py @@ -40,7 +40,7 @@ class EchoBot(sleekxmpp.ClientXMPP): # The session_start event will be triggered when # the bot establishes its connection with the server # and the XML streams are ready for use. We want to - # listen for this event so that we we can intialize + # listen for this event so that we we can initialize # our roster. self.add_event_handler("session_start", self.start) @@ -54,7 +54,7 @@ class EchoBot(sleekxmpp.ClientXMPP): Process the session_start event. Typical actions for the session_start event are - requesting the roster and broadcasting an intial + requesting the roster and broadcasting an initial presence stanza. Arguments: diff --git a/examples/roster_browser.py b/examples/roster_browser.py index 7e7ec81..b366d00 100644 --- a/examples/roster_browser.py +++ b/examples/roster_browser.py @@ -42,7 +42,7 @@ class RosterBrowser(sleekxmpp.ClientXMPP): # The session_start event will be triggered when # the bot establishes its connection with the server # and the XML streams are ready for use. We want to - # listen for this event so that we we can intialize + # listen for this event so that we we can initialize # our roster. We need threaded=True so that the # session_start handler doesn't block event processing # while we wait for presence stanzas to arrive. @@ -57,7 +57,7 @@ class RosterBrowser(sleekxmpp.ClientXMPP): Process the session_start event. Typical actions for the session_start event are - requesting the roster and broadcasting an intial + requesting the roster and broadcasting an initial presence stanza. Arguments: diff --git a/examples/send_client.py b/examples/send_client.py index adf5fcc..caf4768 100755 --- a/examples/send_client.py +++ b/examples/send_client.py @@ -45,7 +45,7 @@ class SendMsgBot(sleekxmpp.ClientXMPP): # The session_start event will be triggered when # the bot establishes its connection with the server # and the XML streams are ready for use. We want to - # listen for this event so that we we can intialize + # listen for this event so that we we can initialize # our roster. self.add_event_handler("session_start", self.start) @@ -54,7 +54,7 @@ class SendMsgBot(sleekxmpp.ClientXMPP): Process the session_start event. Typical actions for the session_start event are - requesting the roster and broadcasting an intial + requesting the roster and broadcasting an initial presence stanza. Arguments: diff --git a/sleekxmpp/plugins/xep_0050/adhoc.py b/sleekxmpp/plugins/xep_0050/adhoc.py index 7dbef31..ec7b704 100644 --- a/sleekxmpp/plugins/xep_0050/adhoc.py +++ b/sleekxmpp/plugins/xep_0050/adhoc.py @@ -149,7 +149,7 @@ class xep_0050(base_plugin): Access control may be implemented in the provided handler. Command workflow is done across a sequence of command handlers. The - first handler is given the intial Iq stanza of the request in order + first handler is given the initial Iq stanza of the request in order to support access control. Subsequent handlers are given only the payload items of the command. All handlers will receive the command's session data.