changes for consistency

final/final.tex

@@ -33,7 +33,8 @@
 \begin{center}
 {\Huge Final Report}\\
 \vspace{10 mm}
-{\Huge The {\tt C0} Debugger}\\
+{\Huge {\tt c0db}\\[.4em]
+The {\tt C0} Debugger}\\
 \vspace{10 mm}
 
 Submitted to\\
@@ -65,9 +66,9 @@ Carnegie Mellon University\\
 Finding problems in code is a difficult and time consuming task, one especially
 difficult for programmers learning a new language. To help students more quickly
 find bugs and understand how their programs run, we created an online debugger
-for the {\tt C0} programming language. The {\tt C0} debugger enables users to
-run programs in their browser and break apart the execution when they don't run
-correctly.
+for the {\tt C0} programming language. The {\tt C0} debugger, {\tt c0db},
+enables users to run programs in their browser and break apart the execution
+when they don't run correctly.
 \end{titlepage}
 
 \pagenumbering{roman}
@@ -88,15 +89,15 @@ development we were unable to receive significant use feedback from students.
 That said, we were able to gather feedback and support from current 15-122
 course staff.
 
-In terms of our original vision, the {\tt C0} debugger includes almost every
-feature we planned to implement. Users can input code and either run the program
-straight through or step through execution instruction by instruction. The only
-significant feature that is not currently implemented completely is breakpoints.
-Implementing breakpoints turned out to be significantly more difficult than we
-anticipated, and given our limited time frame, we were unable to come up with an
-adequate solution. We are currently working with Rob Simmons, 15-122 instructor
-and maintainer for the {\tt C0} language standard, to extend the language to
-support breakpoints more easily going forward.
+In terms of our original vision, {\tt c0db} includes almost every feature we
+planned to implement. Users can input code and either run the program straight
+through or step through execution instruction by instruction. The only
+significant feature that is not currently implemented completely is
+breakpoints.  Implementing breakpoints turned out to be significantly more
+difficult than we anticipated, and given our limited time frame, we were unable
+to come up with an adequate solution. We are currently working with Rob
+Simmons, 15-122 instructor and maintainer for the {\tt C0} language standard,
+to extend the language to support breakpoints more easily going forward.
 
 \begin{figure}[h]
   \includegraphics[width=\linewidth]{new-gantt}
@@ -107,7 +108,7 @@ Relative to our revised Gantt Chart (Figure \ref{gantt}) we hit every milestone
 on time. Both the front-end and back-end teams completed their tasks by the end
 of April, at which point we transitioned everyone to user testing, revisions,
 and polishing. Both teams were able to recover from the lag reported in our
-progress report to complete the {\tt C0} debugger.
+progress report to complete {\tt c0db}.
 
 \section{Discussion}
 

final/letter.tex

@@ -19,8 +19,9 @@
 \vspace{5mm}
 
 Included with this letter is our team's final report for the browser-based
-debugger for the c0 language called c0db. The purpose of the report is to
-update you on our progress and to explain and discuss our results.
+debugger for the {\tt C0} language called {\tt c0db}, the {\tt C0} Debugger.
+The purpose of the report is to update you on our progress and to explain and
+discuss our results.
 
 The report describes the problem addressed by our project, our approach to
 solve it, the results we were able to achieve, our challenges and struggles,
@@ -31,10 +32,10 @@ existing platform.
 If you have any further questions or comments, please contact us at
 shyamsur@andrew.cmu.edu.\\
 
-Sincerely,\\\\\\\\
+Sincerely,\\[4em]
 Shyam Raghavan
 
-\encl{project final paper for c0db}
+\encl{project final paper for {\tt c0db}}
 
 \end{letter}
 \end{document}