update

Author: adela-bytebase

docs/change-database/plan.mdx

@@ -14,13 +14,13 @@ Choose one or moretarget databases and click **Confirm**.
 
 ### 3. Add Changes
 
-Add SQL statements (multiple allowed by clicking **+ Add Change**) and click **Create**. The plan becomes an issue with automatic SQL review.
+Add SQL statements (multiple allowed by clicking **+ Add Change**) and click **Create**. The plan will be in `Draft` status with automatic SQL review.
 
 ![bb-plan-warning-detail](/content/docs/change-database/plan/bb-plan-warning-detail.webp)
 
 ### 4. Submit for Review (Enterprise)
 
-Fix the warning, and click **Ready for Review**. Approval follows [configured rules](/change-database/approval).
+Fix the warning, and click **Ready for Review**. The plan will be converted into an issue and await approval. Approval follows [configured rules](/change-database/approval).
 
 ![plan-approval](/content/docs/change-database/plan/bb-plan-approval.webp)
 

docs/tutorials/sql-review-gui.mdx

@@ -46,12 +46,6 @@ Make sure you have [Docker](https://www.docker.com/) installed, and if you don
 
 1. Go to `Sample Project`, navigate to **CI/CD** > **Plans** and click **+ New Plan**.
 
-   ![new-plan](/content/docs/change-database/plan/bb-new-plan.webp)
-
-1. Select **Schema Migration (DDL)** as the change type.
-
-   ![plan-change-type](/content/docs/change-database/plan/bb-plan-change-type.webp)
-
 1. Select `hr_prod` database as the target since the default SQL Review policy is attached to the `Prod` environment. Click **Confirm** to proceed. You can use the **Schema Editor** to visually design the schema, here we'll intentionally uncheck **Not Null** for `nickname` column.
 
 1. The plan will be in `Draft` status. SQL Review will run automatically, and you'll see violations against our defined rules marked in orange as `warning`.