diff --git a/assets/js/search-data.json b/assets/js/search-data.json
index 85c83af..934d1c3 100644
--- a/assets/js/search-data.json
+++ b/assets/js/search-data.json
@@ -141,7 +141,7 @@
   },"20": {
     "doc": "CLI Reference",
     "title": "Command Reference",
-    "content": "Options . -c, --config <FILE> Config file to use -h, --help Print help -V, --version Print version . Usage . lakefs-databricks [OPTIONS] <COMMAND> . Commands . catalog create . Create a versioned catalog . Options . --force Force creation of the catalog even if it already exists. If specified, the lakeFS repository will be re-associated with the provided Unity catalog. This may have undesired effects. --sample-catalog Add sample data to the created catalog . Usage . lakefs-databricks catalog create [OPTIONS] <CATALOG_NAME> <LAKEFS_REPO_NAME> . Examples . Create a catalog named “my_catalog” mapped to the LakeFS repository “my-repo”: . lakefs-databricks catalog create my_catalog my-repo . Force-create the same catalog, with sample data: . lakefs-databricks catalog create --force --sample-catalog my_catalog my-repo . branch create . Create a branch . Usage . lakefs-databricks branch create <CATALOG_NAME> <BRANCH_NAME> <SOURCE_BRANCH_NAME> . Examples . Create a branch called “my-branch” from the source branch “main”, on the catalog “my_catalog”: . lakefs-databricks branch create my_catalog my-branch main . commit . Record catalog changes . Options . -m, --message <MESSAGE> Commit message . Usage . lakefs-databricks commit [OPTIONS] <CATALOG_NAME> <BRANCH_ID> . Examples . Commit the changes on branch “my-branch” and catalog “my_catalog”, with commit message “Changes”: . lakefs-databricks commit -m \"Changes\" my_catalog my-branch . import . Import table from an existing Unity catalog or from a lakeFS Delta table . Options . -f, --from <FROM_TABLE_PATH> Unity table to import: <CATALOG>.<SCHEMA>.<TABLE> Or lakeFS Delta table to import: lakefs://<REPO>/<BRANCH>/<PATH_TO_TABLE> -t, --to <TO_TABLE_PATH> lakeFS Databricks Unity table to generate: <CATALOG>.<SCHEMA>.<TABLE> -h, --help Print help . Usage . lakefs-databricks import --from <FROM_TABLE_PATH> --to <TO_TABLE_PATH> . Examples . Import table “my_table” from catalog and schema “src_catalog” and “src_schema” to catalog and schema “dst-catalog” and “main”: . lakefs-databricks import --from src_catalog.src_schema.my_table --to dst_catalog.main.my_table . Import table “my_lakefs_table” from lakeFS repository and branch “existing_repo” and “main” to a table named “my_table” in catalog and schema “dst_catalog” and “main”: . lakefs-databricks import --from lakefs://existing_repo/main/_tables/my_lakefs_table --to dst_catalog.main.my_table . ",
+    "content": "Options . -c, --config <FILE> Config file to use -h, --help Print help -V, --version Print version . Usage . lakefs-databricks [OPTIONS] <COMMAND> . Commands . catalog create . Create a versioned catalog . Options . --force Force creation of the catalog even if it already exists. If specified, the lakeFS repository will be re-associated with the provided Unity catalog. This may have undesired effects. --sample-catalog Add sample data to the created catalog . Usage . lakefs-databricks catalog create [OPTIONS] <CATALOG_NAME> <LAKEFS_REPO_NAME> . Examples . Create a catalog named “my_catalog” mapped to the LakeFS repository “my-repo”: . lakefs-databricks catalog create my_catalog my-repo . Force-create the same catalog, with sample data: . lakefs-databricks catalog create --force --sample-catalog my_catalog my-repo . branch create . Create a branch . Usage . lakefs-databricks branch create <CATALOG_NAME> <BRANCH_NAME> <SOURCE_BRANCH_NAME> . Examples . Create a branch called “my-branch” from the source branch “main”, on the catalog “my_catalog”: . lakefs-databricks branch create my_catalog my-branch main . commit . Record catalog changes . Options . -m, --message <MESSAGE> Commit message . Usage . lakefs-databricks commit [OPTIONS] <CATALOG_NAME> <BRANCH_ID> . Examples . Commit the changes on branch “my-branch” and catalog “my_catalog”, with commit message “Changes”: . lakefs-databricks commit -m \"Changes\" my_catalog my-branch . import . Import table from an existing Unity catalog or from a lakeFS Delta table . Options . -f, --from <FROM_TABLE_PATH> Unity table to import: <CATALOG>.<SCHEMA>.<TABLE> Or lakeFS table to import: lakefs://<REPO>/<BRANCH>/<PATH_TO_TABLE> -t, --to <TO_TABLE_PATH> lakeFS Databricks Unity table to generate: <CATALOG>.<SCHEMA>.<TABLE> -h, --help Print help . Usage . lakefs-databricks import --from <FROM_TABLE_PATH> --to <TO_TABLE_PATH> . Examples . Import table “my_table” from catalog and schema “src_catalog” and “src_schema” to catalog and schema “dst-catalog” and “main”: . lakefs-databricks import --from src_catalog.src_schema.my_table --to dst_catalog.main.my_table . Import table “my_lakefs_table” from lakeFS repository and branch “existing_repo” and “main” to a table named “my_table” in catalog and schema “dst_catalog” and “main”: . lakefs-databricks import --from lakefs://existing_repo/main/_tables/my_lakefs_table --to dst_catalog.main.my_table . ",
     "url": "/cli-reference.html#command-reference",
     
     "relUrl": "/cli-reference.html#command-reference"
diff --git a/cli-reference.html b/cli-reference.html
index ea081b7..7dec394 100644
--- a/cli-reference.html
+++ b/cli-reference.html
@@ -679,7 +679,7 @@ <h4 id="import">
 
 <p><strong>Options</strong></p>
 <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>-f, --from &lt;FROM_TABLE_PATH&gt;  Unity table to import: &lt;CATALOG&gt;.&lt;SCHEMA&gt;.&lt;TABLE&gt;
-                              Or lakeFS Delta table to import: lakefs://&lt;REPO&gt;/&lt;BRANCH&gt;/&lt;PATH_TO_TABLE&gt;
+                              Or lakeFS table to import: lakefs://&lt;REPO&gt;/&lt;BRANCH&gt;/&lt;PATH_TO_TABLE&gt;
 -t, --to &lt;TO_TABLE_PATH&gt;      lakeFS Databricks Unity table to generate: &lt;CATALOG&gt;.&lt;SCHEMA&gt;.&lt;TABLE&gt;
 -h, --help                    Print help
 </code></pre></div></div>