ci: add typos job (#692)

Author: newpavlov

.github/workflows/workspace.yml

@@ -116,3 +116,9 @@ jobs:
         env:
           RUSTDOCFLAGS: "-Dwarnings --cfg docsrs"
         run: cargo doc --no-deps --features std
+
+  typos:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: crate-ci/typos@v1

.typos.toml

@@ -0,0 +1,7 @@
+[files]
+extend-exclude = [
+    ".git/"
+]
+
+[default.extend-words]
+"nto" = "nto"

CHANGELOG.md

@@ -92,7 +92,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - `register_custom_getrandom!` macro [#504]
 - Implementation of `From<NonZeroU32>` for `Error` and `Error::code` method [#507]
 - Internet Explorer 11 support [#554]
-- Target-specific assocciated `Error` constants [#562]
+- Target-specific associated `Error` constants [#562]
 
 ### Changed
 - Use `ProcessPrng` on Windows 10 and up, and use `RtlGenRandom` on older Windows versions [#415]
@@ -240,7 +240,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Changed
 - Update MSRV to 1.36 [#291]
 - Use getentropy on Emscripten [#307]
-- Solaris: consistantly use `/dev/random` source [#310]
+- Solaris: consistently use `/dev/random` source [#310]
 - Move 3ds selection above rdrand/js/custom fallback [#312]
 - Remove buffer zeroing from Node.js implementation [#315]
 - Use `open` instead of `open64` [#326]

README.md

@@ -85,7 +85,7 @@ of randomness based on their specific needs:
 | `rdrand`          | x86, x86-64          | `x86_64-*`, `i686-*`     | [`RDRAND`] instruction
 | `rndr`            | AArch64              | `aarch64-*`              | [`RNDR`] register
 | `wasm_js`         | Web Browser, Node.js | `wasm32‑unknown‑unknown`, `wasm32v1-none` | [`Crypto.getRandomValues`]. Requires feature `wasm_js` ([see below](#webassembly-support)).
-| `efi_rng`         | UEFI                 | `*-unknown‑uefi`         | [`EFI_RNG_PROTOCOL`] with `EFI_RNG_ALGORITHM_RAW` (requires `std` and Nigthly compiler)
+| `efi_rng`         | UEFI                 | `*-unknown‑uefi`         | [`EFI_RNG_PROTOCOL`] with `EFI_RNG_ALGORITHM_RAW` (requires `std` and Nightly compiler)
 | `custom`          | All targets          | `*`                      | User-provided custom implementation (see [custom backend])
 | `unsupported`     | All targets          | `*`                      | Always returns `Err(Error::UNSUPPORTED)` (see [unsupported backend])
 

src/backends/use_file.rs

@@ -27,7 +27,7 @@ const FD_ONGOING_INIT: libc::c_int = -2;
 // In theory `libc::c_int` could be something other than `i32`, but for the
 // targets we currently support that use `use_file`, it is always `i32`.
 // If/when we add support for a target where that isn't the case, we may
-// need to use a different atomic type or make other accomodations. The
+// need to use a different atomic type or make other accommodations. The
 // compiler will let us know if/when that is the case, because the
 // `FD.store(fd)` would fail to compile.
 //

src/backends/windows7.rs

@@ -5,7 +5,7 @@
 //! RNG APIs (and why we don't use BCryptGenRandom). On versions prior to
 //! Windows 10, this implementation is secure. On Windows 10 and later, this
 //! implementation behaves identically to the windows.rs implementation, except
-//! that it forces the loading of an additonal DLL (advapi32.dll).
+//! that it forces the loading of an additional DLL (advapi32.dll).
 //!
 //! This implementation will not work on UWP targets (which lack advapi32.dll),
 //! but such targets require Windows 10, so can use the standard implementation.