diff --git a/src/ch09-01-unrecoverable-errors-with-panic.md b/src/ch09-01-unrecoverable-errors-with-panic.md
index 6c590e7..7010ce4 100644
--- a/src/ch09-01-unrecoverable-errors-with-panic.md
+++ b/src/ch09-01-unrecoverable-errors-with-panic.md
@@ -118,4 +118,16 @@ error: Process didn't exit successfully: `target/debug/panic` (exit code: 101)
 ```
 
 That's a lot of output! Line `11` there has the line in our project:
-`src/main.rs` line four.
+`src/main.rs` line four. The key to reading the backtrace is to start from the
+top and read until we see code that we wrote: that's where the problem
+originated. If we didn't want our program to panic here, this line is where we
+would start investigating in order to figure out how we got to this location
+with the values that made our code panic.
+
+Because `panic!` ends the program with no opportunity to recover, it's best to
+not `panic!` in library crates if at all possible. That way, people who use your
+crate get to decide how they want to handle failures from your code, instead of
+you deciding for them. A common pattern when you're writing a binary crate is
+to only `panic!` in the `main` function if an error condition ends up there,
+and to use recoverable errors in all the library functions that might fail.
+Let's look at how to make errors recoverable.