[DOC] remove reference to catchError, fix mistake in changelog

CHANGELOG.md

@@ -16,7 +16,7 @@ All changes are documented here in no particular order.
 
 - components can now have empty content or multiple root nodes (htmlelement or text) ([details](#31-components-can-now-have-arbitrary-content))
 - new `useEffect` hook ([doc](doc/reference/hooks.md#useeffect))
-- new `onDestroyed`, `onWillRender` and `onRendered` hooks ([doc](doc/reference/component.md#lifecycle))
+- new `onWillDestroy`, `onWillRender` and `onRendered` hooks ([doc](doc/reference/component.md#lifecycle))
 - breaking: lifecycle methods are removed ([details](#1-component-lifecycle-methods-are-removed))
 - breaking: can no longer be mounted on detached DOM ([details](#2-components-can-no-longer-be-mounted-in-a-detached-dom-element))
 - breaking: standalone `mount` method API is simpler ([details](#4-mount-method-api-is-simpler))

doc/reference/component.md

@@ -19,7 +19,7 @@
   - [`onError`](#onerror)
 - [Sub components](#sub-components)
 - [Dynamic Sub components](#dynamic-sub-components)
-- [`status` helper]
+- [`status` helper](#status-helper)
 
 ## Overview
 

doc/reference/error_handling.md

@@ -26,7 +26,7 @@ normal state.
 
 Whenever the `onError` lifecycle hook is used, all errors coming from
 sub components rendering and/or lifecycle method calls will be caught and given
-to the `catchError` method. This allows us to properly handle the error, and to
+to the `onError` method. This allows us to properly handle the error, and to
 not break the application.
 
 There are important things to know: