-\Glspl{SDS} on a client are available on the server as well. However, the same
-freedom is not given on the \glspl{SDS} that reside on the client. Not all
-types are suitable to be located on a client. Moreover, \glspl{SDS} behave a
-little bit differently on an \gls{mTask} device than in the \gls{iTasks}
-system. In an \gls{iTasks} system, when the \gls{SDS} is updated, a broadcast
-to everyone in the system watching is made to notify them of an update.
-\glspl{SDS} on the device can update very often and the update might not be the
-final value it will get. Therefore a device must publish the \gls{SDS}
-explicitly to save bandwidth.
+\Glspl{SDS} on a client are available on the server as well as regular
+\gls{SDS}. However, the same freedom is not given on the \glspl{SDS} that
+reside on the client. Not all types are suitable to be located on a client.
+Moreover, \glspl{SDS} behave a little different on an \gls{mTask} device
+compared to the \gls{iTasks} system. In an \gls{iTasks} system, when the \gls{SDS}
+is updated, a broadcast to everyone in the system watching is made to notify
+them of the update. \glspl{SDS} can update very often and the
+update might not be the final value it will get. This results in a lot of
+expensive unneeded bandwidth usage. Therefore a device must publish the
+\gls{SDS} explicitly to save bandwidth.