tiny edits

diff --git a/personal/_posts/2019-11-25-how-to-panic-in-rust.md b/personal/_posts/2019-11-25-how-to-panic-in-rust.md
index 66ca0ab1d8a7e216b262583a2d1a68cefd842d28..83216ad909561630ab225bf0ec70f3e797ecec73 100644 (file)
--- a/personal/_posts/2019-11-25-how-to-panic-in-rust.md
+++ b/personal/_posts/2019-11-25-how-to-panic-in-rust.md
@@ -151,7 +151,7 @@ However, even with that future extension, I think we have the invariant that whe
 I wonder if there is any case where *both* fields will be useful -- and if not, couldn't we encode that by making them two variants of an `enum`?
 There are probably good reasons against that proposal and for the current design; it would be great to get them documented somewhere. :)
 
 I wonder if there is any case where *both* fields will be useful -- and if not, couldn't we encode that by making them two variants of an `enum`?
 There are probably good reasons against that proposal and for the current design; it would be great to get them documented somewhere. :)
 

-There is a lot more to say, but at this point, I invite you to follow the links to the source code that I included above and read the local comments.
-With the high-level structure in mind, those comments should be able to fill out any missing details.
-If people think this information would be worth putting somewhere more permanently, I'd be happy to work this blog post into some form of docs -- I am not sure what would be a good place for those, though.
+There is a lot more to say, but at this point, I invite you to follow the links to the source code that I included above.
+With the high-level structure in mind, you should be able to follow that code.
+If people think this overview would be worth putting somewhere more permanently, I'd be happy to work this blog post into some form of docs -- I am not sure what would be a good place for those, though.

 And if you find any mistakes in what I wrote, please let me know!
 And if you find any mistakes in what I wrote, please let me know!