1 files changed, 4 insertions, 4 deletions
diff --git a/src/ipc_state.cpp b/src/ipc_state.cpp
index 62b1828..fca4e59 100644
--- a/src/ipc_state.cpp
+++ b/src/ipc_state.cpp

@@ -71,10 +71,10 @@ struct IPCState {
  }
  void SetTrackerSlot(std::string server, std::string user) {
-    // This is function is called from the APState thread, not the main thread,
+    // This function is called from the APState thread, not the main thread, and
-    // and it mutates protected state. It only really competes with OnMessage(),
+    // it mutates protected state. It only really competes with OnMessage(), when
-    // when a "Connect" message is received. If this is called right before,
+    // a "Connect" message is received. If this is called right before, and the
-    // and the tracker slot does not match the old game slot, it will initiate a
+    // tracker slot does not match the old game slot, it will initiate a
    // disconnect, and then the OnMessage() handler will see should_disconnect
    // and stop processing the "Connect" message. If this is called right after
    // and the slot does not match, IPC will disconnect, which is tolerable.

diff --git a/src/ipc_state.cpp b/src/ipc_state.cpp index 62b1828..fca4e59 100644 --- a/src/ipc_state.cpp +++ b/src/ipc_state.cpp
@@ -71,10 +71,10 @@ struct IPCState {
71	}	71	}
72		72
73	void SetTrackerSlot(std::string server, std::string user) {	73	void SetTrackerSlot(std::string server, std::string user) {
74	// This is function is called from the APState thread, not the main thread,	74	// This function is called from the APState thread, not the main thread, and
75	// and it mutates protected state. It only really competes with OnMessage(),	75	// it mutates protected state. It only really competes with OnMessage(), when
76	// when a "Connect" message is received. If this is called right before,	76	// a "Connect" message is received. If this is called right before, and the
77	// and the tracker slot does not match the old game slot, it will initiate a	77	// tracker slot does not match the old game slot, it will initiate a
78	// disconnect, and then the OnMessage() handler will see should_disconnect	78	// disconnect, and then the OnMessage() handler will see should_disconnect
79	// and stop processing the "Connect" message. If this is called right after	79	// and stop processing the "Connect" message. If this is called right after
80	// and the slot does not match, IPC will disconnect, which is tolerable.	80	// and the slot does not match, IPC will disconnect, which is tolerable.