COMP: Address remote module syntax errors

Author: thewtex

SoftwareGuide/Latex/DevelopmentGuidelines/CreateAModule.tex

@@ -1041,36 +1041,34 @@ \subsection{Procedure for Adding a Remote Module}
 The procedure to publish a new module in ITK is summarized as follows:
 \begin{enumerate}
 \item Publish an open access article describing the module in an online, open
-access journal like The Insight Journal.
+  access journal like The Insight Journal.
 \item Submit a Gerrit patch (see Section~\ref{sec:GitRepository} on
-page~\pageref{sec:GitRepository) that adds a file named
-\code{Modules/Remote/<module name>.remote.cmake}. This file must have the
-following:
-\begin{enumerate}
-\item Dashboard maintainer name and email in the comments.
-\item A call to the \code{itk_fetch_module} CMake function (documented in
-\code{CMake/ITKModuleRemote.cmake}) whose arguments are:
-\begin{enumerate}
-\item The name of the remote module. Note that in each
-\code{<remote module name>.remote.cmake}, the first argument of the function
-\code{itk_fetch_module()} is the name of the remote module, and it has to be
-consistent with the module name defined in the corresponding
-\code{<remote module name>.remote.cmake}. To better distinguish the remote
-modules from the internal ITK modules, the names of the remote modules should
-\textbf{NOT} contain the ``ITK'' string prefix.
-\item A short description of the module with the handle to the open access
-article.
-\item URLs describing the location and version of the code to download. The
-version should be a specific hash.
-\end{enumerate}
-\end{enumerate}
+  page~\pageref{sec:GitRepository} that adds a file named
+  \code{Modules/Remote/<module name>.remote.cmake}. This file must have the
+  following:
+  \begin{enumerate}
+    \item Dashboard maintainer name and email in the comments.
+    \item A call to the \code{itk\_fetch\_module} CMake function (documented in
+      \code{CMake/ITKModuleRemote.cmake}) whose arguments are:
+      \begin{enumerate}
+      \item The name of the remote module. Note that in each
+        \code{<remote module name>.remote.cmake}, the first argument of the function
+        \code{itk\_fetch\_module()} is the name of the remote module, and it has to be
+        consistent with the module name defined in the corresponding
+        \code{<remote module name>.remote.cmake}. To better distinguish the remote
+        modules from the internal ITK modules, the names of the remote modules should
+        \textbf{NOT} contain the ``ITK'' string prefix.
+      \item A short description of the module with the handle to the open access
+        article.
+      \item URLs describing the location and version of the code to download. The
+        version should be a specific hash.
+      \end{enumerate}
+  \end{enumerate}
 \end{enumerate}
 
 After the Remote Module has experienced sufficient testing, and community
-members express broad interests in the contribution, the submitter can then move
+members express broad interest in the contribution, the submitter can then move
 the contribution into the ITK repository via Gerrit code review.
 
 It is possible but not recommended to directly submit a module to Gerrit for
-review without submitting to Insight Journal first. There are no established
-rules on whether a module should be directly merged into the main repository or
-not.
+review without submitting to Insight Journal first.

SoftwareGuide/Latex/Introduction/Installation.tex

@@ -532,7 +532,7 @@ \subsection{Static and Shared Libraries}
 an application. This reduces binary size and ensures that singleton
 variables are unique across the application.
 
-A very advanced CMake configuration variable,
+An advanced CMake configuration variable,
 \code{ITK\_TEMPLATE\_VISIBILITY\_DEFAULT} defines the symbol visibility
 attribute on template classes to \textit{default} on systems that require it
 to perform \code{dynamic\_cast}'s on pointers passed across binaries. The
@@ -554,7 +554,7 @@ \subsection{Compiling ITK}
 and selecting the ``Build'' context menu item.
 
 The build process can take anywhere from 15 minutes to a couple of hours,
-depending on the the build configuration and the performance of your
+depending on the build configuration and the performance of your
 system. If testing is enabled as part of the normal build process,
 about 2400 test programs will be compiled. In this case, you will then need
 to run \code{ctest} to verify that all the components of ITK have been correctly built
@@ -660,7 +660,7 @@ \section{Using ITK as an External Library}
 
 For a project that uses ITK as an external library, it is recommended to
 specify the individual ITK modules in the \code{COMPONENTS} argument in the
-\code{find_package} CMake command:
+\code{find\_package} CMake command:
 
 \small
 \begin{minted}[baselinestretch=1,fontsize=\footnotesize,linenos=false,bgcolor=ltgray]{bash}
@@ -685,7 +685,7 @@ \section{Using ITK as an External Library}
 \normalsize
 
 If you would like to use the CMake ExternalProject
-Module\footnote{url{https://cmake.org/cmake/help/latest/module/ExternalProject.html}}
+Module\footnote{\url{https://cmake.org/cmake/help/latest/module/ExternalProject.html}}
 to download ITK source code when building your ITK application (a.k.a.
 Superbuild ITK), here is a basic CMake snippet for setting up a Superbuild in
 an ITK application project using CMake:
@@ -713,13 +713,13 @@ \section{Using ITK as an External Library}
 \normalsize
 
 More exemplary configurations for superbuild ITK projects can be found in:
-Slicer\footnote{url{https://github.com/Slicer/Slicer},
-BrainsTools\footnote{url{https://github.com/BRAINSia/BRAINSTools}, ITK Wiki
-Examples\footnote{url{https://github.com/InsightSoftwareConsortium/ITKWikiExamples},
+Slicer\footnote{\url{https://github.com/Slicer/Slicer}},
+BrainsTools\footnote{\url{https://github.com/BRAINSia/BRAINSTools}}, ITK Wiki
+Examples\footnote{\url{https://github.com/InsightSoftwareConsortium/ITKWikiExamples}},
 ITK Sphinx
-Examples\footnote{url{https://github.com/InsightSoftwareConsortium/ITKExamples},
+Examples\footnote{\url{https://github.com/InsightSoftwareConsortium/ITKExamples}},
 and ITK Software
-Guide\footnote{url{https://github.com/InsightSoftwareConsortium/ITKSoftwareGuide}.
+Guide\footnote{\url{https://github.com/InsightSoftwareConsortium/ITKSoftwareGuide}}.
 
 \subsection{Hello World!}
 \label{sec:HelloWorldITK}