ENH: Fix matching parenthesis.

Author: hjmjohnson

SoftwareGuide/Latex/Appendices/CodingStyleGuide.tex

@@ -470,7 +470,7 @@ \section{Naming Conventions}%
 \code{Dimension}, \code{point}, \code{size}, or \code{vector}, instead of
 \code{D}, \code{pt}, \code{sz}, or \code{vec}, respectively). Abbreviations
 are allowable when in common use, and should be in uppercase as in \code{RGB},
-or \code{ID} for ``identifier''.)
+or \code{ID} for ``identifier''.
 \end{itemize}
 
 
@@ -1830,7 +1830,7 @@ \subsection{Class Layout}%
 Classes are declared (\code{.h}) using the following guidelines:
 \begin{itemize}
 \item Begin with the Copyright notice.
-\item Follow with include guards (e.g \code{\#ifndef itkBoxImageFilter\_h})).
+\item Follow with include guards (e.g \code{\#ifndef itkBoxImageFilter\_h}).
 \item Follow with the necessary includes. Include only what is necessary to
 avoid dependency problems.
 \item Place the class in the correct namespace.
@@ -1918,7 +1918,7 @@ \subsection{Class Layout}%
 \begin{itemize}
 \item Begin with the Copyright notice.
 \item Follow with include guards in case of templated classes (e.g
-\code{\#ifndef itkBoxImageFilter\_hxx})).
+\code{\#ifndef itkBoxImageFilter\_hxx}).
 \item Follow with the necessary includes. Include only what is necessary to
 avoid dependency problems.
 \item Place the class in the correct namespace.

SoftwareGuide/Latex/Architecture/Iterators.tex

@@ -460,7 +460,7 @@ \section{Neighborhood Iterators}%
 neighborhood in pixels for dimension $N$.  The length of each face of the
 resulting ND hypercube is $2d + 1$ pixels, a distance of $d$ on either side of
 the single pixel at the neighbor center.
-Figure~{\ref{fig:NeighborhoodIteratorFig2} shows the relationship between the
+Figure~\ref{fig:NeighborhoodIteratorFig2} shows the relationship between the
 radius of the iterator and the size of the neighborhood for a variety of 2D
 iterator shapes.
 

SoftwareGuide/Latex/Architecture/SystemOverview.tex

@@ -295,8 +295,8 @@ \subsection{Error Handling and Exceptions}%
 \end{minted}
 \normalsize
 
-A particular class may throw an exception as demonstrated below (this
-code snippet is taken from \doxygen{ByteSwapper}:
+A particular class may throw an exception as demonstrated below
+(this code snippet is taken from \doxygen{ByteSwapper}):
 
 \small
 \begin{minted}[baselinestretch=1,fontsize=\footnotesize,linenos=false,bgcolor=ltgray]{cpp}
@@ -607,9 +607,9 @@ \section{Data Representation}%
 neighborhood relationships, or to store information on the boundaries of
 cells.
 
-The mesh is defined in terms of three template parameters: 1) a pixel type
-associated with the points, cells, and cell boundaries; 2) the dimension of
-the points (which in turn limits the maximum dimension of the cells); and 3)
+The mesh is defined in terms of three template parameters: (1) a pixel type
+associated with the points, cells, and cell boundaries; (2) the dimension of
+the points (which in turn limits the maximum dimension of the cells); and (3)
 a ``mesh traits'' template parameter that specifies the types of the
 containers and identifiers used to access the points, cells, and/or
 boundaries. By using the mesh traits carefully, it is possible to create

SoftwareGuide/Latex/DevelopmentGuidelines/WriteAFilter.tex

@@ -155,8 +155,8 @@ \section{Overview of Filter Creation}%
 the filter can stream data; that is, process just a portion of the input to
 produce a portion of the output. Often superclass behavior works well: if the
 filter processes the input using single pixel access, then the default
-behavior is adequate. If not, then the user may have to a) find a more
-specialized superclass to derive from, or b) override one or more methods
+behavior is adequate. If not, then the user may have to (a) find a more
+specialized superclass to derive from, or (b) override one or more methods
 that control how the filter operates during pipeline execution. The next
 section describes these methods.
 
@@ -416,9 +416,9 @@ \subsubsection{UpdateOutputData()}%
 \code{Update()} method. The purpose of this method is to determine whether a
 particular filter needs to execute in order to bring its output up to date. (A
 filter executes when its \code{GenerateData()} method is invoked.) Filter
-execution occurs when a) the filter is modified as a result of modifying an
-instance variable; b) the input to the filter changes; c) the input data has
-been released; or d) an invalid RequestedRegion was set previously and the
+execution occurs when (a) the filter is modified as a result of modifying an
+instance variable; (b) the input to the filter changes; (c) the input data has
+been released; or (d) an invalid RequestedRegion was set previously and the
 filter did not produce data. Filters execute in order in the downstream
 direction.  Once a filter executes, all filters downstream of it must also
 execute.