Update src/vision/status_quo/alan_runs_into_stack_trouble.md

Author: nikomatsakis

src/vision/status_quo/alan_runs_into_stack_trouble.md

@@ -9,7 +9,7 @@
 
 ### The problem
 
-Alan is working on a networking service written using async Rust and the tokio async runtime. One day, after many changes to his code base, Alan runs his application and hits an error:
+One day, as Alan is working on his async Rust project, he runs his application and hits an error:
 
 ```
 $ .\target\debug\application.exe
@@ -57,4 +57,4 @@ While Alan knew enough about pinning to know how to satisfy the compiler, he did
     * Barbara, as an expert in Rust, may have had the tools to understand that `pin_mut` is used for pinning to the stack while `Box::pin` is for pinning heap allocations.
     * This problem is somewhat subtle, so someone like Niklaus would probably have had a much harder time figuring this out (or even getting the code to compile in the first place).
 * **Could Alan have used another API to achieve the same objectives?**
-    * Perhaps! Tokio's `select!` macro doesn't require explicit pinning of the futures it's provided, but it's unclear to this author whether it would have been smart enough to avoid pinning large futures to the stack. However, pinning is a part of the way one uses futures in Rust, so it's possible that such an issue would have arisen elsewhere.
+    * Perhaps! Tokio's `select!` macro doesn't require explicit pinning of the futures it's provided, but it's unclear to this author whether it would have been smart enough to avoid pinning large futures to the stack. However, pinning is a part of the way one uses futures in Rust, so it's possible that such an issue would have arisen elsewhere.