summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorlouiz’ <louiz@louiz.org>2017-01-22 21:30:57 +0100
committerlouiz’ <louiz@louiz.org>2017-01-22 21:32:37 +0100
commitb660a4736778cde8d0805390ffa857b77c271757 (patch)
tree02cdaface15354baa21fd19298abd89c0c0dfa17
parent5d801ddcd025f68d2ec91edf0462091a32c779c1 (diff)
downloadbiboumi-b660a4736778cde8d0805390ffa857b77c271757.tar.gz
biboumi-b660a4736778cde8d0805390ffa857b77c271757.tar.bz2
biboumi-b660a4736778cde8d0805390ffa857b77c271757.tar.xz
biboumi-b660a4736778cde8d0805390ffa857b77c271757.zip
grammar: than <-> as
-rw-r--r--doc/biboumi.1.rst2
-rw-r--r--src/bridge/bridge.cpp2
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/biboumi.1.rst b/doc/biboumi.1.rst
index 592643b..98b941e 100644
--- a/doc/biboumi.1.rst
+++ b/doc/biboumi.1.rst
@@ -297,7 +297,7 @@ On XMPP, unlike on IRC, the displayed order of the messages is the same for
all participants of a MUC. Biboumi can not however provide this feature, as
it cannot know whether the IRC server has received and forwarded the
messages to other users. This means that the order of the messages
-displayed in your XMPP client may not be the same than the order on other
+displayed in your XMPP client may not be the same as the order on other
IRC users’.
History
diff --git a/src/bridge/bridge.cpp b/src/bridge/bridge.cpp
index ca9c9fa..cafcbc3 100644
--- a/src/bridge/bridge.cpp
+++ b/src/bridge/bridge.cpp
@@ -1029,7 +1029,7 @@ void Bridge::send_xmpp_ping_request(const std::string& nick, const std::string&
const std::string& id)
{
// Use revstr because the forwarded ping to target XMPP user must not be
- // the same that the request iq, but we also need to get it back easily
+ // the same as the request iq, but we also need to get it back easily
// (revstr again)
// Forward to the first resource (arbitrary, based on the “order” of the std::set) only
const auto resources = this->resources_in_server[hostname];