New.

Geoffrey Challen
1 parent 8c858076
Showing 1 changed file with 5 additions and 6 deletions
usage.tex
@@ -38,10 +38,9 @@ each user enjoys whichever approach is most effective for them.
 \subsection{\texttt{\large PhoneLab} Conductor}
  
 \PhoneLab{} is a large scale smartphone platform testbed at the University at
-Buffalo~\cite{phonelab-sensemine13}. We leverage the Android
-\texttt{logcat} subsystem as a data collection mechanism---experiment apps
-write their data into a system-wide log buffer and we collect and upload this
-data on their behalf.
+Buffalo~\cite{phonelab-sensemine13}. We leverage the Android \texttt{logcat}
+subsystem as a data collection mechanism---experiments log their data into a
+system-wide log buffer and we collect and upload this data on their behalf.
  
 We developed an app called the \PhoneLab{} Conductor for this purpose which
 provides a good example of custom \texttt{maybe} evaluation logic. The goal
@@ -50,7 +49,7 @@ storage usage, and metered data usage. With the \texttt{maybe} statement
 branching between multiple policies for uploading data---such as always
 waiting until the user reaches a plug, or always initiating an upload once
 the storage allocated is 50\% full---the evaluation logic would provide the
-lowest possible score if data had been lost, or otherwise a score combining
+worst possible score if data had been lost, or otherwise a score combining
 the multiple attributes the app is trying to minimize.
  
 Due to the uncertainties we faced during development, we implemented a
@@ -63,7 +62,7 @@ proven essential after deployment---for example, when an upload policy that
 worked previously abruptly stopped working on a newer Android version.
 Development of this app would have been considerably easier using
 \texttt{maybe}, which could automate the process of pushing policies to
-clients in an energy-efficient way, and enable per-user goal-driven
+clients in an energy-efficient way, and enabling per-user goal-driven
 adaptation.