diff --git a/_partials/_livesync-terminal.md b/_partials/_livesync-terminal.md
index a0aaf95edf..ef199d46b6 100644
--- a/_partials/_livesync-terminal.md
+++ b/_partials/_livesync-terminal.md
@@ -175,7 +175,7 @@ instance to a $SERVICE_LONG:
    As you run the $PG_CONNECTOR continuously, best practice is to run it as a Docker daemon.
 
    ```shell
-   docker run -d --rm --name livesync timescale/live-sync:v0.3.3 run \
+   docker run -d --rm --name livesync timescale/live-sync:v0.4.0 run \
       --publication <publication_name> --subscription <subscription_name> \
       --source $SOURCE --target $TARGET --table-map <table_map_as_json>
    ```
@@ -191,6 +191,11 @@ instance to a $SERVICE_LONG:
    `--table-map`: (Optional) A JSON string that maps source tables to target tables. If not provided, the source and target table names are assumed to be the same.
    For example, to map the source table `metrics` to the target table `metrics_data`:
 
+   `--table-sync-workers`: (Optional) The number of parallel workers to use for initial table sync. Default is 4.
+
+   `--copy-data`: (Optional) By default, the initial table data is copied from source to target before starting logical replication. Set to `false` so only changes made after replication slot creation are replicated.
+   Best practice is to set to `false` during dry-run livesync so you do not copy table data.
+
    ```
    --table-map '{"source": {"schema": "public", "table": "metrics"}, "target": {"schema": "public", "table": "metrics_data"}}'
    ```
@@ -325,7 +330,7 @@ EOF
    Use the `--drop` flag to remove the replication slots created by the $PG_CONNECTOR on the source database.
 
    ```shell
-   docker run -it --rm --name livesync timescale/live-sync:v0.3.3 run \
+   docker run -it --rm --name livesync timescale/live-sync:v0.4.0 run \
       --publication <publication_name> --subscription <subscription_name> \
       --source $SOURCE --target $TARGET \
       --drop