typos: fix typos in comments

Author: mathstuf

Accelerators/Vtkm/Filters/Testing/Cxx/TestVTKMExtractVOI.cxx

@@ -36,7 +36,7 @@ int TestVTKMExtractVOI(int argc, char* argv[])
   voi->SetVOI(-11, 39, 5, 45, 0, 0);
   voi->SetSampleRate(5, 5, 1);
 
-  // Get rid of ambiguous triagulation issues.
+  // Get rid of ambiguous triangulation issues.
   vtkNew<vtkDataSetSurfaceFilter> surf;
   surf->SetInputConnection(voi->GetOutputPort());
 

Accelerators/Vtkm/Filters/Testing/Cxx/TestVTKMHistogram.cxx

@@ -315,7 +315,7 @@ void testHistogramWithPointData(vtkmHistogram* filter, bool isPointType)
   VerifyHistogram(filter, isPointType);
 }
 
-} // anomynous namespace
+} // anonymous namespace
 
 int TestVTKMHistogram(int, char*[])
 {

CMake/patches/3.22/FindMPI.cmake

@@ -432,7 +432,7 @@ function (_MPI_interrogate_compiler LANG)
   # a particular MPICH derivate might check compiler interoperability.
   # Intel MPI in particular does this with I_MPI_CHECK_COMPILER.
   file(TO_NATIVE_PATH "${CMAKE_${LANG}_COMPILER}" _MPI_UNDERLAYING_COMPILER)
-  # On Windows, the Intel MPI batch scripts can only work with filnames - Full paths will break them.
+  # On Windows, the Intel MPI batch scripts can only work with filenames - Full paths will break them.
   # Due to the lack of other MPICH-based wrappers for Visual C++, we may treat this as default.
   if(MSVC)
     get_filename_component(_MPI_UNDERLAYING_COMPILER "${_MPI_UNDERLAYING_COMPILER}" NAME)

CMake/vtkModule.cmake

@@ -749,7 +749,7 @@ function (vtk_module_scan)
     endif ()
 
     # Throw error when mutually exclusive options are present.
-    # When a module opts into marshalling, it requries the hierarchy
+    # When a module opts into marshalling, it requires the hierarchy
     if (${_vtk_scan_module_name}_EXCLUDE_WRAP AND ${_vtk_scan_module_name}_INCLUDE_MARSHAL)
       message(FATAL_ERROR
         "The ${_vtk_scan_module_name} module can not declare `EXCLUDE_WRAP` and `INCLUDE_MARSHAL` at the same time.")
@@ -4204,7 +4204,7 @@ function (vtk_module_add_module name)
     # XXX(cmake-3.23): file sets
     if (NOT _vtk_build_USE_FILE_SETS OR
         CMAKE_VERSION VERSION_LESS "3.23" OR
-        # XXX(cmake-3.19): Using a non-`INTERACE` `FILE_SET`s with `INTERFACE`
+        # XXX(cmake-3.19): Using a non-`INTERFACE` `FILE_SET`s with `INTERFACE`
         # targets is not yet supported.
         (CMAKE_VERSION VERSION_LESS "3.19" AND
          _vtk_add_module_HEADER_ONLY))

CMake/vtkModuleTesting.cmake

@@ -57,7 +57,7 @@ endfunction ()
 # Opt-in option from projects using VTK to activate SSIM baseline comparison
 if (DEFINED DEFAULT_USE_SSIM_IMAGE_COMP AND DEFAULT_USE_SSIM_IMAGE_COMP)
   set(default_image_compare "VTK_TESTING_IMAGE_COMPARE_METHOD=TIGHT_VALID")
-# We are compiling VTK standalone if we succed the following condition
+# We are compiling VTK standalone if we succeed the following condition
 elseif (DEFINED VTK_VERSION)
   set(default_image_compare "VTK_TESTING_IMAGE_COMPARE_METHOD=TIGHT_VALID")
 else()
@@ -321,7 +321,7 @@ C++ tests
     current source directory. If alternate baseline images are required,
     ``<NAME>`` may be suffixed by ``_1``, ``_2``, etc. The valid image is passed via
     the ``-V`` flag.
-    - ``TIGHT_VALID``: Uses euclidian type metrics to compare baselines. Baseline
+    - ``TIGHT_VALID``: Uses euclidean type metrics to compare baselines. Baseline
     comparison is sensitive to outliers in this setting.
     - ``LOOSE_VALID``: Uses L1 type metrics to compare baselines. Baseline comparison
     is somewhat more forgiving. Typical use cases involve rendering that is highly GPU
@@ -710,7 +710,7 @@ Options:
 - ``JUST_VALID``: Only applies when neither ``NO_VALID`` or ``NO_RT`` are present.
   If it is not specified, the test is run via ``vtkmodules.test.rtImageTest``.
 - ``TIGHT_VALID``: Default behavior if legacy image comparison method is turned off by default.
-  The baseline is tested using an euclidian metric, which is sensitive to outliers.
+  The baseline is tested using an euclidean metric, which is sensitive to outliers.
 - ``LOOSE_VALID``: The baseline is tested using an norm-1 metric, which is less sensitive to
   outliers. It should typically be used when comparing text or when testing rendering that
   varies a lot depending on the GPU drivers.

CMake/vtkTypeLists.cmake

@@ -2,7 +2,7 @@
 # vtkTypeLists
 
 This module provides lists of (c++) data type supported by VTK.
-A CamelCase formated list is also provided to easily construct
+A CamelCase formatted list is also provided to easily construct
 class names.
 
 This is useful to generate template instantiation at configure time.

Charts/Core/vtkScatterPlotMatrix.cxx

@@ -757,7 +757,7 @@ void vtkScatterPlotMatrix::AdvanceAnimation()
       // add 3d renderer to render window.
       renWin->AddRenderer(this->Private->BigChart3DRenderer);
       // DO NOT ERASE main scene renderer. Allow the 2D scatter plots to remain on the color
-      // attachment. we don't want to draw those unncessarily during animation because it tanks
+      // attachment. we don't want to draw those unnecessarily during animation because it tanks
       // framerate.
       this->Scene->GetRenderer()->EraseOff();
       this->Private->CurrentAngle = 0.0;

Common/ComputationalGeometry/Testing/Cxx/UnitTestParametricSpline.cxx

@@ -269,7 +269,7 @@ int TestSetGet()
     ++status;
   }
 
