Generated .pdf file.
Change-Id: I19eb53cd64e19db54f5ae44885e7d5cd33365432
diff --git a/NLSR-Developers-Guide.pdf b/NLSR-Developers-Guide.pdf
new file mode 100644
index 0000000..37bfd92
--- /dev/null
+++ b/NLSR-Developers-Guide.pdf
Binary files differ
diff --git a/figures/generic-lsdb-flow-eps-converted-to.pdf b/figures/generic-lsdb-flow
similarity index 100%
rename from figures/generic-lsdb-flow-eps-converted-to.pdf
rename to figures/generic-lsdb-flow
Binary files differ
diff --git a/intro.tex b/intro.tex
index db91a84..4f2932e 100644
--- a/intro.tex
+++ b/intro.tex
@@ -62,7 +62,7 @@
\begin{figure}
\center
-\includegraphics[width=\linewidth]{figures/system-interaction}
+\includegraphics[width=\linewidth]{figures/system-interaction.pdf}
\caption{Simplified Diagram of the Actions of NLSR's Modules}
\label{fig:system-interaction}
\end{figure}
diff --git a/lsdb.tex b/lsdb.tex
index 31c719e..b5a3e13 100644
--- a/lsdb.tex
+++ b/lsdb.tex
@@ -27,7 +27,7 @@
The LSDB provides three internal interfaces for each of the three types of LSAs to add or update LSAs in the LSDB.
The general logic for each type of LSA installation is similar (Figure~\ref{fig:generic-lsdb-flow}), but there are slight differences in the events that are triggered by an installation or update.
-\begin{figure}
+\begin{figure}[h]
\center
\includegraphics[width=0.5\linewidth]{figures/generic-lsdb-flow}
\label{fig:generic-lsdb-flow}
diff --git a/nlsr-docs.pdf b/nlsr-docs.pdf
new file mode 100644
index 0000000..f892434
--- /dev/null
+++ b/nlsr-docs.pdf
Binary files differ
diff --git a/nlsr-docs.tex b/nlsr-docs.tex
index cec050c..de61c5d 100644
--- a/nlsr-docs.tex
+++ b/nlsr-docs.tex
@@ -13,7 +13,7 @@
\usepackage{multirow}
\title{NLSR Developer's Guide}
-\author[1]{Vince Lehman, Muktdir Chowdhury, Nicholas Gordon}
+\author[1]{Vince Lehman, Muktadir Chowdhury, Nicholas Gordon}
\affil[1]{University of Memphis}
diff --git a/npt.tex b/npt.tex
index 77ca2ff..d9197d4 100644
--- a/npt.tex
+++ b/npt.tex
@@ -9,7 +9,8 @@
\begin{footnotesize}
The ``wire'' arrows represent references (i.e. ``x has y''),
- whereas the ``solid'' arrows represent inheritance (i.e. ``y subclasses x'').
+ whereas the ``solid'' arrows represent inheritance (i.e. ``y subclasses x''). \\
+ The quantification (e.g. 0..*) is standard UML.
\end{footnotesize}
\end{caption}
\label{fig:npt-class-diagram}
@@ -76,6 +77,6 @@
\subsection{Removing routing table pool entries from the pool}
\label{sec:npt-rtpe-del}
-An RTPE will be deleted when, after removing an RTPE from an NPT entry, \texttt{NamePrefixTable::removeEntry()} determines that the just-removed RTPE now has a use count of 0.
+After an RTPE is removed from an NPT entry, it will be deleted from the pool if \texttt{NamePrefixTable::removeEntry()} determines that the RTPE now has a use count of 0.
It will then call \texttt{NamePrefixTable::deleteRtpeFromPool()}, passing the RTPE as a parameter.
The method will erase the element from the hash map that they are contained in.