typos

Author: musvaage

.spin/cmds.py

@@ -508,7 +508,7 @@ def lint(ctx, branch, uncommitted):
     Examples:
 
     \b
-    For lint checks of your development brach with `main` or a custom branch:
+    For lint checks of your development branch with `main` or a custom branch:
 
     \b
     $ spin lint # defaults to main

benchmarks/benchmarks/bench_io.py

@@ -88,7 +88,7 @@ def setup(self, num_lines):
         # unfortunately, timeit will only run setup()
         # between repeat events, but not for iterations
         # within repeats, so the StringIO object
-        # will have to be rewinded in the benchmark proper
+        # will have to be rewound in the benchmark proper
         self.data_comments = StringIO('\n'.join(data))
 
     def time_comment_loadtxt_csv(self, num_lines):

doc/neps/nep-0021-advanced-indexing.rst

@@ -649,7 +649,7 @@ eventualities.
 Copyright
 ---------
 
-This document is placed under the CC0 1.0 Universell (CC0 1.0) Public Domain Dedication [1]_.
+This document is placed under the CC0 1.0 Universal (CC0 1.0) Public Domain Dedication [1]_.
 
 
 References and footnotes

doc/neps/nep-0048-spending-project-funds.rst

@@ -125,7 +125,7 @@ a volunteer in a reasonable amount of time.
 There are also many tasks, activities, and projects outside of
 development work that are important and could enhance the project or community
 - think of, for example, user surveys, translations, outreach, dedicated
-mentoring of newcomers, community organizating, website improvements, and
+mentoring of newcomers, community organizing, website improvements, and
 administrative tasks.
 
 Time of people to perform tasks is also not the only thing that funds can be

doc/neps/nep-0053-c-abi-evolution.rst

@@ -253,7 +253,7 @@ a user to:
   yet compatible.
 
 The import of ``numpy2_compat`` (and an error when it is missing) will be
-inserted by the NumPy eaders as part of the ``import_array()`` call.
+inserted by the NumPy headers as part of the ``import_array()`` call.
 
 Alternatives
 ============

doc/source/f2py/f2py-testing.rst

@@ -45,7 +45,7 @@ class present in ``util.py``.
 
 This class many helper functions for parsing and compiling test source files. Its child 
 classes can override its ``sources`` data member to provide their own source files.
-This superclass will then compile the added source files upon object creation andtheir
+This superclass will then compile the added source files upon object creation and their
 functions will be appended to ``self.module`` data member. Thus, the child classes will
 be able to access the fortran functions specified in source file by calling
 ``self.module.[fortran_function_name]``.

doc/source/reference/c-api/array.rst

@@ -2920,7 +2920,7 @@ of this useful approach to looping over an array from C.
 
 .. c:function:: void PyArray_ITER_NEXT(PyObject* iterator)
 
-    Incremement the index and the dataptr members of the *iterator* to
+    Increment the index and the dataptr members of the *iterator* to
     point to the next element of the array. If the array is not
     (C-style) contiguous, also increment the N-dimensional coordinates
     array.

doc/source/reference/c-api/datetimes.rst

@@ -194,7 +194,7 @@ Conversion functions
 
     Returns the string length to use for converting datetime
     objects with the given local time and unit settings to strings.
-    Use this when constructings strings to supply to
+    Use this when constructing strings to supply to
     ``NpyDatetime_MakeISO8601Datetime``.
 
 .. c:function:: int NpyDatetime_MakeISO8601Datetime(\

doc/source/reference/simd/build-options.rst

@@ -203,7 +203,7 @@ Behaviors
           # is equivalent to
           python -m build --wheel -Csetup-args=-Dcpu-baseline="sse sse2 sse3 ssse3 sse41 popcnt sse42"
 
-- ``cpu-dispatch`` does not combain any of implied CPU features,
+- ``cpu-dispatch`` does not combine any of implied CPU features,
   so you must add them unless you want to disable one or all of them::
 
     # Only dispatches AVX2 and FMA3

doc/source/reference/simd/how-it-works.rst

@@ -201,7 +201,7 @@ through ``--cpu-dispatch``, but it can also represent other options such as:
       #define NPY__CPU_TARGET_AVX2
       #define NPY__CPU_TARGET_AVX512F
       // our dispatch-able source
-      #include "/the/absuolate/path/of/hello.dispatch.c"
+      #include "/the/absolute/path/of/hello.dispatch.c"
 
 - **(D) Dispatch-able configuration header**: The infrastructure
   generates a config header for each dispatch-able source, this header
@@ -234,7 +234,7 @@ through ``--cpu-dispatch``, but it can also represent other options such as:
           // the additional optimizations, so it could be SSE42 or AVX512F
         #define CURRENT_TARGET(X) NPY_CAT(NPY_CAT(X, _), NPY__CPU_TARGET_CURRENT)
       #endif
-      // Macro 'CURRENT_TARGET' adding the current target as suffux to the exported symbols,
+      // Macro 'CURRENT_TARGET' adding the current target as suffix to the exported symbols,
       // to avoid linking duplications, NumPy already has a macro called
       // 'NPY_CPU_DISPATCH_CURFX' similar to it, located at
       // numpy/numpy/_core/src/common/npy_cpu_dispatch.h