diff --git a/PBDSecPaper.tex b/PBDSecPaper.tex
index 11dd3eb..bba6160 100644
--- a/PBDSecPaper.tex
+++ b/PBDSecPaper.tex
@@ -84,7 +84,7 @@
 	\item The goal being to obtain the same level of abstraction as is writtien into good coding functions.~\cite{Vincentelli2002}
 	\end{itemize}
 \item Security centers around being able to gauge the trustworthiness of components as well as the larger system made of distributed components.
-\item Lack of design/methodology for doing platform-based design of security elements, although conceptual use in mobile embedded systems.
+\item Lack of design/methodology for doing platform-based design of security elements, although conceptual use in mobile embedded systems. \textbf{[Add citation(s) here]}
 \item Ground work for implementing security via PBD exists; this paper is centered around connecting the dots and laying the foundation for framework that will be built upon for creating security in a doucmented, rigorous, standardized way.
 \end{itemize}
 \end{abstract}
@@ -92,7 +92,6 @@
 \section{Previous Work}
 \label{Previous Work}
 \begin{itemize}
-\item Middleware describes software that resides between an application and the inner workings of the system hosting the application.  The purpose of the middleware is to abstract the complexities of the underlying technology from the application layer~\cite{Lang2003}; to act as translation software for communicating from lower level to a higher level.  This is the same sort of ``abstraction bridge'' that is required by the ``meet-in-the-middle'' methodology of PBD, along with the sort of software construct that benefits the virtualization of security component mapping.
 \item As systems move towards more and more complex designs and implementations (as allowed by growths in technology; Moore's Law) the ability to make simplistic changes to these designs becomes exponentially more difficult.  For this reason, levels of abstraction are desired when simplifying the design/evaluation phases of systems development.
 	\begin{itemize}
 	\item Use of system-on-chip (SoC) to replace multi-chip solutions.
@@ -100,7 +99,9 @@ \section{Previous Work}
 		\item Use of SoC to handle encryption/security in a secure and removed manner.
 		\end{itemize}
 	\end{itemize}
+\item Middleware describes software that resides between an application and the inner workings of the system hosting the application.  The purpose of the middleware is to abstract the complexities of the underlying technology from the application layer~\cite{Lang2003}; to act as translation software for communicating from lower level to a higher level.  This is the same sort of ``abstraction bridge'' that is required by the ``meet-in-the-middle'' methodology of PBD, along with the sort of software construct that benefits the virtualization of security component mapping.
 \item ``However, even though current silicon technology is closely following the growing demands; the effort needed in modeling, simulating, and validating such designs is adversely affected.  This is because current modeling tools and frameworks, hardware and software co-design environments, and validation and verification frameworks do not scale with the rising demands.''`\cite{Patel2007}
+\item \textbf{\textit{Add something about previous security work; taxonomy?}}
 \end{itemize}
 
 \section{Considerations}
@@ -126,7 +127,7 @@ \section{Considerations}
 		\item \textbf{Note:} ``If the instruction set architecture (ISA) is kept constant, then software porting is much easier.''~\cite{Vincentelli2002}
 		\end{itemize}
 	\end{itemize}
-\item Where do we gain/lose on shifting the method of design
+\item Where do we gain/lose on shifting the method of design.  Development of these tools implies that there is a need to change the focus and methods of design/development\textbf{[Add Quo Vadis paper citation here]}.
 	\begin{itemize}
 	\item Gain is ease of changes in development and searching of design space
 		\begin{itemize}
@@ -263,7 +264,7 @@ \section{Conclusion}
 	\end{itemize}
 \item Advantages: swap out old security modules with newer ones (re-use of base system), degree of system customization to meet system hardware/software needs
 \item As with any new shift in design methodoloy the largest cost in this new system would be the need for rigorous documentation and standardization of the process, components, and communication elements of said components.
-\item This is why the development of groundwork for PBD-Security designs will be a slow and arduous, but the resulting `paydirt' will be a new set of virtualization tools at abstraction levels with design spaces yet true explored at regualr levels.  The hope of this paper is to begin designing a frame work that pushes for not only better system design and developemtn (PBD) but alos for proper incorporation and planning of system security in an intelligent, rigorous and documented/standardized way.
+\item This is why the development of groundwork for PBD-Security designs will be a slow and arduous work, but the resulting `paydirt' will be a new set of virtualization tools at abstraction levels with design spaces yet true explored at regualr levels.  The hope of this paper is to begin designing a frame work that pushes for not only better system design and development (PBD) but also for proper incorporation and planning of system security in an intelligent, rigorous and documented/standardized way.
 \item Concerns during development:~\cite{Pinto2006}
 	\begin{itemize}
 	\item Common pitfalls are mishandling corner cases and inadvertently misinterpreting changes in the communication semantics