Some doc fixing

Author: patel-vansh

user_guide_src/source/changelogs/v4.8.0.rst

@@ -74,6 +74,8 @@ Model
 Libraries
 =========
 
+- **Context**: This new feature allows you to easily set and retrieve normal or hidden contextual data for the current request. See :ref:`Context <context>` for details.
+
 Helpers and Functions
 =====================
 

user_guide_src/source/general/context.rst

@@ -1,7 +1,11 @@
+.. _context:
+
 ###################
 Context
 ###################
 
+.. versionadded:: 4.8.0
+
 .. contents::
     :local:
     :depth: 2
@@ -19,9 +23,9 @@ The Context class is particularly useful for:
 - Adding contextual information to your logs automatically
 - Storing sensitive data that should not appear in logs
 
-******************
-Accessing Context
-******************
+***********************
+Accessing Context Class
+***********************
 
 You can access the Context service anywhere in your application using the ``service()`` function:
 
@@ -123,7 +127,9 @@ To remove all context data:
 Hidden Context Data
 *********************
 
-The Context class provides a separate storage area for sensitive data that should not be included in logs. This is useful for storing API keys, passwords, tokens, or other sensitive information that you need to access during the request but don't want to expose in log files.
+The Context class provides a separate storage area for sensitive data that should not be included in logs.
+This is useful for storing API keys, passwords, tokens, or other sensitive information that you need to access
+during the request but don't want to expose in log files.
 
 Setting Hidden Data
 ===================
@@ -172,18 +178,21 @@ To clear both regular and hidden data:
 
 .. literalinclude:: context/022.php
 
-.. important:: Regular data and hidden data are stored separately. A key can exist in both regular and hidden storage with different values. Use ``get()`` for regular data and ``getHidden()`` for hidden data.
+.. important:: Regular data and hidden data are stored separately. A key can exist in both regular and hidden storage
+with different values. Use ``get()`` for regular data and ``getHidden()`` for hidden data.
 
 ***********************************
 Integration with Logging
 ***********************************
 
-The Context class integrates seamlessly with CodeIgniter's logging system. When enabled, context data is automatically appended to log messages, providing additional information for debugging and monitoring.
+The Context class integrates seamlessly with CodeIgniter's logging system. When enabled, context data is automatically
+appended to log messages, providing additional information for debugging and monitoring.
 
 Enabling Global Context Logging
 ================================
 
-To enable automatic logging of context data, set the ``$logGlobalContext`` property to ``true`` in your **app/Config/Logger.php** file:
+To enable automatic logging of context data, set the ``$logGlobalContext`` property to ``true`` in your
+**app/Config/Logger.php** file:
 
 .. literalinclude:: context/023.php
 
@@ -197,7 +206,8 @@ This would produce a log entry like:
 
     ERROR - 2026-02-18 --> Payment processing failed {"user_id":123,"transaction_id":"txn_12345"}
 
-.. note:: Hidden data set with ``setHidden()`` is **never** included in logs, even when ``$logGlobalContext`` is enabled. This ensures sensitive information like API keys or tokens remain secure.
+.. note:: Hidden data set with ``setHidden()`` is **never** included in logs, even when ``$logGlobalContext`` is enabled.
+This ensures sensitive information like API keys or tokens remain secure.
 
 ***************
 Important Notes

user_guide_src/source/general/logging.rst

@@ -118,6 +118,35 @@ Several core placeholders exist that will be automatically expanded for you base
 | {env:foo}      | The value of 'foo' in $_ENV                       |
 +----------------+---------------------------------------------------+
 
+.. _logging-global-context:
+
+Global Context Logging
+----------------------
+
+.. versionadded:: 4.8.0
+
+You can automatically append context data to all log messages by enabling the ``$logGlobalContext``
+property in **app/Config/Logger.php**:
+
+.. literalinclude:: context/023.php
+
+When enabled, all regular context data (set via the :ref:`Context class <context>`) is automatically
+appended to every log message as a JSON string:
+
+.. literalinclude:: context/024.php
+
+This would produce a log entry like:
+
+.. code-block:: text
+
+    ERROR - 2026-02-18 --> Payment processing failed {"user_id":123,"transaction_id":"txn_12345"}
+
+.. note:: Hidden data set with ``setHidden()`` is **never** included in log output, even when
+    ``$logGlobalContext`` is enabled. This protects sensitive information such as API keys
+    and tokens from appearing in log files.
+
+See :ref:`context` for full documentation on storing and managing context data.
+
 Using Third-Party Loggers
 =========================