-The type of the parametric lens is \CI{Maybe (MTaskDevice, Int)}. The \gls{SDS}
-can be responsible for the entire list of devices, from now on global.
-Moreover, the \gls{SDS} can focus on a single device, from now on local. A
-local \gls{SDS} can also specifically focus on a single \gls{SDS} on a single
-device, from now on called local-share. The implementation of the real
-\gls{SDS} is given in Listing~\ref{lst:actualdev}. The \gls{SDS} is a lens on
-an actual \gls{SDS} that writes to a file or memory. Reading the \gls{SDS} is
-nothing more than reading the real \gls{SDS}. Writing the \gls{SDS} is a little
-bit more involved. If the write operation originated from a \gls{SDS} focussed
-on a single client-\gls{SDS}, the write action must also be relayed to the
-actual device. If the write originated from a \gls{SDS} focussed the devices or
-on one device only, nothing needs to be done. The notification predicate
-determines whether a watcher gets a notification update.
+The type for the parametric lens of the big \gls{SDS} is \CI{Maybe
+(MTaskDevice, Int)}. The \gls{SDS} is responsible for storing the entire list
+of devices, from now on global. Moreover, the \gls{SDS} can focus on a single
+device, from now on local. A local \gls{SDS} can also specifically focus on a
+single \gls{SDS} on a single device, from now on called local-share. The
+implementation of the real \gls{SDS} is given in Listing~\ref{lst:actualdev}.
+The \gls{SDS} is a lens on an actual \gls{SDS} that writes to a file or memory.
+Reading the \gls{SDS} is nothing more than reading the real \gls{SDS}. Writing
+the \gls{SDS} is a little bit more involved. If the write operation originated
+from a \gls{SDS} focussed on a single client-\gls{SDS}, the write action must
+also be relayed to the actual device. If the write originated from a \gls{SDS}
+focussed the devices or on one device only, nothing needs to be done. The
+notification predicate determines whether a watcher gets a notification update.