Spell check.

Geoffrey Challen
1 parent 0b387634
Showing 5 changed files with 18 additions and 19 deletions
figures/tables/tableALL.tex
introduction.tex
metric.tex
results.tex
usage.tex
@@ -142,7 +142,7 @@
 \caption{\small \textbf{Evaluating Components of a Value Measure.}
 \PhoneLab{} data is used to weight overall app energy usage in a variety of
-different ways. Ommitted results are caused by Android reporting energy
+different ways. Omitted results are caused by Android reporting energy
 consumption for non-apps such as the Android System.}
 \label{table-results}
@@ -64,13 +64,12 @@ smartphones~\cite{jdpowerbatterylife-url}, we believe this effort is
 worthwhile.
 In this paper we motivate the idea of a value measure and describe an early
-failure at developing one based on measuring content delivery. We begin in
-Section~\ref{sec-usage} by describing how useful such a measure would be and
-the results of being able to answer questions like those posed above, as well
-as formulating design requirements for the value measure itself.
-Section~\ref{sec-measure} presents an overview of possible inputs into such a
-measure and discussion of how each could be measured and how useful it might
-be. In Section~\ref{sec-results} we present at formulating a value measure
-based on content delivered through the video display and audio output---an
-attempt that we consider a failure based on the result of a user survey, but
-one that we hope sheds light on how difficult this challenge may be.
+failure at developing one. We begin in Section~\ref{sec-usage} by describing
+how useful such a measure would be while also formulating design requirements
+for the value measure itself. Section~\ref{sec-measure} presents an overview
+of possible inputs into such a measure and discussion of how each could be
+measured and how useful it might be. In Section~\ref{sec-results} we present
+at formulating a value measure based on content delivered through the video
+display and audio output---an attempt that we consider a failure based on the
+result of a user survey, but a failure that we hope sheds some light on this
+difficult challenge.
@@ -26,7 +26,7 @@ foreground information---such as a pedometer app.
 Patterns of interaction may also be useful to observe, and inputs such as
 keystrokes and touchscreen events are simple to track. However, there is more
-obvious differentation between app interaction patterns between
+obvious differentiation between app interaction patterns between
 categories---users deliver far more keystrokes to a chat client than to a
 video player---so it is clear that interaction statistics will have to be
 used in conjunction with complementary value measure components that offset
@@ -6,7 +6,7 @@ large dataset of energy consumption measurements collected by an IRB-approved
 experiment run on the \PhoneLab{} testbed. \PhoneLab{} is a public smartphone
 platform testbed located at the University at
 Buffalo~\cite{phonelab-sensemine13}. 220~students, faculty, and staff carry
-instrumented Android Nexus~5 smartphones and receiv subsidized service in
+instrumented Android Nexus~5 smartphones and receive subsidized service in
 return for willingness to participate in experiments. \PhoneLab{} provides
 access to a representative group of participants balanced between genders and
 across a wide variety of age brackets, making our results more
@@ -112,7 +112,7 @@ redraws.
 \centering
 \includegraphics[width=\textwidth]{./figures/survey.pdf}
-\caption{\textbf{Participant responses to energy inefficient app sugestions.} The height of each bar
+\caption{\textbf{Participant responses to energy inefficient app suggestions.} The height of each bar
 demonstrates how many of the suggested apps the user is willing to remove for better battery life. }
 \label{fig-survey}
@@ -122,7 +122,7 @@ redraws.
 To continue the evaluation of our simple content-based value measure, we
 prepared a survey for the 107~\PhoneLab{} participants who contributed data
 to our experiment. Our goal was to determine if users would be more willing
-to remove inefficienct apps, as defined using our content-based measure. As a
+to remove inefficient apps, as defined using our content-based measure. As a
 baseline, we also asked users about the apps that consumed the most energy.
 We used each participants data to generate a custom survey containing
 questions about 9 apps: the 3 least efficient apps as computed by our
@@ -54,7 +54,7 @@ the second experiment to make it more similar to the first, the adversary
 could remove the apps consuming the least energy up to a given target.
 For our value measure we are hopeful that users will prove capable of
-assiging cardinal utilities to apps---as in the second experiment---since
+assigning cardinal utilities to apps---as in the second experiment---since
 this matches most directly with our proposed value measure and could provide
 ground truth for a value measure computed automatically. The second
 experiment also engages users directly in the task of allocating energy,
@@ -88,7 +88,7 @@ consumption alone~\cite{carat-sensys13}. Consider attempting to compare a
 chat client and videoconferencing app by only measuring their energy
 consumption. Unless it is terribly written, the chat client will consume less
 energy. But this does not mean that it is efficient, or that the
-videconferencing app is not. Ultimately, all the energy consumption
+videoconferencing app is not. Ultimately, all the energy consumption
 comparison truly reveals is that the two apps do different things---which we
 knew.
@@ -104,7 +104,7 @@ By computing value and, thus, energy efficiency, we can overcome these
 weaknesses. A value measure should allow us to compare the efficiency of two
 apps in different categories based on how efficiently they use energy to
 deliver user value, making it possible to compare games to email clients to
-video players. Comparisons within the same app category shoud allow users to
+video players. Comparisons within the same app category should allow users to
 select the most efficient email client or web browser. Aggregating results
 over all users, differences in app energy efficiency should reflect how well
 the app is written and how well it predicts and adapts to users, not just
@@ -154,7 +154,7 @@ However, all of these previous efforts have ignored the critical question of
 mechanisms are, systems that rely on rates will fail if they provide the same
 rate to Skype and Snapchat, or to a very efficient app and an energy virus.
-A measure of value can be used alone or in conjuction with energy consumption
+A measure of value can be used alone or in conjunction with energy consumption
 to help prioritize limited energy resources. The simplest approach is to
 attempt to enforce an energy allocation based on the relative value assigned
 to each app. To encourage apps to be more energy efficient, it may also be