Spelling

array_api_compat/common/_helpers.py

@@ -593,7 +593,7 @@ def array_namespace(
 
     use_compat: bool or None
         If None (the default), the native namespace will be returned if it is
-        already array API compatible, otherwise a compat wrapper is used. If
+        already array API compatible; otherwise, a compat wrapper is used. If
         True, the compat library wrapped library will be returned. If False,
         the native library namespace is returned.
 

array_api_compat/dask/array/linalg.py

@@ -43,7 +43,7 @@ def qr(  # type: ignore[no-redef]
 # and dask doesn't have the full_matrices keyword
 def svd(x: Array, full_matrices: bool = True, **kwargs: object) -> SVDResult:  # type: ignore[no-redef]
     if full_matrices:
-        raise ValueError("full_matrics=True is not supported by dask.")
+        raise ValueError("full_matrices=True is not supported by dask.")
     return da.linalg.svd(x, coerce_signs=False, **kwargs)
 
 def svdvals(x: Array) -> Array:

docs/changelog.md

@@ -221,7 +221,7 @@ Thomas Li
     `xp.__array_namespace_info__()`.
   - Various fixes to the `clip()` wrappers.
 
-- `torch.conj` now wrapps `torch.conj_physical`, which makes a copy rather
+- `torch.conj` now wraps `torch.conj_physical`, which makes a copy rather
   than setting the conjugation bit, as arrays with the conjugation bit set do
   not support some APIs.
 
@@ -298,7 +298,7 @@ Thomas Li
 
 - New flag `use_compat` to {func}`~.array_namespace` to force the use or
   non-use of the compat wrapper namespace. The default is to return a compat
-  namespace when it is appropiate.
+  namespace when it is appropriate.
 
 - Fix the `copy` flag to `asarray` for NumPy, CuPy, and Dask.
 

docs/dev/releasing.md

@@ -24,7 +24,7 @@
 
   This does mean you can ignore CI failures, but ideally you should fix any
   failures or update the `*-xfails.txt` files before tagging, so that CI and
-  the CuPy tests fully pass. Otherwise it will be hard to tell what things are
+  the CuPy tests fully pass. Otherwise, it will be hard to tell what things are
   breaking in the future. It's also a good idea to remove any xpasses from
   those files (but be aware that some xfails are from flaky failures, so
   unless you know the underlying issue has been fixed, an xpass test is