From 30ec6fc22f9c5a51d9ae94e7cb12b85e992b00a4 Mon Sep 17 00:00:00 2001
From: jchovanec <joelchovanec@gmail.com>
Date: Wed, 7 Jun 2017 02:44:19 -0400
Subject: [PATCH] Corrected error message displayed on example runs in ch12-06.

---
 .../src/ch12-06-writing-to-stderr-instead-of-stdout.md        | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/second-edition/src/ch12-06-writing-to-stderr-instead-of-stdout.md b/second-edition/src/ch12-06-writing-to-stderr-instead-of-stdout.md
index 87b082834..dacbb538f 100644
--- a/second-edition/src/ch12-06-writing-to-stderr-instead-of-stdout.md
+++ b/second-edition/src/ch12-06-writing-to-stderr-instead-of-stdout.md
@@ -37,7 +37,7 @@ expecting printed on the screen, so that means it must have ended up in the
 file. Let's see what *output.txt* contains:
 
 ```text
-Application error: No search string or filename found
+Problem parsing arguments: not enough arguments
 ```
 
 <!-- I don't understand why we send this output to a file to then just say we
@@ -112,7 +112,7 @@ redirecting `stdout` with `>`:
 
 ```text
 $ cargo run > output.txt
-Application error: No search string or filename found
+Problem parsing arguments: not enough arguments
 ```
 
 Now we see our error on the screen, and `output.txt` contains nothing, which is