diff --git a/book/src/plumbing/database_and_runtime.md b/book/src/plumbing/database_and_runtime.md
index 947b67c4..06f0636f 100644
--- a/book/src/plumbing/database_and_runtime.md
+++ b/book/src/plumbing/database_and_runtime.md
@@ -31,7 +31,7 @@ There are three key bits of data:
 * The `Shared` struct, which contains the data stored across all snapshots. This is primarily the ingredients described in the [jars and ingredients chapter](./jars_and_ingredients.md), but it also contains some synchronization information (a cond var). This is used for cancellation, as described below.
     * The data in the `Shared` struct is only shared across threads when other threads are active. Some operations, like mutating an input, require an `&mut` handle to the `Shared` struct. This is obtained by using the `Arc::get_mut` methods; obviously this is only possible when all snapshots and threads have ceased executing, since there must be a single handle to the `Arc`.
 * The `Routes` struct, which contains the information to find any particular ingredient -- this is also shared across all handles, and its construction is also described in the [jars and ingredients chapter](./jars_and_ingredients.md). The routes are separated out from the `Shared` struct because they are truly immutable at all times, and we want to be able to hold a handle to them while getting `&mut` access to the `Shared` struct.
-* The `Runtime` struct, which is specific to a particular database instance. It contains the data for a single active thread, along with some links to shraed data of its own.
+* The `Runtime` struct, which is specific to a particular database instance. It contains the data for a single active thread, along with some links to shared data of its own.
 
 ## Incrementing the revision counter and getting mutable access to the jars
 
diff --git a/book/src/plumbing/query_ops.md b/book/src/plumbing/query_ops.md
index 425209ad..f94d0f28 100644
--- a/book/src/plumbing/query_ops.md
+++ b/book/src/plumbing/query_ops.md
@@ -9,6 +9,6 @@ Each of the query storage struct implements the `QueryStorageOps` trait found in
  which defines the basic operations that all queries support. The most important are these two:
 
 * [maybe changed after](./maybe_changed_after.md): Returns true if the value of the query (for the given key) may have changed since the given revision.
-* [Fetch](./fetch.md): Returms the up-to-date value for the given K (or an error in the case of an "unrecovered" cycle).
+* [Fetch](./fetch.md): Returns the up-to-date value for the given K (or an error in the case of an "unrecovered" cycle).
 
-[`plumbing`]: https://github.com/salsa-rs/salsa/blob/master/src/plumbing.rs
\ No newline at end of file
+[`plumbing`]: https://github.com/salsa-rs/salsa/blob/master/src/plumbing.rs