diff --git a/ARCHITECTURE.md b/ARCHITECTURE.md
index 0225d302d..ccd0191f0 100644
--- a/ARCHITECTURE.md
+++ b/ARCHITECTURE.md
@@ -220,8 +220,8 @@ for reference: they include large amounts of manual SSR route handling, etc.
 ## `cargo-leptos` helpers
 
 `leptos_config` and `leptos_hot_reload` exist to support two different features
-of `cargo-leptos`, namely its configuration and its view-patching/hot-
-reloading features.
+of `cargo-leptos`, namely its configuration and its view-patching/hot-reloading 
+features.
 
 It’s important to say that the main feature `cargo-leptos` remains its ability
 to conveniently tie together different build tooling, compiling your app to
diff --git a/docs/book/src/reactivity/interlude_functions.md b/docs/book/src/reactivity/interlude_functions.md
index 18034cc04..de13d0a43 100644
--- a/docs/book/src/reactivity/interlude_functions.md
+++ b/docs/book/src/reactivity/interlude_functions.md
@@ -68,7 +68,7 @@ pub fn SimpleCounter(cx: Scope) -> impl IntoView {
 
 The `SimpleCounter` function itself runs once. The `value` signal is created once. The framework hands off the `increment` function to the browser as an event listener. When you click the button, the browser calls `increment`, which updates `value` via `set_value`. And that updates the single text node represented in our view by `{value}`.
 
-Closures are key to reactivity. They provide the framework with the ability to rerun the smallest possible unit of your application in responsive to a change.
+Closures are key to reactivity. They provide the framework with the ability to rerun the smallest possible unit of your application in response to a change.
 
 So remember two things: