fix minor typos and grammar (#195)

src/15_global_state.md

@@ -1,6 +1,6 @@
 # Global State Management
 
-So far, we've only been working with local state in components, and we’ve seen how to coordinate state between parent and child components. On occasion, there are times where people look for a more general solution for global state management that can work throughout an application.
+So far, we've only been working with local state in components, and we’ve seen how to coordinate state between parent and child components. On occasion, there are times when people look for a more general solution for global state management that can work throughout an application.
 
 In general, **you do not need this chapter.** The typical pattern is to compose your application out of components, each of which manages its own local state, not to store all state in a global structure. However, there are some cases (like theming, saving user settings, or sharing data between components in different parts of your UI) in which you may want to use some kind of global state management.
 

src/appendix_reactive_graph.md

@@ -184,7 +184,7 @@ B (CHECK)    C (CHECK)
    |____D (CHECK)__|
 ```
 
-Now those effects are run. (All of the effects will be marked `Check` at this point.) Before re-running its computation, the effect checks its parents to see if they are dirty. So
+Now those effects are run. (All of the effects will be marked `Check` at this point.) Before re-running its computation, the effect checks its parents to see if they are dirty.
 
 - So `D` goes to `B` and checks if it is `Dirty`.
 - But `B` is also marked `Check`. So `B` does the same thing:

src/deployment/ssr.md

@@ -153,7 +153,7 @@ By default, Fly.io will auto-stop machines that don't have traffic coming to the
 [See this page in the Fly.io docs for more details](https://fly.io/docs/apps/autostart-stop/).
 ```
 
-If you would prefer to use Github Actions to manage your deployments, you will need to create a new access token via the [Fly.io](https://fly.io/) web UI.
+If you prefer to use Github Actions to manage your deployments, you will need to create a new access token via the [Fly.io](https://fly.io/) web UI.
 
 Go to "Account" > "Access Tokens" and create a token named something like "github_actions", then add the token to your Github repo's secrets by going into your project's Github repo, then clicking
 "Settings" > "Secrets and Variables" > "Actions" and creating a "New repository secret" with the name "FLY_API_TOKEN".

src/islands.md

@@ -135,7 +135,7 @@ If you open up the source for the page now, you’ll see that your `HomePage` is
 </leptos-island>
 ```
 
-Only code for what's inside this `<leptos-island>` is compiled to WASM, only only that code runs when hydrating.
+Only code for what's inside this `<leptos-island>` is compiled to WASM, only that code runs when hydrating.
 
 ## Using Islands Effectively
 

src/router/19_a.md

@@ -62,7 +62,7 @@ pub fn App() -> impl IntoView {
     view! {
         <Router>
             <h1>"Contact App"</h1>
-            // this <nav> will show on every routes,
+            // this <nav> will show on every route,
             // because it's outside the <Routes/>
             // note: we can just use normal <a> tags
             // and the router will use client-side navigation

src/ssr/21_cargo_leptos.md

@@ -39,4 +39,4 @@ Once your app has compiled you can open up your browser to [`http://localhost:30
 
 `cargo-leptos` has lots of additional features and built in tools. You can learn more [in its `README`](https://github.com/leptos-rs/cargo-leptos/blob/main/README.md).
 
-But what exactly is happening when you open our browser to `localhost:3000`? Well, read on to find out.
+But what exactly is happening when you open your browser to `localhost:3000`? Well, read on to find out.

src/view/05_forms.md

@@ -71,7 +71,7 @@ view! {
 
 ### Simplifying Controlled Inputs with `bind:`
 
-Adherence to Web standards and a clear division between “reading from a signal” and ”writing to a signal” are good, but creating
+Adherence to Web standards and a clear division between “reading from a signal” and “writing to a signal” are good, but creating
 controlled inputs in this way can sometimes seem like more boilerplate than is really necessary.
 
 Leptos also includes a special `bind:` syntax for inputs that allows you to automatically bind signals to inputs. They do exactly the same thing as the “controlled input” pattern above: create an event listener that updates the signal, and a dynamic property that reads from the signal. You can use `bind:value` for text inputs, `bind:checked` for checkboxes, and `bind:group` for radio button groups.

src/view/06_control_flow.md

@@ -215,7 +215,7 @@ efficient. But if it’s at all expensive to render either branch, reach for
 
 ## Note: Type Conversions
 
-There‘s one final thing it’s important to say in this section.
+There’s one final thing it’s important to say in this section.
 
 Leptos uses a statically-typed view tree. The `view` macro returns different types
 for different kinds of view.