Fix a few typos and remove unused includes

Author: jmcarcell

DDCore/include/DD4hep/Detector.h

@@ -34,7 +34,6 @@
 #include <map>
 #include <vector>
 #include <string>
-#include <cstdio>
 #include <memory>
 
 // Forward declarations
@@ -216,14 +215,14 @@ namespace dd4hep {
                                               unsigned int excludeFlag=0 ) const = 0 ;
 #endif
 
-    /** Miscaneleous accessors to the detexctor description  */
+    /** Miscaneleous accessors to the detector description  */
 
     /// Register new parent detector using the detector name.
     /** Volumes must be registered/declared PRIOR to be picked up!
      *  Once registered, Detector::pickMotherVolume(detector) will automatically return the
      *  proper parent volume!
      * 
-     *  The method throws an exception if another volume was already declared for this subdetector
+     *  The method throws an exception if another volume was already declared for this subdetector.
      *  The method throws an exception if the volume to be registered is invalid.
      */
     virtual void   declareParent(const std::string& detector_name, const DetElement& det) = 0;

DDCore/include/DD4hep/SignalHandler.h

@@ -13,9 +13,6 @@
 #ifndef DD4HEP_DDCORE_SIGNALHANDLER_H
 #define DD4HEP_DDCORE_SIGNALHANDLER_H
 
-/// System include files
-#include <csignal>
-
 /// Namespace for the AIDA detector description toolkit
 namespace dd4hep {
 

DDCore/src/DetectorLoad.cpp

@@ -136,7 +136,7 @@ void DetectorLoad::processXMLElement(const std::string& xmlfile, const xml::Hand
       PluginDebug dbg;
       result = PluginService::Create<long>(type, m_detDesc, &handle);
       if ( 0 == result )  {
-        throw std::runtime_error("dd4hep: Failed to locate plugin to interprete files of type"
+        throw std::runtime_error("dd4hep: Failed to locate plugin to interpret files of type"
                                  " \"" + tag + "\" - no factory:" + type + ". " + dbg.missingFactory(type));
       }
     }

DDCore/src/SignalHandler.cpp

@@ -15,6 +15,7 @@
 #include <DD4hep/Printout.h>
 #include <DD4hep/SignalHandler.h>
 
+#include <csignal>
 #include <map>
 #include <memory>
 #include <string>

DDCore/src/plugins/LCDDConverter.cpp

@@ -1063,7 +1063,7 @@ void LCDDConverter::handleProperties(Detector::Properties& prp) const {
         PluginDebug dbg;
         result = PluginService::Create<long>(tag, &m_detDesc, ptr, &vals);
         if (0 == result) {
-          except("LCDDConverter", "Failed to locate plugin to interprete files of type"
+          except("LCDDConverter", "Failed to locate plugin to interpret files of type"
                  " \"" + tag + "\" - no factory:" + type + ". " +
                  dbg.missingFactory(tag));
         }

DDG4/src/Geant4Interrupts.cpp

@@ -16,6 +16,8 @@
 #include <DDG4/Geant4Kernel.h>
 #include <DDG4/Geant4Interrupts.h>
 
+#include <csignal>
+
 /// Default SIGINT handler: trigger end-of-event-loop in Geant4Kernel object
 bool dd4hep::sim::Geant4Interrupts::default_sigint_handler(void* user_context, int)   {
   Geant4Kernel* krnl = (Geant4Kernel*)user_context;

DDParsers/include/Parsers/spirit/GrammarsV2.h

@@ -22,7 +22,6 @@
 //==============================================================================
 #include <string>
 #include <vector>
-#include <deque>
 #include <list>
 #include <set>
 #include <map>

DDParsers/include/Parsers/spirit/ParsersFactory.h

@@ -16,8 +16,6 @@
 // STD & STL
 // ============================================================================
 #include <string>
-#include <vector>
-#include <map>
 // ============================================================================
 // Boost:
 // ============================================================================

doc/usermanuals/DD4hep/chapters/basics.tex

@@ -434,7 +434,7 @@ \section{The Detector Description Data Hub: \texttt{Detector}}
 
 \section{Detector Description Persistency in \texttt{XML}}
 \label{sec:compact-xml-structure}
-As explained in a previous section, the mechanism involved in the data loading allows an application to be fairly independent of the technology used to populate the transient detector representation. However, if one wants to use a given technology, she/he has to get/provide the corresponding conversion mechanism. The choice of \texttt{XML} was driven mainly by its easiness of use and the number of tools provided for its manipulation and parsing. Moreover, \texttt{XML} data can be easily translated into many other format using tools like \texttt{XSLT}  processors. The grammar used for the \texttt{XML} data is pretty simple and straight forward, actually very similar to other geometry description languages based on \texttt{XML}. For example the material description is nearly identical to the material description in \texttt{GDML}~\cite{Chytracek:2006be}. The syntactic structure of the compact \texttt{XML} description was taken from the SiD detector description~\cite{Gaede:81331}. The following listing shows the basic layout of any the compact detector description file with its different sections:
+As explained in a previous section, the mechanism involved in the data loading allows an application to be fairly independent of the technology used to populate the transient detector representation. However, if one wants to use a given technology, she/he has to get/provide the corresponding conversion mechanism. The choice of \texttt{XML} was driven mainly by its easiness of use and the number of tools provided for its manipulation and parsing. Moreover, \texttt{XML} data can be easily translated into many other format using tools like \texttt{XSLT}  processors. The grammar used for the \texttt{XML} data is pretty simple and straight forward, actually very similar to other geometry description languages based on \texttt{XML}. For example the material description is nearly identical to the material description in \texttt{GDML}~\cite{Chytracek:2006be}. The syntactic structure of the compact \texttt{XML} description was taken from the SiD detector description~\cite{Gaede:81331}. The following listing shows the basic layout of the compact detector description file with its different sections:
 
 \begin{minted}[frame=single,framesep=3pt,breaklines=true,tabsize=2,linenos,fontsize=\small]{xml}
 <lccdd>

examples/DDDigi/scripts/DigiTest.py

@@ -105,7 +105,7 @@ def next_input(self):
       self.used_inputs = []
     next_source = self.inputs[len(self.used_inputs)]
     self.used_inputs.append(next_source)
-    self.info('Prepariing next input file: ' + str(next_source))
+    self.info('Preparing next input file: ' + str(next_source))
     return next_source
 
   def run_checked(self, num_events=5, num_threads=5, parallel=3):