From 3d4d91a462c8d211caf857d3b9ce3d2421871e81 Mon Sep 17 00:00:00 2001 From: Erik Johnston Date: Tue, 1 Mar 2016 16:15:59 +0000 Subject: [PATCH] Reword to make sense --- specification/modules/presence.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/specification/modules/presence.rst b/specification/modules/presence.rst index de327e3c..52e59970 100644 --- a/specification/modules/presence.rst +++ b/specification/modules/presence.rst @@ -66,10 +66,10 @@ b) a presence state other than ``online``. During this period clients must consider the user to be currently active, irrespective of the last active time. The last active time must be up to date whenever the server gives a presence -event to the client; the ``currently_active`` mechanism should purely be used to -disable as opposed to disabling last active tracking. Thus clients can fetch up -to date last active times by explicitly requesting the presence for a given -user. +event to the client. The ``currently_active`` mechanism should purely be used by +servers to stop sending continuous presence updates, as opposed to disabling +last active tracking entirely. Thus clients can fetch up to date last active +times by explicitly requesting the presence for a given user. Idle timeout ~~~~~~~~~~~~