Update documentations

Author: paulbalandan

user_guide_src/source/changelogs/v4.3.0.rst

@@ -221,7 +221,9 @@ Helpers and Functions
 Error Handling
 ==============
 
-- You can now log deprecation errors instead of throwing them. See :ref:`logging_deprecation_errors` for details.
+- You can now log deprecation warnings instead of throwing exceptions. See :ref:`logging_deprecation_warnings` for details.
+- Logging of deprecations is turned on by default.
+- To *temporarily* enable throwing of deprecations, set the environment variable ``CODEIGNITER_SCREAM_DEPRECATIONS`` to a truthy value.
 
 Others
 ======

user_guide_src/source/general/errors.rst

@@ -134,10 +134,10 @@ Since v4.3.0, you can specify the exit code for your Exception class to implemen
 
 When an exception implementing ``HasExitCodeInterface`` is caught by CodeIgniter's exception handler, the code returned from the ``getExitCode()`` method will become the exit code.
 
-.. _logging_deprecation_errors:
+.. _logging_deprecation_warnings:
 
-Logging Deprecation Errors
-==========================
+Logging Deprecation Warnings
+============================
 
 .. versionadded:: 4.3.0
 
@@ -161,3 +161,6 @@ After that, subsequent deprecations will be logged instead of thrown.
 This feature also works with user deprecations:
 
 .. literalinclude:: errors/014.php
+
+For testing your application you may want to always throw on deprecations. You may configure this by
+setting the environment variable ``CODEIGNITER_SCREAM_DEPRECATIONS`` to a truthy value.