diff --git a/include/start.tex b/include/start.tex
index 41dc2ba..24d5f27 100644
--- a/include/start.tex
+++ b/include/start.tex
@@ -40,6 +40,9 @@
 \isbn{978-1-4503-4416-6/16/06}
 \doi{http://dx.doi.org/10.1145/2938559.2938604}
 
+\clubpenalty=10000 
+\widowpenalty = 10000
+
 \input{.xxxnote}
 \input{.draft}
 \input{.blue}
diff --git a/introduction.tex b/introduction.tex
index 0caf1e6..c9de3e6 100644
--- a/introduction.tex
+++ b/introduction.tex
@@ -1,5 +1,6 @@
 \section{introduction}
 
+\begin{comment}
 Current operating systems are already proficient at managing certain system
 resources, such as the CPU, memory, and disk. But on interactive mobile devices,
 users care more about resources such as time, battery life, and money, that are
@@ -10,6 +11,7 @@ a metered data plan. It is the degree to which mobile devices effectively
 manage these human-facing resources that determines a user's
 \textit{quality of experience} (QoE), and it is QoE which should drive not just
 policy, but decisions on mobile devices.
+\end{comment}
 
 \begin{sloppypar}
 While modern operating systems such as Android make decisions based on policies
@@ -37,7 +39,7 @@ frequency, such as for time-insensitive background tasks or when the performance
 increase would not be perceivable, negative QoE may manifest itself through
 poor battery life.
 
-\newpage
+%\newpage
 In terms of QoE, static policies can lead to resource allocation decisions that
 are less than optimal. To remedy this, we propose designing QoE-centric
 mobile operating systems that use QoE as input to drive resource allocation
diff --git a/paper.tex b/paper.tex
index 561180c..3c9a84b 100644
--- a/paper.tex
+++ b/paper.tex
@@ -48,7 +48,7 @@
 
 \maketitle
 
-%\input{abstract.tex}
+\input{abstract.tex}
 \input{introduction.tex}
 \input{design.tex}