From 71b525e1fa1c74359120634e980256a9489003c0 Mon Sep 17 00:00:00 2001 From: "Kyle P. Johnson" Date: Thu, 14 Aug 2014 16:16:58 -0400 Subject: [PATCH] typos --- docs/errorhandling.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/errorhandling.rst b/docs/errorhandling.rst index 4db7a209..7c557e4f 100644 --- a/docs/errorhandling.rst +++ b/docs/errorhandling.rst @@ -8,17 +8,17 @@ Logging Application Errors Applications fail, servers fail. Sooner or later you will see an exception in production. Even if your code is 100% correct, you will still see exceptions from time to time. Why? Because everything else involved will -fail. Here some situations where perfectly fine code can lead to server +fail. Here are some situations where perfectly fine code can lead to server errors: - the client terminated the request early and the application was still - reading from the incoming data. -- the database server was overloaded and could not handle the query. + reading from the incoming data +- the database server was overloaded and could not handle the query - a filesystem is full - a harddrive crashed - a backend server overloaded - a programming error in a library you are using -- network connection of the server to another system failed. +- network connection of the server to another system failed And that's just a small sample of issues you could be facing. So how do we deal with that sort of problem? By default if your application runs in