deletions | additions       diff --git a/section_Apache_Derby_Architecture_subsection__.tex b/section_Apache_Derby_Architecture_subsection__.tex  index 465dad6..84e9fdb 100644  --- a/section_Apache_Derby_Architecture_subsection__.tex  +++ b/section_Apache_Derby_Architecture_subsection__.tex 
...
\section {Apache Derby Architecture} {Introduccton To Apache Derby}  \subsection{Derby Architecture}  Before going in to the details of Derby Optimizer lets look at the Apache Derby architecture. If we consider the module view of Derby architecture it is a system comprised of a monitor and a collection of modules. The monitor is code that maps module requests to implementations based upon the request and the environment. For example with JDK  1.3 the internal request for a JDBC driver the monitor selects Derby’s JDBC 2.0 implementation, while in JDK 1.4 the driver is the JDBC 3.0 implementation. This allows Derby to present a single JDBC driver to the application regardless of JDK and internally the correct driver is loaded.