chore: standardize Rollback terminology in documentation

content/blog/database-version-control.md

@@ -45,7 +45,7 @@ Database version control often relies on migration scripts, which are code files
 
 By keeping a history of changes, version control enables controlled deployment of database updates. If a problem occurs, it allows teams to roll back to a previous version of the database schema and associated data. Bytebase provides the following rollback options:
 
-- Data rollback. Using undo logs like MySQL binlog to roll back data changes.
+- Data rollback. Using undo logs like MySQL binlog to revert data changes.
 - Restore from backup and Point-in-time-Recovery (PITR). You can instruct Bytebase to take manual or periodic backups and restore from them.
 - Schema synchronization. You can synchronize one database schema to another. Bytebase can calculate the difference and apply the change.
 

mintlify/change-database/change-history.mdx

@@ -14,6 +14,6 @@ The history is listed under the database page
 
 ## Rollback schema
 
-You can also select a DDL and Baseline history version and roll back to that version.
+You can also select a DDL and Baseline history version and rollback to that version.
 
 ![version-rollback](/content/docs/change-database/change-workflow/version-rollback.webp)

mintlify/change-database/rollback-schema-changes.mdx

@@ -2,7 +2,7 @@
 title: Schema Rollback
 ---
 
-Bytebase records the history for each schema change. To roll back a schema change:
+Bytebase records the history for each schema change. To rollback a schema change:
 
 - You can use
   [Schema Synchronization](/change-database/synchronize-schema) to synchronize the database to a

mintlify/docs.json

@@ -123,7 +123,7 @@
                 ]
               },
               {
-                "group": "Roll back",
+                "group": "Rollback",
                 "pages": [
                   "change-database/rollback-data-changes",
                   "change-database/rollback-schema-changes"

mintlify/tutorials/how-to-synchronize-database-schemas.mdx

@@ -85,7 +85,7 @@ Use this for:
 
 ## Case 3 - Rollback to previous schema versions
 
-Use schema synchronization to roll back databases to any previous version from their migration history.
+Use schema synchronization to rollback databases to any previous version from their migration history.
 
 1. Navigate to **Sync Schema** and select `hr_test` as the source database.
 
@@ -106,7 +106,7 @@ You've learned how to:
 
 - Synchronize schemas to new databases
 - Propagate changes across multiple environments
-- Roll back to previous schema versions
+- Rollback to previous schema versions
 
 ## Next steps