DOC: Correct typos across documentation (#1603)

Thank you to Jessica Garnett for finding and fixing these typos.

Author: jess-garnett

docs/AnacondaPackages.md

@@ -4,7 +4,7 @@
 
 These builds can on the order of **multiple hours** to complete on x86 systems that predate Intel 13th Generation processors. Be patient. The build looks like it is stuck but python is just taking it's time to recursively figure out the needed DLLs because ITK and VTK create a ton of DLL libraries. This is especially slow on Windows systems.
 
-## Python Varitions
+## Python Variations
 
 - 3.9
 - 3.10

docs/Build_From_Source.md

@@ -78,7 +78,7 @@ This example shows how to configure simplnx to build using Visual Studio IDE
 
 ```shell
 set BUILD_DIR=VisualStudio
-set VCPKG_INSTALL_ROOT=C:/Appications/vcpkg
+set VCPKG_INSTALL_ROOT=C:/Applications/vcpkg
 cd simplnx
 mkdir %BUILD_DIR%
 cd %BUILD_DIR%
@@ -87,15 +87,15 @@ cmake -G "Visual Studio 17 2022" -A x64 -DCMAKE_TOOLCHAIN_FILE=%VCPKG_INSTALL_RO
 
 ### Windows with Ninja and IDE of choice (QtCreator, CLion, command line)
 
-Adjust the below commands to the sytle of your shell (The below example is done in Windows Command Prompt Batch file style).
+Adjust the below commands to the style of your shell (The below example is done in Windows Command Prompt Batch file style).
 
-In this example we are building a Release version of compled into a directory called `Release` inside the source directory. We will be using the `ninja` generator so be sure that ninja.exe is on your PATH
+In this example we are building a Release version compiled into a directory called `Release` inside the source directory. We will be using the `ninja` generator so be sure that ninja.exe is on your PATH
 
 ```shell
 set NINJA_INSTALL=C:/Applications/ninja-win
 set PATH=%PATH%:%NINJA_INSTALL%
 set BUILD_DIR=Release
-set VCPKG_INSTALL_ROOT=C:/Appications/vcpkg
+set VCPKG_INSTALL_ROOT=C:/Applications/vcpkg
 cd simplnx
 mkdir %BUILD_DIR%
 cd %BUILD_DIR%
@@ -140,13 +140,13 @@ cmake -G Ninja -DCMAKE_TOOLCHAIN_FILE=$VCPKG_INSTALL_ROOT/scripts/buildsystems/v
 
 | Identifier | Type | Explanation |
 |------------|------|-------------|
-| `ITKImageProcessing_USE_JOB_POOL` | `BOOL` | When `ON` the amount of threads used to build `ITK` library plugin is capped (see `ITKImageProcessing_JOB_POOL`). Some of the `ITK` files more 2+ GB of memory to compile due to heavy templating. This is to prevent sytems from running out of memory during compilation. |
+| `ITKImageProcessing_USE_JOB_POOL` | `BOOL` | When `ON` the amount of threads used to build `ITK` library plugin is capped (see `ITKImageProcessing_JOB_POOL`). Some of the `ITK` files more 2+ GB of memory to compile due to heavy templating. This is to prevent systems from running out of memory during compilation. |
 | `ITKImageProcessing_JOB_POOL` | `STRING` | If `ITKImageProcessing_USE_JOB_POOL` is `ON`, this variable is the maximum number of threads available to the `ITK` plugin during compilation. For example on a system with 32 threads and 64GB of RAM a value of `16` will prevent out-of-memory errors during compilation. |
 | `SIMPLNX_BUILD_TESTS` | `BOOL` | Turning this on will compile the filter/library tests and include them in the all ctests target |
 | `SIMPLNX_BUILD_DOCS` | `BOOL` | Turning this on will build the library/filters documentation, `SPHINX_BUILD_EXECUTABLE` must be defined |
 | `SPHINX_BUILD_EXECUTABLE` | `PATH` | The absolute path to to the sphinx executable; *required* for `SIMPLNX_BUILD_PYTHON_DOCS` and/or `SIMPLNX_BUILD_DOCS` |
-| `SIMPLNX_EXTRA_PLUGINS` | `STRING` | A list of plugin targets (separated by `;`) to include into the library. Currently the only offical additional plugin not bundled is `SimplnxReview` which is untested filters |
-| `SIMPLNX_ENABLE_BENCHMARK_UTILITY` | `BOOL` | Turning this on will include the preffered benchmarking library; Be sure to **add** `benchmark` **to** `VCPKG_MANIFEST_FEATURES` **list** |
+| `SIMPLNX_EXTRA_PLUGINS` | `STRING` | A list of plugin targets (separated by `;`) to include into the library. Currently the only official additional plugin not bundled is `SimplnxReview` which is untested filters |
+| `SIMPLNX_ENABLE_BENCHMARK_UTILITY` | `BOOL` | Turning this on will include the preferred benchmarking library; Be sure to **add** `benchmark` **to** `VCPKG_MANIFEST_FEATURES` **list** |
 
 ### Python Binding CMake Arguments
 

docs/CMakeLists.txt

@@ -1,7 +1,7 @@
 # ------------------------------------------------------------------------------
 # Building the Developer Documentation using Doxygen is probably not supported
 # and has not been updated since 2021. This is being left in here for historical
-# reasons and incase someone wants to add this capability in the future.
+# reasons and in case someone wants to add this capability in the future.
 # ------------------------------------------------------------------------------
 
 option(SIMPLNX_BUILD_SPHINX_DOCS "Use Doxygen to build developer documentation (Not Supported)" OFF)

docs/Doxyfile.in

@@ -466,7 +466,7 @@ LOOKUP_CACHE_SIZE      = 0
 # than 0 to get more control over the balance between CPU load and processing
 # speed. At this moment only the input processing can be done using multiple
 # threads. Since this is still an experimental feature the default is set to 1,
-# which efficively disables parallel processing. Please report any issues you
+# which effectively disables parallel processing. Please report any issues you
 # encounter. Generating dot graphs in parallel is controlled by the
 # DOT_NUM_THREADS setting.
 # Minimum value: 0, maximum value: 32, default value: 1.

docs/PortingFilters.md

@@ -73,7 +73,7 @@ folder.
 
 The backwards compatibility will begin testing immediately as long as the filter is registered in the `PluginNameUUIDLegacyMapping.hpp` file. The only exception is new filters that have no **SIMPL** equivalent.
 
-To run the test in advance select the `conversion_test` ctest target and run it. Most of the errors are from issues in the filter's `FromSIMPLJson()` function. The error messages should guide you towards a solution. The following cases are exceptions that can be hard to diagnose without apriori knowledge.
+To run the test in advance select the `conversion_test` ctest target and run it. Most of the errors are from issues in the filter's `FromSIMPLJson()` function. The error messages should guide you towards a solution. The following cases are exceptions that can be hard to diagnose without a priori knowledge.
 
 How To Update Test For Filter Changes/Ports
 
@@ -200,7 +200,7 @@ At the current time, the only filters that should be made parallel are those tha
 
 ### Syntax for Simplnx
 
-This is an examplar use case and doesn't truly encompass all possible use cases for the functions, but instead serves to show how it should be structured in most cases.  
+This is an exemplar use case and doesn't truly encompass all possible use cases for the functions, but instead serves to show how it should be structured in most cases.  
 
 In an anonymous namespace:
 ```cpp
@@ -233,7 +233,7 @@ private:
 };
 ```
 
-In the exectuting function:
+In the executing function:
 
 ```cpp
 ParallelDataAlgorithm dataAlg;  
@@ -275,7 +275,7 @@ For progress messaging a throttled messenger class is provided. To initialize it
 ThrottledMessenger throttledMessenger = messageHelper.createThrottledMessenger();
 ```
 
-The throttled messenger will print every 1000 milliseconds (1 second) by default, to change this intialize it as follows:
+The throttled messenger will print every 1000 milliseconds (1 second) by default, to change this initialize it as follows:
 
 ```cpp
 ThrottledMessenger throttledMessenger = messageHelper.createThrottledMessenger(static_cast<std::chrono::milliseconds>(number_in_milliseconds));

docs/dream3d_file_spec.md

@@ -72,7 +72,7 @@ These attributes are on every DataObject:
 
 ### Specific ObjectType Attributes
 
-Based on the ObjectType, there can be additional attriutes that can be read based on the ObjectType value
+Based on the ObjectType, there can be additional attributes that can be read based on the ObjectType value
 
 #### AttributeMatrix
 

src/Plugins/ITKImageProcessing/src/ITKImageProcessing/Filters/ITKSigmoidImageFilter.cpp

@@ -79,7 +79,7 @@ Parameters ITKSigmoidImageFilter::parameters() const
   Parameters params;
   params.insertSeparator(Parameters::Separator{"Input Parameter(s)"});
   params.insert(std::make_unique<Float64Parameter>(k_Alpha_Key, "Alpha", "The Alpha value from the Sigmoid equation. ", 1));
-  params.insert(std::make_unique<Float64Parameter>(k_Beta_Key, "Beta", "The Beta value from teh sigmoid equation", 0));
+  params.insert(std::make_unique<Float64Parameter>(k_Beta_Key, "Beta", "The Beta value from the sigmoid equation", 0));
   params.insert(std::make_unique<Float64Parameter>(k_OutputMaximum_Key, "Output Maximum", "The maximum output value", 255));
   params.insert(std::make_unique<Float64Parameter>(k_OutputMinimum_Key, "Output Minimum", "The minimum output value", 0));
 

src/Plugins/OrientationAnalysis/src/OrientationAnalysis/Filters/Algorithms/ComputeFeatureReferenceMisorientations.cpp

@@ -78,7 +78,7 @@ Result<> ComputeFeatureReferenceMisorientations::operator()()
     return MakeErrorResult(-34900, "Total features was zero. The filter cannot proceed. Check either the feature attribute matrix or the average quaternions for proper size");
   }
 
-  // Create local storage for teh centers and center distances
+  // Create local storage for the centers and center distances
   std::vector<size_t> m_Centers(totalFeatures, 0);
   std::vector<float> m_CenterDistances(totalFeatures, 0.0f);
 

src/Plugins/OrientationAnalysis/test/ComputeTwinBoundariesTest.cpp

@@ -143,7 +143,7 @@ TEST_CASE("OrientationAnalysis::ComputeTwinBoundariesFilter: No Incoherence", "[
 
   // Compare the output arrays with those precalculated from the file
   {
-    // The exemplar algorithm skips invalid values while this algorithm doesn't due to lack of apriori knowledge (face normals array) so we simulate it here
+    // The exemplar algorithm skips invalid values while this algorithm doesn't due to lack of a priori knowledge (face normals array) so we simulate it here
     auto& faceNormals = dataStructure.getDataRefAs<Float64Array>(TwinBoundariesConstants::k_FaceNormalsPath);
     auto& exemplarBoundaries = dataStructure.getDataRefAs<UInt8Array>(TwinBoundariesConstants::k_ExemplarBoundariesPath);
     auto& generatedBoundaries = dataStructure.getDataRefAs<UInt8Array>(TwinBoundariesConstants::k_GeneratedBoundariesPath);

src/Plugins/SimplnxCore/docs/CreateDataArrayAdvancedFilter.md

@@ -24,7 +24,7 @@ The *Step Operation* parameter is active when *Initialization Type* is set to **
 - **Addition [0]**: Each successive element value is the previous value plus the step amount (ascending sequence).
 - **Subtraction [1]**: Each successive element value is the previous value minus the step amount (descending sequence).
 
-When initializing a multicomponent array square bracket notation can be used to specify different initialization values for each component. For example say that I want to intialize a 2 component array where the first component is 0 and the second component is 1 we would use the following input string for the *Initialization Value*
+When initializing a multicomponent array square bracket notation can be used to specify different initialization values for each component. For example say that I want to initialize a 2 component array where the first component is 0 and the second component is 1 we would use the following input string for the *Initialization Value*
 
     0;1