remove unneeded comment that was breaking the build

turbot · Dec 7, 2024 · c7a579c · c7a579c
1 parent d3a1085
commit c7a579c
Showing 1 changed file with 1 addition and 5 deletions.
diff --git a/docs/manage/workspaces.md b/docs/manage/workspaces.md
@@ -11,13 +11,9 @@ Each workspace comprises:
 
 - A single local workspace directory for Tailpipe data (parquet) and metadata files
 
-<!--
-- Optionally, a single remote object store for synchronizing tailpipe data (parquet) and metadata
--->
-
 - Optionally, context-specific settings and options
 
-You can use **workspaces** to keep independent sets of data. <!-- and sync them with independent remote libraries in S3 -->.  Tailpipe workspaces enable you to define multiple named configurations and easily switch among them using the `--workspace` argument or `TAILPIPE_WORKSPACE` environment variable.  If there is no `--workspace` argument or `TAILPIPE_WORKSPACE` environment variable, then the `default` workspace will be used.
+You can use **workspaces** to keep independent sets of data. Tailpipe workspaces enable you to define multiple named configurations and easily switch among them using the `--workspace` argument or `TAILPIPE_WORKSPACE` environment variable.  If there is no `--workspace` argument or `TAILPIPE_WORKSPACE` environment variable, then the `default` workspace will be used.
 
 Workspace configurations can be defined in any `.tpc` file in the `~/.tailpipe/config` directory, but by convention they are defined in `~/.tailpipe/config/workspaces.tpc` file. This file may contain multiple workspace definitions that can then be referenced by name.