diff --git a/product_docs/docs/epas/14/epas_upgrade_guide/03_limitations.mdx b/product_docs/docs/epas/14/epas_upgrade_guide/03_limitations.mdx
index 7f5df57f398..59b1f1aa3f3 100644
--- a/product_docs/docs/epas/14/epas_upgrade_guide/03_limitations.mdx
+++ b/product_docs/docs/epas/14/epas_upgrade_guide/03_limitations.mdx
@@ -2,7 +2,8 @@
 title: "Upgrade considerations"
 ---
 
-The following limitations apply to upgrading EDB Postgres Advanced Server:
+Consider the following when upgrading EDB Postgres Advanced Server:
+
 
 -   The `pg_upgrade` utility cannot upgrade a partitioned table if a foreign key refers to the partitioned table.
 -   If you are upgrading from the version 9.4 server or a lower version of EDB Postgres Advanced Server, and you use partitioned tables that include a `SUBPARTITION BY` clause, you must use `pg_dump` and `pg_restore` to upgrade an existing EDB Postgres Advanced Server installation to a later version of EDB Postgres Advanced Server. To upgrade, you must:
@@ -11,3 +12,4 @@ The following limitations apply to upgrading EDB Postgres Advanced Server:
     3.  Use `pg_upgrade` to upgrade the rest of the EDB Postgres Advanced Server database to a more recent version.
     4.  Use `pg_restore` to restore the subpartitioned table to the latest upgraded EDB Postgres Advanced Server database.
 -   If you perform an upgrade of the EDB Postgres Advanced Server installation, you must rebuild any hash-partitioned table on the upgraded server.
+-   If you are using an ODBC, JDBC, OCI, or .NET driver to connect to your database applications and upgrading to a new major version of EDB Postgres Advanced Server, upgrade your driver to the latest version when upgrading EDB Postgres Advanced Server.