diff --git a/src/15_global_state.md b/src/15_global_state.md index fa29bd0..68515c6 100644 --- a/src/15_global_state.md +++ b/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. diff --git a/src/appendix_reactive_graph.md b/src/appendix_reactive_graph.md index fc42c06..f40d55f 100644 --- a/src/appendix_reactive_graph.md +++ b/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: diff --git a/src/deployment/ssr.md b/src/deployment/ssr.md index ad97aa6..9fc5ac7 100644 --- a/src/deployment/ssr.md +++ b/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". diff --git a/src/islands.md b/src/islands.md index e32b2e7..e37d7a6 100644 --- a/src/islands.md +++ b/src/islands.md @@ -135,7 +135,7 @@ If you open up the source for the page now, you’ll see that your `HomePage` is ``` -Only code for what's inside this `` is compiled to WASM, only only that code runs when hydrating. +Only code for what's inside this `` is compiled to WASM, only that code runs when hydrating. ## Using Islands Effectively diff --git a/src/router/19_a.md b/src/router/19_a.md index 8d0c5bc..f970af8 100644 --- a/src/router/19_a.md +++ b/src/router/19_a.md @@ -62,7 +62,7 @@ pub fn App() -> impl IntoView { view! {

"Contact App"

- // this