diff --git a/docs/consensus-commit.mdx b/docs/consensus-commit.mdx
index 6e88aedd..d61d31fb 100644
--- a/docs/consensus-commit.mdx
+++ b/docs/consensus-commit.mdx
@@ -29,7 +29,7 @@ Pessimistic concurrency control (PCC), on the other hand, assumes conflicts are
 The OCC protocol of ScalarDB has three phases, as the commonly used OCC protocols, each of which does the following:
 
 * Read phase:
-  * ScalarDB tracks the read and write sets of transactions. ScalarDB copies every record that a transaction accesses from databases to its local workspace and stores its writes in the workspace.
+  * ScalarDB tracks the read and write sets of transactions. ScalarDB copies every record that a transaction accesses from databases to its local workspace and stores its writes in the local workspace.
 * Validation phase:
   * ScalarDB checks if the committing transaction conflicts with other transactions. ScalarDB uses backward validation; it goes to the write phase only if other transactions have not written what the transaction reads and writes, which are called read validation and write validation, respectively.
 * Write phase:
@@ -216,7 +216,7 @@ If you take backups from multiple databases or from non-transactional databases,
 
 In the current implementation, ScalarDB throws an exception in the following cases:
 
-* Executing scan operations after write (Put, Insert, Update, Upsert) operations for the same record in a transaction.
+* Executing scan operations after write (Put, Insert, Update, Upsert, Delete) operations for the same record in a transaction.
 * Executing write (Put, Insert, Update, and Upsert) operations after Delete operations for the same record in a transaction.
 
 ## See also
diff --git a/docs/roadmap.mdx b/docs/roadmap.mdx
index 7646ca94..b195d884 100644
--- a/docs/roadmap.mdx
+++ b/docs/roadmap.mdx
@@ -121,7 +121,7 @@ If you have a feature request or want to prioritize feature development, please
 
 ### CY2026
 
-- ** Audit Logging**
+- **Audit logging**
     - Users will be able to view and manage the access logs of ScalarDB Cluster and Analytics, mainly for auditing purposes.
 - **Stored procedures**
     - Users will be able to define stored procedures so that they can execute a set of operations with a complex logic inside ScalarDB Cluster.
@@ -130,6 +130,6 @@ If you have a feature request or want to prioritize feature development, please
 - **User-defined functions (UDFs)**
     - Users will be able to define functions so that they can use functions in SQLs to express complex logic in a simpler way.
 - **Addition of SQL operations for sorting**
-    - Users will be able to issue sorting (ORDER BY) operations in ScalarDB SQL.
+    - Users will be able to issue arbitrary sorting (ORDER BY) operations in ScalarDB SQL for multiple or non-JDBC databases. (Currently, ScalarDB can issue sorting operations using clustering keys or arbitrary sorting operations for single JDBC databases.)
 - **Addition of more data types**
     - Users will be able to use complex data types, such as JSON.
\ No newline at end of file