Fix typo

Change-Id: If8b06f8879712ade0bfaaf807c37222bb06bd279
Reviewed-on: https://gerrit.libreoffice.org/71025
Tested-by: Jenkins
Reviewed-by: Jens Carl <j.carl43@gmx.de>

1 files changed, 2 insertions, 2 deletions

diff --git a/connectivity/source/drivers/odbc/OStatement.cxx b/connectivity/source/drivers/odbc/OStatement.cxx
index 3a74bf565fe7..5797ec6e436a 100644
--- a/connectivity/source/drivers/odbc/OStatement.cxx
+++ b/connectivity/source/drivers/odbc/OStatement.cxx
@@ -67,12 +67,12 @@ OStatement_Base::OStatement_Base(OConnection* _pConnection )
 
     //setMaxFieldSize(0);
     // Don't do this. By ODBC spec, "0" is the default for the SQL_ATTR_MAX_LENGTH attribute. We once introduced
-    // this line since an PostgreSQL ODBC driver had a default other than 0. However, current drivers (at least 8.3
+    // this line since a PostgreSQL ODBC driver had a default other than 0. However, current drivers (at least 8.3
     // and later) have a proper default of 0, so there should be no need anymore.
     // On the other hand, the NotesSQL driver (IBM's ODBC driver for the Lotus Notes series) wrongly interprets
     // "0" as "0", whereas the ODBC spec says it should in fact mean "unlimited".
     // So, removing this line seems to be the best option for now.
-    // If we ever again encounter a ODBC driver which needs this option, then we should introduce a data source
+    // If we ever again encounter an ODBC driver which needs this option, then we should introduce a data source
     // setting for it, instead of unconditionally doing it.
 
     osl_atomic_decrement( &m_refCount );