-  // Now change the spline tyeps
+  // Now change the spline types
   vtkSmartPointer<vtkKochanekSpline> xSpline = vtkSmartPointer<vtkKochanekSpline>::New();
   pspline->SetXSpline(xSpline);
   className = pspline->GetXSpline()->GetClassName();

Common/ComputationalGeometry/vtkBilinearQuadIntersection.h

@@ -35,7 +35,7 @@ class VTKCOMMONCOMPUTATIONALGEOMETRY_EXPORT vtkBilinearQuadIntersection
 
   /**
    * Compute cartesian coordinates of point in the quad
-   * using parameteric coordinates
+   * using parametric coordinates
    */
   vtkVector3d ComputeCartesianCoordinates(double u, double v);
 

Common/Core/vtkDeserializer.h

@@ -38,7 +38,7 @@ class VTKCOMMONCORE_EXPORT vtkDeserializer : public vtkObject
    * Constructs an object of type `className`.
    *
    * If a constructor is not found for `className`, the `GetConstructor` walks through each item
-   * in `superClassNames` and attempts to contruct an instance of that type.
+   * in `superClassNames` and attempts to construct an instance of that type.
    * This is useful when the VTK build of the serializer side and the deserializer side
    * are on entirely different platforms by taking advantage of the object factory mechanism.
    *
@@ -48,7 +48,7 @@ class VTKCOMMONCORE_EXPORT vtkDeserializer : public vtkObject
    * Let's suppose in a Windows VTK application, the `vtkSerializer` serialized an instance of
    * `vtkWin32RenderWindowInteractor` into json which was then transferred over the network
    * to a macOS machine. Over there, seeing that the state refers to the
-   * `vtkWin32RenderWindowInteractor` calss the `vtkDeserializer` will attempt to find a constructor
+   * `vtkWin32RenderWindowInteractor` class the `vtkDeserializer` will attempt to find a constructor
    * for win32 class and fail. It then checks if the super class (here `vtkRenderWindowInteractor`)
    * has a constructor and constructs a new instance of that type. Due to the object factory
    * mechanism, the macOS build of VTK constructs a `vtkCocoaRenderWindowInteractor` and it all