From 1d2c61323e6cc349d9bb162a6372c10a996d2081 Mon Sep 17 00:00:00 2001
From: Bulat Musin <9249387+bmusin@users.noreply.github.com>
Date: Thu, 11 Jan 2018 09:52:09 +0300
Subject: [PATCH] refine wording

to a string sounds awkward,  to string is, probably, softer on the eye.
---
 first-edition/src/error-handling.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/first-edition/src/error-handling.md b/first-edition/src/error-handling.md
index 02bd67587..aaa26876a 100644
--- a/first-edition/src/error-handling.md
+++ b/first-edition/src/error-handling.md
@@ -917,7 +917,7 @@ Reasonable people can disagree over whether this code is better than the code
 that uses combinators, but if you aren't familiar with the combinator approach,
 this code looks simpler to read to me. It uses explicit case analysis with
 `match` and `if let`. If an error occurs, it simply stops executing the
-function and returns the error (by converting it to a string).
+function and returns the error (by converting it to string).
 
 Isn't this a step backwards though? Previously, we said that the key to
 ergonomic error handling is reducing explicit case analysis, yet we've reverted