Bump crate-ci/typos from 1.29.10 to 1.30.0

.github/workflows/ValidatePullRequest.yml

@@ -64,4 +64,4 @@ jobs:
     steps:
     - uses: actions/checkout@v4
     - name: Spell Check Repo
-      uses: crate-ci/typos@v1.29.10
+      uses: crate-ci/typos@v1.30.0

src/hyperlight_host/src/hypervisor/surrogate_process_manager.rs

@@ -335,7 +335,7 @@ fn ensure_surrogate_process_exe() -> Result<()> {
 
         if embedded_file_sha != file_on_disk_sha {
             println!(
-                "sha of embedded surrorate '{}' does not match sha of file on disk '{}' - deleting surrogate binary at {}",
+                "sha of embedded surrogate '{}' does not match sha of file on disk '{}' - deleting surrogate binary at {}",
                 embedded_file_sha,
                 file_on_disk_sha,
                 &surrogate_process_path.display()

src/hyperlight_host/src/mem/mgr.rs

@@ -584,7 +584,7 @@ impl SandboxMemoryManager<HostSharedMemory> {
         // the guest manipulating this memory location because the only
         // addresses that are valid are in its own address space.
         //
-        // When executing in-process, maniulating this pointer could cause the
+        // When executing in-process, manipulating this pointer could cause the
         // host to execute arbitrary functions.
         let guest_ptr = GuestPtr::try_from(RawPtr::from(guest_dispatch_function_ptr))?;
         guest_ptr.absolute()

src/hyperlight_host/src/mem/shared_mem.rs

@@ -229,7 +229,7 @@ unsafe impl Send for GuestSharedMemory {}
 /// sadly, mostly un-adopted for C++23, although that does not concern
 /// us), the paper did not actually redefine volatile accesses or data
 /// races to prevent volatile accesses from racing with other accesses
-/// and causing undefined behaviour.  P1382R1 [5] would have amendend
+/// and causing undefined behaviour.  P1382R1 [5] would have amended
 /// the wording of the data race definition to specifically exclude
 /// volatile, but, unfortunately, despite receiving a
 /// generally-positive reception at its first WG21 meeting more than
@@ -257,7 +257,7 @@ unsafe impl Send for GuestSharedMemory {}
 /// In short, none of the Rust-level operations available to us do the
 /// right thing, at the Rust spec level or the LLVM spec level. Our
 /// major remaining options are therefore:
-///   - Choose one of the options that is avaiblale to us, and accept
+///   - Choose one of the options that is available to us, and accept
 ///     that we are doing something unsound according to the spec, but
 ///     hope that no reasonable compiler could possibly notice.
 ///   - Use inline assembly per architecture, for which we would only

src/hyperlight_host/src/sandbox/initialized_multi_use.rs

@@ -121,7 +121,7 @@ impl MultiUseSandbox {
     /// // original `sbox` variable.
     /// let mut ctx = sbox.new_call_context();
     ///
-    /// // Do a guest call with the context. Assues that the loaded binary
+    /// // Do a guest call with the context. Assumes that the loaded binary
     /// // ("some_guest_binary") has a function therein called "SomeGuestFunc"
     /// // that takes a single integer argument and returns an integer.
     /// match ctx.call(

typos.toml

@@ -3,3 +3,7 @@ extend-ignore-identifiers-re = ["Fo"]
 
 [files]
 extend-exclude = ["**/*.patch", "src/hyperlight_guest/third_party/**/*", "NOTICE.txt"]
+
+[default.extend-words]
+# typ is used for field name as type is a reserved keyword
+typ="typ"