summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--server/char_device.h2
-rw-r--r--server/reds.c2
2 files changed, 2 insertions, 2 deletions
diff --git a/server/char_device.h b/server/char_device.h
index 99bdb2e2..c17a40d4 100644
--- a/server/char_device.h
+++ b/server/char_device.h
@@ -138,7 +138,7 @@ int spice_char_device_state_restore(SpiceCharDeviceState *dev,
* Instead, it would have been more appropriate to reset them upon AGEN_CONNECT.
* The client tokens are tracked as part of the SpiceCharDeviceClientState. Thus,
* in order to be backwartd compatible with the client, we need to track the tokens
- * event when the agent is detached. We don't destroy the the char_device state, and
+ * event when the agent is detached. We don't destroy the char_device state, and
* instead we just reset it.
* In addition, there is a misshandling of AGENT_TOKENS message in spice-gtk: it
* overrides the amount of tokens, instead of adding the given amount.
diff --git a/server/reds.c b/server/reds.c
index b3dfb25a..30d0652e 100644
--- a/server/reds.c
+++ b/server/reds.c
@@ -502,7 +502,7 @@ static void reds_reset_vdp(void)
* Instead, it would have been more appropriate to reset them upon AGEN_CONNECT.
* The client tokens are tracked as part of the SpiceCharDeviceClientState. Thus,
* in order to be backward compatible with the client, we need to track the tokens
- * even if the agent is detached. We don't destroy the the char_device state, and
+ * even if the agent is detached. We don't destroy the char_device state, and
* instead we just reset it.
* In addition, there used to be a misshandling of AGENT_TOKENS message in spice-gtk: it
* overrides the amount of tokens, instead of adding the given amount.