docs: minor improvement for docs (bytecodealliance#11952)

Signed-off-by: geogrego <[email protected]>

Author: geogrego

cranelift/codegen/src/machinst/buffer.rs

@@ -1608,7 +1608,7 @@ impl<I: VCodeInst> MachBuffer<I> {
         // relocation or to the veneer inserted. Additionally
         // `MachBuffer` needs the concept of a label which will never be
         // resolved, so `emit_island` doesn't trip over not actually ever
-        // knowning what some labels are. Currently the loop in
+        // knowing what some labels are. Currently the loop in
         // `finish_emission_maybe_forcing_veneers` would otherwise infinitely
         // loop.
         //

crates/wasmtime/src/runtime/component/resources/host_dynamic.rs

@@ -46,7 +46,7 @@ use wasmtime_environ::component::{CanonicalAbiInfo, InterfaceType};
 /// to know how to destroy the associated state, if any, that
 /// [`ResourceDynamic`] references. The difference with [`Resource`] is that is
 /// has runtime type information instead of static type information, meaning
-/// that it's possible to mix these up at compile by by accident.
+/// that it's possible to mix these up at compile by accident.
 ///
 /// However a [`ResourceDynamic`] can be constructed dynamically at runtime with
 /// a runtime-defined type. For example an embedding that provides generic

crates/wizer/src/info.rs

@@ -4,7 +4,7 @@ use std::ops::Range;
 /// Info that we keep track of on a per module-within-a-module-linking-bundle
 /// basis.
 ///
-/// These are created during during our `parse` pass and then used throughout
+/// These are created during our `parse` pass and then used throughout
 /// our later passes.
 #[derive(Default)]
 pub struct ModuleContext<'a> {

examples/min-platform/embedding/src/lib.rs

@@ -85,7 +85,7 @@ fn config() -> Config {
         // isn't possible in no_std. For x86_64 we can use the cpuid instruction
         // bound through an external crate.
         //
-        // Note that CPU support for these features has existend since 2013
+        // Note that CPU support for these features has existed since 2013
         // (Haswell) on Intel chips and 2012 (Piledriver) on AMD chips.
         unsafe {
             config.detect_host_feature(move |feature| {

examples/min-platform/src/main.rs

@@ -82,7 +82,7 @@ fn main() -> Result<()> {
     //
     // Note that the embedding will need to check that these features are
     // actually available at runtime. CPU support for these features has
-    // existend since 2013 (Haswell) on Intel chips and 2012 (Piledriver) on
+    // existed since 2013 (Haswell) on Intel chips and 2012 (Piledriver) on
     // AMD chips.
     if cfg!(target_arch = "x86_64") {
         unsafe {