Fix typos discovered by codespell

Signed-off-by: Christian Clauss <[email protected]>

Author: cclauss

Justfile

@@ -74,7 +74,7 @@ clean-rust:
 
 # TESTING
 # Some tests cannot run with other tests, they are marked as ignored so that cargo test works
-# there may be tests that we really want to ignore so we cant just use --ignored and we have to
+# there may be tests that we really want to ignore so we can't just use --ignored and we have to
 # Specify the test name of the ignored tests that we want to run
 test-rust target=default-target features="": (test-rust-int "rust" target features) (test-rust-int "c" target features) (test-seccomp target)
     # unit tests

proposals/NNNN-hip-template/README.md

@@ -27,7 +27,7 @@
 This section is incredibly important for producing high-quality, user-focused
 documentation such as release notes or a development roadmap. It should be
 possible to collect this information before implementation begins, in order to
-avoid requiring implementors to split their attention between writing release
+avoid requiring implementers to split their attention between writing release
 notes and implementing the feature itself. HIP editors should help to ensure 
 that the tone and content of the `Summary` section is useful for a wide audience.
 

src/hyperlight_host/src/error.rs

@@ -55,7 +55,7 @@ pub enum HyperlightError {
     BoundsCheckFailed(u64, usize),
 
     /// Checked Add Overflow
-    #[error("Couldnt add offset to base address. Offset: {0}, Base Address: {1}")]
+    #[error("Couldn't add offset to base address. Offset: {0}, Base Address: {1}")]
     CheckedAddOverflow(u64, u64),
 
     /// Cross beam channel receive error

src/hyperlight_host/src/func/call_ctx.rs

@@ -120,7 +120,7 @@ impl SingleUseGuestCallContext {
     /// `args`, and expect the return value have the same type as
     /// `func_ret_type`.
     ///
-    /// Once the call is complete, the 'SingleUseSandbox' will no longer be useable and a new one will need to be created.
+    /// Once the call is complete, the 'SingleUseSandbox' will no longer be usable and a new one will need to be created.
     ///
     /// Rather than call this method directly, consider using the `call_guest_function_by_name` method on the `SingleUseSandbox`
 

src/hyperlight_host/src/func/guest_dispatch.rs

@@ -386,7 +386,7 @@ mod tests {
 
     fn terminate_vcpu_after_1000ms() -> Result<()> {
         // This test relies upon a Hypervisor being present so for now
-        // we will skip it if there isnt one.
+        // we will skip it if there isn't one.
         if !is_hypervisor_present() {
             println!("Skipping terminate_vcpu_after_1000ms because no hypervisor is present");
             return Ok(());
@@ -435,7 +435,7 @@ mod tests {
     #[test]
     fn test_terminate_vcpu_calling_host_spinning_cpu() {
         // This test relies upon a Hypervisor being present so for now
-        // we will skip it if there isnt one.
+        // we will skip it if there isn't one.
         if !is_hypervisor_present() {
             println!("Skipping test_call_guest_function_by_name because no hypervisor is present");
             return;

src/hyperlight_host/src/hypervisor/windows_hypervisor_platform.rs

@@ -99,7 +99,7 @@ impl VMPartition {
         let whvmapgparange2_func = unsafe {
             match try_load_whv_map_gpa_range2() {
                 Ok(func) => func,
-                Err(e) => return Err(new_error!("Cant find API: {}", e)),
+                Err(e) => return Err(new_error!("Can't find API: {}", e)),
             }
         };
 

src/hyperlight_host/src/mem/pe/pe_info.rs

@@ -360,7 +360,7 @@ mod tests {
                 load_address: 5368709120,
                 num_relocations: (900..1200).collect(),
                 // range of possible # of relocations
-                // (hardware dependant)
+                // (hardware dependent)
             }
         } else {
             PEFileTest {

src/hyperlight_host/src/sandbox/run_options.rs

@@ -17,7 +17,7 @@ limitations under the License.
 use tracing::{instrument, Span};
 
 /// Configuration options for setting up a new `UninitializedSandbox` and
-/// subsequent inititialized sandboxes, including `MultiUseSandbox` and
+/// subsequent initialized sandboxes, including `MultiUseSandbox` and
 /// `SingleUseSandbox`.
 ///
 /// A `SandboxRunOptions` instance must be created with either in-process