Doc updates.

Author: anthony-tuininga

doc/src/api_manual/module.rst

@@ -364,7 +364,7 @@ Oracledb Methods
 
     The ``use_sni`` parameter is expected to be a boolean which indicates
     whether to use the TLS Server Name Indicator (SNI) extension to bypass the
-    second TLS neogiation that would otherwise be required. This parameter is
+    second TLS negotiation that would otherwise be required. This parameter is
     used in both python-oracledb Thin and Thick modes. The default value is
     False.
 
@@ -697,7 +697,7 @@ Oracledb Methods
 
     The ``use_sni`` parameter is expected to be a boolean which indicates
     whether to use the TLS Server Name Indicator (SNI) extension to bypass the
-    second TLS neogiation that would otherwise be required. This parameter is
+    second TLS negotiation that would otherwise be required. This parameter is
     used in both python-oracledb Thin and Thick modes. The default value is
     False.
 
@@ -1041,7 +1041,7 @@ Oracledb Methods
 
     The ``use_sni`` parameter is expected to be a boolean which indicates
     whether to use the TLS Server Name Indicator (SNI) extension to bypass the
-    second TLS neogiation that would otherwise be required. This parameter is
+    second TLS negotiation that would otherwise be required. This parameter is
     used in both python-oracledb Thin and Thick modes. The default value is
     False.
 
@@ -1522,7 +1522,7 @@ Oracledb Methods
 
     The ``use_sni`` parameter is expected to be a boolean which indicates
     whether to use the TLS Server Name Indicator (SNI) extension to bypass the
-    second TLS neogiation that would otherwise be required. This parameter is
+    second TLS negotiation that would otherwise be required. This parameter is
     used in both python-oracledb Thin and Thick modes. The default value is
     False.
 
@@ -1919,7 +1919,7 @@ Oracledb Methods
 
     The ``use_sni`` parameter is expected to be a boolean which indicates
     whether to use the TLS Server Name Indicator (SNI) extension to bypass the
-    second TLS neogiation that would otherwise be required. This parameter is
+    second TLS negotiation that would otherwise be required. This parameter is
     used in both python-oracledb Thin and Thick modes. The default value is
     False.
 
@@ -2123,7 +2123,8 @@ Oracledb Methods
     ``is_thin_mode()`` will never change for the lifetime of the process.
 
     The attribute :attr:`Connection.thin` can be used to check a connection's
-    mode.
+    mode. The attribute :attr:`ConnectionPool.thin` can be used to check a
+    pool's mode.
 
     .. note::
 
@@ -2495,7 +2496,7 @@ Oracledb Methods
 
     The ``use_sni`` parameter is expected to be a boolean which indicates
     whether to use the TLS Server Name Indicator (SNI) extension to bypass the
-    second TLS neogiation that would otherwise be required. This parameter is
+    second TLS negotiation that would otherwise be required. This parameter is
     used in both python-oracledb Thin and Thick modes. The default value is
     False.
 

doc/src/user_guide/bind.rst

@@ -29,7 +29,7 @@ more than once with different data values.  If you do not use bind variables,
 Oracle must reparse and cache multiple statements.  When using bind variables,
 Oracle Database may be able to reuse the statement execution plan and context.
 
-.. note::
+.. warning::
 
     Never concatenate or interpolate user data into SQL statements:
 

doc/src/user_guide/connection_handling.rst

@@ -2091,10 +2091,11 @@ shrinkage is only initiated when the pool is accessed so pools in fully dormant
 applications will not shrink until the application is next used.
 
 For pools created with :ref:`external authentication <extauth>`, with
-:ref:`homogeneous <connpooltypes>` set to False, or when using :ref:`drcp`,
-then the number of connections opened at pool creation is zero even if a larger
-value is specified for ``min``.  Also, in these cases the pool increment unit
-is always 1 regardless of the value of ``increment``.
+:ref:`homogeneous <connpooltypes>` set to False, or when using :ref:`drcp` (in
+python-oracledb Thick mode), then the number of connections opened at pool
+creation is zero even if a larger value is specified for ``min``.  Also, in
+these cases the pool increment unit is always 1 regardless of the value of
+``increment``.
 
 .. _poolhealth:
 
@@ -2774,6 +2775,10 @@ state can optionally be specified. See the Oracle Database documentation on
 dblatest&id=GUID-661BB906-74D2-4C5D-9C7E-2798F76501B3>`__ for more information
 on purity and connection classes.
 
+Note that when using DRCP with a python-oracledb local :ref:`connection pool
+<connpooling>` in Thick mode, the local connection pool ``min`` value is
+ignored and the pool will be created with zero connections.
+
 **Requesting a Pooled Server**
 
 To request a DRCP pooled server, you can:

doc/src/user_guide/tracing.rst

@@ -248,11 +248,13 @@ Finding the python-oracledb Mode
 
 The boolean attributes :attr:`Connection.thin` and :attr:`ConnectionPool.thin`
 can be used to show the current mode of a python-oracledb connection or pool,
-respectively.  The python-oracledb version can be shown with
-:data:`oracledb.__version__`.
+respectively. The method :meth:`oracledb.is_thin_mode()` can also be used, but
+review its usage notes about when its return value may change.
 
-The information can also be seen in the Oracle Database data dictionary table
-V$SESSION_CONNECT_INFO:
+The python-oracledb version can be shown with :data:`oracledb.__version__`.
+
+Version and mode information can also be seen in the Oracle Database data
+dictionary table V$SESSION_CONNECT_INFO:
 
 .. code-block:: python