From a39efb029ff8a559d03eb73278237fde51fbaf78 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebasti=C3=A1n=20Ram=C3=ADrez?= Date: Mon, 9 Dec 2019 18:59:29 +0100 Subject: [PATCH] :speech_balloon: Rephrase handling-errors to remove gender while keeping readability (#780) --- docs/tutorial/handling-errors.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/tutorial/handling-errors.md b/docs/tutorial/handling-errors.md index becb84fd5..5d364fd0b 100644 --- a/docs/tutorial/handling-errors.md +++ b/docs/tutorial/handling-errors.md @@ -4,9 +4,9 @@ This client could be a browser with a frontend, the code from someone else, an I You could need to tell that client that: -* He doesn't have enough privileges for that operation. -* He doesn't have access to that resource. -* The item he was trying to access doesn't exist. +* The client doesn't have enough privileges for that operation. +* The client doesn't have access to that resource. +* The item the client was trying to access doesn't exist. * etc. In these cases, you would normally return an **HTTP status code** in the range of **400** (from 400 to 499).