aboutsummaryrefslogtreecommitdiff
path: root/src/net/zmq.cpp
diff options
context:
space:
mode:
authorAbdullah <73560425+zer-far@users.noreply.github.com>2022-04-27 18:53:03 +0100
committerAbdullah <73560425+zer-far@users.noreply.github.com>2022-04-27 18:53:03 +0100
commit070e41d88b79908107518f8716b9ce8418c4b194 (patch)
tree2493f56395fb73b4ad5fb883ae364868033f2481 /src/net/zmq.cpp
parentMerge pull request #8275 (diff)
downloadmonero-070e41d88b79908107518f8716b9ce8418c4b194.tar.xz
Change "Github" to "GitHub"
Diffstat (limited to '')
-rw-r--r--src/net/zmq.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/net/zmq.cpp b/src/net/zmq.cpp
index bd7855f21..2b3ca8376 100644
--- a/src/net/zmq.cpp
+++ b/src/net/zmq.cpp
@@ -134,7 +134,7 @@ namespace zmq
{
/* ZMQ documentation states that message parts are atomic - either
all are received or none are. Looking through ZMQ code and
- Github discussions indicates that after part 1 is returned,
+ GitHub discussions indicates that after part 1 is returned,
`EAGAIN` cannot be returned to meet these guarantees. Unit tests
verify (for the `inproc://` case) that this is the behavior.
Therefore, read errors after the first part are treated as a