diff --git a/versioned_docs/version-3.14/overview.mdx b/versioned_docs/version-3.14/overview.mdx
index f999b409..e7a2532e 100644
--- a/versioned_docs/version-3.14/overview.mdx
+++ b/versioned_docs/version-3.14/overview.mdx
@@ -12,13 +12,13 @@ This page describes what ScalarDB is and its primary use cases.
 
 ## What is ScalarDB?
 
-ScalarDB is a hybrid transaction/analytical processing (HTAP) engine for diverse databases. It runs as middleware on databases and virtually unifies diverse databases by achieving ACID transactions and real-time analytics across them to simplify the complexity of managing multiple databases or multiple instances of a single database.
+ScalarDB is a universal hybrid transaction/analytical processing (HTAP) engine for diverse databases. It runs as middleware on databases and virtually unifies diverse databases by achieving ACID transactions and real-time analytics across them to simplify the complexity of managing multiple databases or multiple instances of a single database.
 
 ![How ScalarDB simplifies complex data management architecture.](images/scalardb.png)
 
 As a versatile solution, ScalarDB supports a range of databases, including:
 
-- Relational databases that support JDBC, such as MariaDB, Microsoft SQL Server, MySQL, Oracle Database, PostgreSQL, SQLite, and their compatible databases, like Amazon Aurora, Google AlloyDB, TiDB, and YugabyteDB.
+- Relational databases that support JDBC, such as MariaDB, Microsoft SQL Server, MySQL, Oracle Database, PostgreSQL, SQLite, and their compatible databases, like Amazon Aurora and YugabyteDB.
 - NoSQL databases like Amazon DynamoDB, Apache Cassandra, and Azure Cosmos DB.
 
 For details on which databases ScalarDB supports, refer to [Databases](requirements.mdx#databases).
diff --git a/versioned_docs/version-3.14/schema-loader.mdx b/versioned_docs/version-3.14/schema-loader.mdx
index 2a6e78da..aca76e1a 100644
--- a/versioned_docs/version-3.14/schema-loader.mdx
+++ b/versioned_docs/version-3.14/schema-loader.mdx
@@ -532,15 +532,15 @@ Auto-scaling for Cosmos DB for NoSQL is enabled only when this option is set to
 
 The following table shows the supported data types in ScalarDB and their mapping to the data types of other databases.
 
-| ScalarDB  | Cassandra | Cosmos DB for NoSQL | DynamoDB | MySQL    | PostgreSQL/YugabyteDB | Oracle         | SQL Server      | SQLite  |
-|-----------|-----------|---------------------|----------|----------|-----------------------|----------------|-----------------|---------|
-| BOOLEAN   | boolean   | boolean (JSON)      | BOOL     | boolean  | boolean               | number(1)      | bit             | boolean |
-| INT       | int       | number (JSON)       | N        | int      | int                   | number(10)     | int             | int     |
-| BIGINT    | bigint    | number (JSON)       | N        | bigint   | bigint                | number(19)     | bigint          | bigint  |
-| FLOAT     | float     | number (JSON)       | N        | real     | real                  | binary_float   | float(24)       | float   |
-| DOUBLE    | double    | number (JSON)       | N        | double   | double precision      | binary_double  | float           | double  |
-| TEXT      | text      | string (JSON)       | S        | longtext | text                  | varchar2(4000) | varchar(8000)   | text    |
-| BLOB      | blob      | string (JSON)       | B        | longblob | bytea                 | RAW(2000)      | varbinary(8000) | blob    |
+| ScalarDB | Cassandra | Cosmos DB for NoSQL | DynamoDB | MySQL/MariaDB | PostgreSQL/YugabyteDB | Oracle         | SQL Server      | SQLite  |
+|----------|-----------|---------------------|----------|---------------|-----------------------|----------------|-----------------|---------|
+| BOOLEAN  | boolean   | boolean (JSON)      | BOOL     | boolean       | boolean               | number(1)      | bit             | boolean |
+| INT      | int       | number (JSON)       | N        | int           | int                   | number(10)     | int             | int     |
+| BIGINT   | bigint    | number (JSON)       | N        | bigint        | bigint                | number(16)     | bigint          | bigint  |
+| FLOAT    | float     | number (JSON)       | N        | real          | real                  | binary_float   | float(24)       | float   |
+| DOUBLE   | double    | number (JSON)       | N        | double        | double precision      | binary_double  | float           | double  |
+| TEXT     | text      | string (JSON)       | S        | longtext      | text                  | varchar2(4000) | varchar(8000)   | text    |
+| BLOB     | blob      | string (JSON)       | B        | longblob      | bytea                 | RAW(2000)      | varbinary(8000) | blob    |
 
 However, the following data types in JDBC databases are converted differently when they are used as a primary key or a secondary index key. This is due to the limitations of RDB data types. For MySQL and Oracle, you can change the column size (minimum 64 bytes) as long as it meets the limitation of the total size of key columns. For details, see [Underlying storage or database configurations](configurations.mdx#underlying-storage-or-database-configurations).