Shuffling words around for the page limit.

Author: jssmith1

progNav Paper/progNav Paper.tex

@@ -284,7 +284,7 @@ \section{Preliminary Evaluation}
 
 %We chose two tasks that (differentiate between the two tasks... up and down?)
 
-To evaluate the usability of Flower, we administered an adapted version of the Post-Study System Usability Questionnaire (PSSUQ)~\cite{Lewis95ibmcomputer} after participants had completed both tasks. We modified the questionnaire by replacing ``this system'' with ``this tool'' and asked questions from the System Quality and Interface Quality categories.
+To evaluate the usability of Flower, we administered an adapted version of the Post-Study System Usability Questionnaire (PSSUQ)~\cite{Lewis95ibmcomputer}. We modified the questionnaire by replacing ``this system'' with ``this tool'' and asked questions from the System Quality and Interface Quality categories.
 To prompt discussion about the usability of Flower, we also asked participants open-ended questions based on applicable categories from Nielsen's usability heuristics~\cite{Nielsen1992}.
 %To capture participant's experiences that these two metrics overlooked, two of the authors independently examined each audio/video recording and recorded memos. 
 
@@ -425,7 +425,7 @@ \section{Study Limitations}
 \section{Conclusion}
 
 In this work we presented a new tool, Flower, that helps developers navigate program flow with its minimalistic interface. 
-Flower  fills a void between ad-hoc, tool-less, navigation strategies and cumbersome flow visualization tools.
+Flower  fills a void between tool-less navigation strategies and cumbersome flow visualization tools.
 Based on our preliminary evaluation, Flower  was most effective when developers wished to navigate program structures with few branches.
 
 \section{Acknowledgments}