From ccc34576444e6cddc40115e085284a51ea4dddfd Mon Sep 17 00:00:00 2001 From: Josef Brandl Date: Tue, 3 Oct 2017 21:07:13 +0200 Subject: [PATCH] Fix mistake --- .../src/ch12-06-writing-to-stderr-instead-of-stdout.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 6c91378d5..b7c8f89f9 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 @@ -4,7 +4,7 @@ At the moment we’re writing all of our output to the terminal with the `println!` function. Most terminals provide two kinds of output: *standard output* for general information (sometimes abbreviated as `stdout` in code), and *standard error* for error messages (`stderr`). This distinction enables -users to choose whether to direct the successful output of a program to a +users to choose to direct the successful output of a program to a file but still print error messages to the screen. The `println!` function is only capable of printing to standard output, though,