apply feedback from Kevin B.

Author: GlenDC

src/idiomatic/leveraging-the-type-system/raii.md

@@ -1,5 +1,5 @@
 ---
-minutes: 30
+minutes: 60
 ---
 
 # RAII: `Drop` trait
@@ -57,7 +57,7 @@ fn main() -> Result<(), std::io::Error> {
   }
   ```
 
-- Note that `Drop::drop` cannot return errors. Any fallible logic must be
+- Note that `Drop::drop` cannot return a Result. Any fallible logic must be
   handled internally or ignored. In the standard library, errors during FD
   closure inside `Drop` are silently discarded. See the implementation:
   <https://doc.rust-lang.org/src/std/os/fd/owned.rs.html#169-196>

src/idiomatic/leveraging-the-type-system/raii/drop_bomb.md

@@ -48,7 +48,7 @@ fn main() -> io::Result<()> {
   in an unfinished state. The destructor panics if the transaction has not been
   explicitly finalized (for example, with `commit()`).
 
-- The finalizing operation (such as `commit()`) usually take `self` by value.
+- The finalizing operation (such as `commit()`) usually takes `self` by value.
   This ensures that once the transaction is finalized, the original object can
   no longer be used.
 
@@ -62,7 +62,7 @@ fn main() -> io::Result<()> {
   debug builds. Whether this is appropriate depends on the guarantees your API
   must enforce.
 
-- Panicking in Release builds is reasonable when silent misuse would cause major
+- Panicking in release builds is reasonable when silent misuse would cause major
   correctness or security problems.
 
 ## More to explore

src/idiomatic/leveraging-the-type-system/raii/drop_bomb_forget.md

@@ -42,8 +42,8 @@ In the previous slide we saw that calling
 [`std::mem::forget`](https://doc.rust-lang.org/std/mem/fn.forget.html) prevents
 `Drop::drop` from ever running.
 
-Remember that `mem::forget` leaks the value. This is safe in Rust, but the
-memory will not be reclaimed.
+Remember that `mem::forget` intentionally leaks the value. This is memory-safe
+in Rust, but the memory will not be reclaimed.
 
 However, this avoids needing a runtime flag: when the transaction is
 successfully committed, we can _defuse_ the drop bomb — meaning we prevent

src/idiomatic/leveraging-the-type-system/raii/drop_guards.md

@@ -44,7 +44,7 @@ impl Drop for MutexGuard<'_> {
 ## More to Explore
 
 This example shows a C++ style mutex that does not contain the data it protects.
-While this is non idiomatic in Rust, the goal here is only to illustrate the
+While this is non-idiomatic in Rust, the goal here is only to illustrate the
 core idea of a drop guard, not to demonstrate a proper Rust mutex design.
 
 For brevity, several features are omitted:
@@ -54,7 +54,7 @@ For brevity, several features are omitted:
   mechanism.
 - Ergonomic access via `Deref` and `DerefMut` on `MutexGuard` (letting the guard
   behave like a `&T` or `&mut T`).
-- A fully blocking `.lock()` method and a non blocking `try_lock` variant.
+- A fully blocking `.lock()` method and a non-blocking `try_lock` variant.
 
 You can explore the
 [`Mutex` implementation in Rust’s std library](https://doc.rust-lang.org/std/sync/struct.Mutex.html)

src/idiomatic/leveraging-the-type-system/raii/drop_skipped.md

@@ -56,11 +56,11 @@ fn main() {
 - Remove the `mem::forget` call, then uncomment the `panic!` below it. What do
   you expect now?
 
-  With the default `panic=unwind` setting, the stack still unwinds and
+  With the default `panic = "unwind"` setting, the stack still unwinds and
   destructors run, even when the panic starts in `main`.
 
   - With
-    [`panic=abort`](https://doc.rust-lang.org/cargo/reference/profiles.html#panic),
+    [`panic = "abort"`](https://doc.rust-lang.org/cargo/reference/profiles.html#panic),
     no unwinding takes place.
 
 - Finally, uncomment the `panic!` inside `Foo::drop` and run it. Ask the class:

src/idiomatic/leveraging-the-type-system/raii/scope_guard.md

@@ -1,7 +1,7 @@
 # Scope Guards
 
 A scope guard uses the `Drop` trait to run cleanup code automatically when a
-scope exits — even during unwinding.
+scope exits, even during unwinding.
 
 ```rust,editable,compile_fail
 use scopeguard::{ScopeGuard, guard};

src/idiomatic/leveraging-the-type-system/typestate-pattern.md

@@ -1,5 +1,5 @@
 ---
-minutes: 30
+minutes: 65
 ---
 
 ## Typestate Pattern: Problem