docs: futher cleanup changelist

Author: tianzhou

mintlify/content/docs/tutorials/how-to-move-schema-change-from-test-to-prod/changelist-add-change.webp

@@ -1,6 +1,6 @@
 ---
 title: Onboarding Plan
-icon: "notebook-pen"
+icon: 'notebook-pen'
 ---
 
 <Note>
@@ -96,5 +96,4 @@ Related features (in addition to Phase 1):
 - [GitOps](/vcs-integration/overview/)
 - [Drift Detection](/change-database/drift-detection/)
 - [Batch Change](/change-database/batch-change/)
-- [Changelist](/changelist/)
 - [Online Schema Migration (MySQL only)](/change-database/online-schema-migration-for-mysql/)

mintlify/content/docs/tutorials/how-to-move-schema-change-from-test-to-prod/changelist-apply.webp

@@ -91,13 +91,11 @@ If you want **Time scheduling** feature, you will need to upgrade to **Pro Plan*
 
 If you want the approval flow to be more dynamic based on the context like the type of SQL statements, follow this tutorial [Database Change with Risk-Based Approval Flow](/tutorials/database-change-management-with-risk-adjusted-approval-flow/).
 
-
 ### Summary
 
 You have now learned how to use Bytebase to deploy schema migration in a basic way. Bytebase also provides other advanced features for your interests:
 
 - [GitOps](/vcs-integration/overview/) - Observe Git code push events and trigger schema migration;
 - [Batch changes](/change-database/batch-change/) - Change multiple databases in a single workflow;
-- [Changelist](/changelist/) - Organize and apply changes sequentially, or export them for offline execution.
 
 Join our [Discord channel](https://discord.com/invite/huyw7gRsyA) to discuss.

mintlify/content/docs/tutorials/how-to-move-schema-change-from-test-to-prod/changelist-details-page.webp

@@ -44,26 +44,7 @@ You can see how Bytebase shows the diff between the test database (source) and t
 
 Thus we have successfully propagate the change from `test` to `prod`.
 
-## Option 3: Changelist
-
-Still within `Basic Project` interface, enter [**Changelists**](/changelist/) section on the left-side bar, where you can create a **New Changelist**.
-
-![changelist-entry](/content/docs/tutorials/how-to-move-schema-change-from-test-to-prod/changelist-entry.webp)
-
-In the details page of our new changelist, besides **Upload .sql or .zip file**, we can also click the `+` to **Add Change**.
-
-![changelist-details-page](/content/docs/tutorials/how-to-move-schema-change-from-test-to-prod/changelist-details-page.webp)
-
-We can choose `Change History` as Change source to add our former schema changes to changelist. Or, we can edit **Raw SQL** to add any schema change to our changelist.
-
-![changelist-add-change](/content/docs/tutorials/how-to-move-schema-change-from-test-to-prod/changelist-add-change.webp)
-
-Having finished editing the new changelist, **Apply to database** where you choose both databases to **Edit Schema**. Then just create and deploy the issue as we did.
-
-![changelist-apply](/content/docs/tutorials/how-to-move-schema-change-from-test-to-prod/changelist-apply.webp)
-
 ## Related docs
 
 - [Streamlined Rollout](/change-database/batch-change/#change-databases-from-multiple-environments)
 - [Schema Synchronization](/change-database/synchronize-schema)
-- [Changelist](/changelist)