Skip to content

Commit bf33d01

Browse files
thewtexCode Review
authored andcommitted
Merge "DOC: Fix typos in the SW guide LaTeX files."
2 parents 96cf1cf + 3ef24e6 commit bf33d01

2 files changed

Lines changed: 4 additions & 4 deletions

File tree

SoftwareGuide/Latex/DG05-SoftwareProcess.tex

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -199,8 +199,8 @@ \section{Working The Process}
199199
day to the CDash dashboard. Developers who checked in code are expected to
200200
visit the dashboard and ensure their changes are acceptable---that is, they
201201
do not introduce compilation errors or warnings, or break any other tests
202-
including regression, memory, PrintSelf, and Set/Get. Again, developers are
203-
expected to fix problems immediately.
202+
including regression, memory, \code{PrintSelf}, and \code{Set}/\code{Get}.
203+
Again, developers are expected to fix problems immediately.
204204

205205
The release cycle occurs a small number of times a year. This requires
206206
tagging and branching the Git repository, updating documentation, and
@@ -222,7 +222,7 @@ \section{The Effectiveness of the Process}
222222
The effectiveness of this process is profound. By providing immediate
223223
feedback to developers through email and Web pages (e.g., the dashboard), the
224224
quality of ITK is exceptionally high, especially considering the complexity
225-
of the algorithms and system. Errors, when accidently introduced, are caught
225+
of the algorithms and system. Errors, when accidentally introduced, are caught
226226
quickly, as compared to catching them at the point of release. To wait to the
227227
point of release is to wait too long, since the causal relationship between a
228228
code change or addition and a bug is lost. The process is so powerful that it

SoftwareGuide/Latex/I02-Installation.tex

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ \section{Using CMake for Configuring and Building ITK}
140140
CMake generates native Makefiles or workspaces to be used with the corresponding
141141
development environment of your choice. For example, on UNIX and Cygwin systems,
142142
CMake generates Makefiles; under Microsoft Windows CMake generates Visual Studio
143-
workspaces; CMake is also capable of generateing appropriate build files for
143+
workspaces; CMake is also capable of generating appropriate build files for
144144
other development environments, e.g., Eclipse. The information used by CMake is
145145
provided in \code{CMakeLists.txt} files that are present in every directory of
146146
the ITK source tree. Along with the specification of project structure and code

0 commit comments

Comments
 (0)