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>

examples/PWA-example/public/sw.js

@@ -137,7 +137,7 @@ self.addEventListener("fetch", function (event) {
              - You should also consider the origin. It's easier to decide what
                "unavailable" means for requests against your origins than for requests
                against a third party, such as an ad provider.
-             - Generate a Response programmaticaly, as shown below, and return that.
+             - Generate a Response programmatically, as shown below, and return that.
           */
 
           //console.log('WORKER: fetch request failed in both cache and network.');

examples/counters.rs

@@ -12,7 +12,7 @@ fn app() -> Element {
     // Store the counters in a signal
     let mut counters = use_signal(|| vec![0, 0, 0]);
 
-    // Whenver the counters change, sum them up
+    // Whenever the counters change, sum them up
     let sum = use_memo(move || counters.read().iter().copied().sum::<i32>());
 
     rsx! {

examples/crm.rs

@@ -7,7 +7,7 @@
 //! in a way that works across pages.
 //!
 //! We implement a number of important details here too, like focusing inputs, handling form submits, navigating the router,
-//! platform-specific configuration, and importing 3rd party CSS libaries.
+//! platform-specific configuration, and importing 3rd party CSS libraries.
 
 use dioxus::prelude::*;
 

examples/flat_router.rs

@@ -1,5 +1,5 @@
 //! This example shows how to use the `Router` component to create a simple navigation system.
-//! The more complex router example uses all of the router features, while this simple exmaple showcases
+//! The more complex router example uses all of the router features, while this simple example showcases
 //! just the `Layout` and `Route` features.
 //!
 //! Layouts let you wrap chunks of your app with a component. This is useful for things like a footers, heeaders, etc.

examples/form.rs

@@ -37,7 +37,7 @@ fn app() -> Element {
 
                     // On desktop/liveview, the form will not navigate the page - the expectation is that you handle
                     // The form event.
-                    // Howver, if your form doesn't have a submit handler, it might navigate the page depending on the webview.
+                    // However, if your form doesn't have a submit handler, it might navigate the page depending on the webview.
                     // We suggest always attaching a submit handler to the form.
                     onsubmit: move |ev| {
                         println!("Submit event: {:#?}", ev);

examples/future.rs

@@ -1,6 +1,6 @@
 //! A simple example that shows how to use the use_future hook to run a background task.
 //!
-//! use_future won't return a value, analagous to use_effect.
+//! use_future won't return a value, analogous to use_effect.
 //! If you want to return a value from a future, use use_resource instead.
 
 use dioxus::prelude::*;

examples/multiwindow.rs

@@ -1,6 +1,6 @@
 //! Multiwindow example
 //!
-//! This exmaple shows how to implement a simple multiwindow application using dioxus.
+//! This example shows how to implement a simple multiwindow application using dioxus.
 //! This works by spawning a new window when the user clicks a button. We have to build a new virtualdom which has its
 //! own context, root elements, etc.
 

examples/openid_connect_demo/Dioxus.toml

@@ -3,7 +3,7 @@
 # dioxus project name
 name = "OpenID Connect authentication demo"
 
-# default platfrom
+# default platform
 # you can also use `dioxus serve/build --platform XXX` to use other platform
 # value: web | desktop
 default_platform = "web"

examples/optional_props.rs

@@ -31,7 +31,7 @@ fn app() -> Element {
             e: "asd".to_string(),
         }
 
-        // `b` and `e` are ommitted
+        // `b` and `e` are omitted
         Button {
             a: "asd".to_string(),
             c: "asd".to_string(),

examples/rsx_usage.rs

@@ -261,7 +261,7 @@ mod baller {
     }
 }
 
-/// Documention for this component is visible within the rsx macro
+/// Documentation for this component is visible within the rsx macro
 #[component]
 pub fn Taller(
     /// Fields are documented and accessible in rsx!

examples/signals.rs

@@ -1,6 +1,6 @@
 //! A simple example demonstrating how to use signals to modify state from several different places.
 //!
-//! This simlpe example implements a counter that can be incremented, decremented, and paused. It also demonstrates
+//! This simple example implements a counter that can be incremented, decremented, and paused. It also demonstrates
 //! that background tasks in use_futures can modify the value as well.
 //!
 //! Most signals implement Into<ReadOnlySignal<T>>, making ReadOnlySignal a good default type when building new

examples/web_component.rs

@@ -14,14 +14,14 @@ fn app() -> Element {
     rsx! {
         div {
             h1 { "Web Components" }
-            CoolWebComponet { my_prop: "Hello, world!".to_string() }
+            CoolWebComponent { my_prop: "Hello, world!".to_string() }
         }
     }
 }
 
 /// A web-component wrapped with a strongly typed interface using a component
 #[component]
-fn CoolWebComponet(my_prop: String) -> Element {
+fn CoolWebComponent(my_prop: String) -> Element {
     rsx! {
         // rsx! takes a webcomponent as long as its tag name is separated with dashes
         web-component {