refine doc

Author: luoyuxia

website/docs/maintenance/operations/updating-configs.md

@@ -32,16 +32,10 @@ admin.alterClusterConfigs(
                 new AlterConfig(DATALAKE_ENABLED.key(), "true", AlterConfigOpType.SET),
                 new AlterConfig(DATALAKE_FORMAT.key(), "paimon", AlterConfigOpType.SET)));
 
-// Pre-bind the lakehouse format without enabling lakehouse tables
-admin.alterClusterConfigs(
-        Arrays.asList(
-                new AlterConfig(DATALAKE_ENABLED.key(), "false", AlterConfigOpType.SET),
-                new AlterConfig(DATALAKE_FORMAT.key(), "paimon", AlterConfigOpType.SET)));
-
-// Return to legacy behavior where configuring datalake.format alone also enables lakehouse tables
+// Disable lakehouse storage
 admin.alterClusterConfigs(
         Collections.singletonList(
-                new AlterConfig(DATALAKE_ENABLED.key(), null, AlterConfigOpType.DELETE)));
+                new AlterConfig(DATALAKE_ENABLED.key(), "false", AlterConfigOpType.SET)));
 
 // Set RocksDB shared rate limiter to 200MB/sec
 admin.alterClusterConfigs(
@@ -54,8 +48,6 @@ The `AlterConfig` class contains three properties:
 * `value`: The configuration value to be set (e.g., `paimon`)
 * `opType`: The operation type, either `AlterConfigOpType.SET` or `AlterConfigOpType.DELETE`
 
-If `datalake.enabled` is explicitly configured, `datalake.format` must also be configured in the cluster.
-
 ### Using Flink Stored Procedures
 
 For certain configurations, Fluss provides convenient Flink stored procedures that can be called directly from Flink SQL. See [Procedures](engine-flink/procedures.md#cluster-configuration-procedures) for detailed documentation on using `get_cluster_config` and `set_cluster_config` procedures.

website/docs/maintenance/operations/upgrade-notes-0.10.md

@@ -5,35 +5,40 @@ sidebar_position: 4
 
 # Upgrade Notes from v0.9 to v0.10
 
-## New `datalake.enabled` Cluster Configuration
+## Cluster Configuration Changes
 
-Starting from v0.10, Fluss introduces the cluster-level configuration `datalake.enabled` to control whether the cluster is ready to create and manage lakehouse tables.
+### New `datalake.enabled` Cluster Configuration
 
-### Behavior Changes
+Starting in v0.10, Fluss introduces the cluster-level configuration `datalake.enabled` to control whether the cluster is ready to create and manage lakehouse tables.
 
-- If `datalake.enabled` is unset, Fluss keeps the legacy behavior: configuring `datalake.format` alone also enables lakehouse tables.
-- If `datalake.enabled = false`, Fluss only pre-binds the lake format for newly created tables and does not allow lakehouse tables yet.
+#### Behavior Changes
+
+- If `datalake.enabled` is unset, Fluss preserves the legacy behavior: configuring `datalake.format` alone also enables lakehouse tables.
+- If `datalake.enabled = false`, Fluss pre-binds the lake format for newly created tables but does not allow lakehouse tables yet.
 - If `datalake.enabled = true`, Fluss fully enables lakehouse tables.
 - If `datalake.enabled` is explicitly configured, `datalake.format` must also be configured.
 
-### Recommended Configuration
+#### Recommended Configuration
 
-If you want to enable lakehouse tables on the cluster, configure both options together:
+To enable lakehouse tables for the cluster, configure both options together:
 
 ```yaml
 datalake.enabled: true
 datalake.format: paimon
 ```
 
-If you only want to pre-bind the lake format without enabling lakehouse tables yet, configure:
+To pre-bind the lake format without enabling lakehouse tables yet, configure:
 
 ```yaml
 datalake.enabled: false
 datalake.format: paimon
 ```
 
-### Documentation Updates for Existing Deployments
+This mode is useful when you want newly created tables to carry the lake format in advance, while postponing lakehouse enablement at the cluster level.
+After `datalake.enabled` is later set to `true`, tables created under this configuration can still turn on `table.datalake.enabled` without being recreated.
+
+#### Notes for Existing Deployments
 
-If your existing deployment or internal scripts only set `datalake.format`, they will continue to work with the legacy behavior as long as `datalake.enabled` is left unset.
+If your existing deployment or internal scripts only set `datalake.format`, they will continue to work with the legacy behavior as long as `datalake.enabled` remains unset.
 
-However, for new configuration examples and operational guidance, prefer configuring `datalake.enabled` explicitly together with `datalake.format`.
+For new configuration examples and operational guidance, we recommend explicitly configuring `datalake.enabled` together with `datalake.format`.