finished error handling guide [skip ci]

docs/guide/rest-error-handling.md

@@ -49,7 +49,6 @@ Sometimes you may want to customize the default error response format. For examp
 using different HTTP statuses to indicate different errors, you would like to always use 200 as HTTP status
 and enclose the actual HTTP status code as part of the JSON structure in the response, like shown in the following,
 
-
 ```
 HTTP/1.1 200 OK
 Date: Sun, 02 Mar 2014 05:31:43 GMT

docs/guide/runtime-logging.md

@@ -162,6 +162,10 @@ under the categories whose names match either `yii\db\*` or `yii\web\HttpExcepti
 ]
 ```
 
+> Info: When an HTTP exception is caught by the [error handler](runtime-handling-errors.md), an error message
+  will be logged with the category name in the format of `yii\web\HttpException:ErrorCode`. For example,
+  the [[yii\web\NotFoundHttpException]] will cause an error message of category `yii\web\HttpException:404`.
+
 
 ### Message Formatting <a name="message-formatting"></a>
 

docs/internals/translation-status.md

@@ -32,8 +32,8 @@ runtime-requests.md                 | Yes
 runtime-responses.md                | Yes
 runtime-sessions-cookies.md         | Yes
 runtime-url-handling.md             |
-runtime-handling-errors.md          |
-runtime-logging.md                  |
+runtime-handling-errors.md          | Yes
+runtime-logging.md                  | Yes
 concept-components.md               | Yes
 concept-properties.md               | Yes
 concept-events.md                   | Yes