docs(database): clarify lockForUpdate driver notes

Signed-off-by: memleakd <121398829+memleakd@users.noreply.github.com>

Author: memleakd

system/Database/BaseBuilder.php

@@ -111,10 +111,8 @@ class BaseBuilder
 
     /**
      * QB FOR UPDATE flag
-     *
-     * @var bool
      */
-    protected $QBLockForUpdate = false;
+    protected bool $QBLockForUpdate = false;
 
     /**
      * QB ORDER BY data

user_guide_src/source/database/query_builder.rst

@@ -777,16 +777,18 @@ Use this method inside a database transaction. The exact locking behavior is
 determined by the database server and transaction isolation level.
 
 This method is supported by the **MySQLi**, **Postgre**, **OCI8**, and
-**SQLSRV** drivers. Unsupported drivers throw a ``DatabaseException``.
-
-SQLSRV uses SQL Server table hints instead of a trailing ``FOR UPDATE`` clause.
-The hint is applied to table references in the ``FROM`` clause; joined tables
-are not hinted. Its exact lock granularity depends on SQL Server's execution
-plan and transaction isolation level. SQLSRV does not support
-``lockForUpdate()`` without a ``FROM`` table or on subqueries.
-
-OCI8 does not support ``lockForUpdate()`` together with ``limit()`` or
-``offset()`` because Oracle does not allow ``FOR UPDATE`` with row limiting.
+**SQLSRV** drivers. Unsupported drivers throw a ``DatabaseException``. See the
+following notes for OCI8 and SQLSRV driver-specific behavior.
+
+.. note:: SQLSRV uses SQL Server table hints instead of a trailing ``FOR UPDATE``
+    clause. The hint is applied to table references in the ``FROM`` clause;
+    joined tables are not hinted. Its exact lock granularity depends on SQL
+    Server's execution plan and transaction isolation level. SQLSRV does not
+    support ``lockForUpdate()`` without a ``FROM`` table or on subqueries.
+
+.. note:: OCI8 does not support ``lockForUpdate()`` together with ``limit()`` or
+    ``offset()`` because Oracle does not allow ``FOR UPDATE`` with row
+    limiting.
 
 .. _query-builder-union: