fix most typos, add crate-ci/typos to CI (#2653)

* fix most typos, add crate-ci/typos to CI

---------

Co-authored-by: Jonathan Kelley <jkelleyrtp@gmail.com>

packages/rsx/src/component.rs

@@ -4,7 +4,7 @@
 //! diagnostics. This was refactored from a straightforward parser to this validation approach so
 //! that we can emit errors as diagnostics instead of returning results.
 //!
-//! Using this approach we can provide *much* better errors as well as partial expansion whereever
+//! Using this approach we can provide *much* better errors as well as partial expansion wherever
 //! possible.
 //!
 //! It does lead to the code actually being larger than it was before, but it should be much easier

packages/rsx/src/element.rs

@@ -598,7 +598,7 @@ fn merging_weird_fails() {
 }
 
 #[test]
-fn diagnositcs() {
+fn diagnostics() {
     let input = quote::quote! {
         p {
             class: "foo bar"

packages/rsx/src/ifmt.rs

@@ -13,7 +13,7 @@ use syn::{
 ///
 /// This wraps LitStr with some extra goodies like inline expressions and hot-reloading.
 /// Originally this was intended to provide named inline string interpolation but eventually Rust
-/// actualy shipped this!
+/// actually shipped this!
 #[derive(Debug, PartialEq, Eq, Clone, Hash)]
 pub struct IfmtInput {
     pub source: LitStr,

packages/rsx/src/rsx_block.rs

@@ -25,7 +25,7 @@ use syn::{
 ///  children
 /// }
 ///
-/// Does not make any guarnatees about the contents of the block - this is meant to be verified by the
+/// Does not make any guarantees about the contents of the block - this is meant to be verified by the
 /// element/component impls themselves.
 ///
 /// The name of the block is expected to be parsed by the parent parser. It will accept items out of
@@ -381,7 +381,7 @@ mod tests {
     /// Some tests of partial expansion to give better autocomplete
     #[test]
     fn partial_cases() {
-        let with_hander = quote! {
+        let with_handler = quote! {
             {
                 onclick: move |_| {
                     some.
@@ -389,7 +389,7 @@ mod tests {
             }
         };
 
-        let _block: RsxBlock = syn::parse2(with_hander).unwrap();
+        let _block: RsxBlock = syn::parse2(with_handler).unwrap();
     }
 
     /// Ensure the hotreload scoring algorithm works as expected

packages/rsx/src/scoring.rs

@@ -92,7 +92,7 @@ fn score_attr_value(old_attr: &AttributeValue, new_attr: &AttributeValue) -> usi
         //       right now going from float to int or vice versa will cause a full rebuild
         //       which can get confusing. if we can figure out a way to hotreload this, that'd be great
         (AttrLiteral(left), AttrLiteral(right)) => {
-            // We assign perfect matches for token resuse, to minimize churn on the renderer
+            // We assign perfect matches for token reuse, to minimize churn on the renderer
             match (&left.value, &right.value) {
                 // Quick shortcut if there's no change
                 (Fmted(old), Fmted(new)) if old == new => usize::MAX,
@@ -127,7 +127,7 @@ fn score_attr_value(old_attr: &AttributeValue, new_attr: &AttributeValue) -> usi
             score_attr_value(value_a, value_b)
         }
 
-        // todo: we should try and score recrusively if we can - templates need to propagate up their
+        // todo: we should try and score recursively if we can - templates need to propagate up their
         // scores. That would lead to a time complexity explosion but can be helpful in some cases.
         //
         // If it's expression-type things, we give a perfect score if they match completely

packages/rsx/src/template_body.rs

@@ -3,7 +3,7 @@
 //! The `Callbody` is the contents of the rsx! macro - this contains all the information about every
 //! node that rsx! directly knows about. For loops, if statements, etc.
 //!
-//! However, thre are multiple *templates* inside a callbody - due to how core clones templates and
+//! However, there are multiple *templates* inside a callbody - due to how core clones templates and
 //! just generally rationalize the concept of a template, nested bodies like for loops and if statements
 //! and component children are all templates, contained within the same Callbody.
 //!