some spell checking on the docs (#3285)

Author: zingale

Docs/Migration/Migration.md

@@ -91,7 +91,7 @@ perform the search and replace.
 ### Step 5
 
 AMReX `migration/5-namespace` branch should be used in this step.
-BoxLib has a `BoxLib` namspace, but most of BoxLib classes are not in
+BoxLib has a `BoxLib` namespace, but most of BoxLib classes are not in
 the namespace.  In AMReX, all classes and functions have been moved
 into the `amrex` namespace.  In this step, you can use
 `Tools/Migration/step-5-amrex-namespace/amrex-namespace.sh` to replace

Docs/sphinx_documentation/source/AMReX_Profiling_Tools.rst

@@ -435,7 +435,7 @@ Profiling Options
 
 AMReX's communication algorithms are often regions of code that increase in wall clock time
 when the application is load imbalanced, due to the MPI_Wait calls in these functions.
-To better understand if this is occuring and by how much, you can turn on an AMReX timed
+To better understand if this is occurring and by how much, you can turn on an AMReX timed
 synchronization with the runtime variable: ``amrex.use_profiler_syncs=1`` This adds named timers
 beginning with ``SyncBeforeComms`` immediately prior to the start of the FillBoundary,
 ParallelCopy and particle Redistribute functions, isolating any prior load imbalance to that timer

Docs/sphinx_documentation/source/Basics.rst

@@ -380,7 +380,7 @@ They are briefly introduced in the table below.
    |                                           |        | after the executable.                     |
    +-------------------------------------------+--------+-------------------------------------------+
    | ``amrex:get_command_argument(int n)``     | String | Returns the n-th argument after           |
-   |                                           |        | the exectuable.                           |
+   |                                           |        | the executable.                           |
    +-------------------------------------------+--------+-------------------------------------------+
 
 

Docs/sphinx_documentation/source/BuildingAMReX.rst

@@ -502,7 +502,7 @@ The list of available options is reported in the :ref:`table <tab:cmakevar>` bel
    +------------------------------+-------------------------------------------------+-------------------------+-----------------------+
    | AMReX_EXPORT_DYNAMIC         |  Enable backtrace on macOS                      | NO (unless Darwin)      | YES, NO               |
    +------------------------------+-------------------------------------------------+-------------------------+-----------------------+
-   | AMReX_SENSEI                 |  Enable the SENSEI in situ infrastucture        | NO                      | YES, NO               |
+   | AMReX_SENSEI                 |  Enable the SENSEI in situ infrastructure       | NO                      | YES, NO               |
    +------------------------------+-------------------------------------------------+-------------------------+-----------------------+
    | AMReX_NO_SENSEI_AMR_INST     |  Disables the instrumentation in amrex::Amr     | NO                      | YES, NO               |
    +------------------------------+-------------------------------------------------+-------------------------+-----------------------+
@@ -744,7 +744,7 @@ We do not officially support AMReX on Windows, and many of us do not have access
 machines.  However, we believe there are no fundamental issues for it to work on Windows.
 
 (1) AMReX mostly uses standard C++17.
-We run continous integration tests on Windows with MSVC and Clang compilers.
+We run continuous integration tests on Windows with MSVC and Clang compilers.
 
 (2) We use POSIX signal handling when floating point exceptions, segmentation faults, etc. happen.
 This capability is not supported on Windows.

Docs/sphinx_documentation/source/LinearSolvers.rst

@@ -400,7 +400,7 @@ Some of the linear solvers support curvilinear coordinates including 1D
 spherical and 2d cylindrical :math:`(r,z)`.  In those cases, the
 divergence operator has extra metric terms.  If one does not want the
 solver to include the metric terms because they have been handled in
-other ways, one can turn them off with a setter funtion. For
+other ways, one can turn them off with a setter function. For
 the cell-centered linear solvers `MLABecLaplacian` and `MLPoisson`, one
 can call :cpp:`setMetricTerm(bool)` with :cpp:`false`
 on the :cpp:`LPInfo` object passed to the constructor of linear

Docs/sphinx_documentation/source/SUNDIALS_top.rst

@@ -4,7 +4,7 @@ SUNDIALS
 ========
 
 SUNDIALS stands for **SU**\ite of **N**\onlinear and **DI**\fferential/**AL**\gebraic
-equation **S**\olvers. It consistes of the following six solvers:
+equation **S**\olvers. It consists of the following six solvers:
 
 - CVODE, for initial value problems for ODE systems
 

Docs/sphinx_documentation/source/Visualization.rst

@@ -94,9 +94,9 @@ Amrvis. Additional information is contained in the document
    The settings for Amrvis are saved in the configuration file ``.amrvis.defaults`` in
    your home directory. A default version of this file is available in the parent directory of the
    Amrvis repo. Run the command ``cp Amrvis/amrvis.defaults ~/.amrvis.defaults`` to
-   copy it to your home directory. A color pallete is also available in the Amrvis directory as a file
+   copy it to your home directory. A color palette is also available in the Amrvis directory as a file
    named ``Palette``.
-   To configure Amrvis to use this pallete you can open the ``.amrvis.defaults`` file
+   To configure Amrvis to use this palette you can open the ``.amrvis.defaults`` file
    in your home directory and edit the line containing ``palette`` to point to the
    location of this file. For example,