From 88ce757b3d383e19ba672c637db7b0f673e29bc4 Mon Sep 17 00:00:00 2001
From: Jon Udell <jon@jonudell.info>
Date: Wed, 29 Jan 2025 21:17:42 -0800
Subject: [PATCH] proofread

---
 docs/learn.md                                 | 21 +++--
 docs/manage/collection.md                     |  4 +-
 docs/manage/plugin.md                         | 17 ++--
 docs/manage/source.md                         |  2 -
 docs/pipes-ecosystem/index.md                 |  2 +-
 docs/reference/cli/compact.md                 |  4 +-
 docs/reference/cli/connect.md                 | 15 ++--
 docs/reference/cli/partition.md               | 84 +++++++++----------
 docs/reference/cli/plugin.md                  |  4 +-
 docs/reference/cli/query.md                   |  3 +-
 docs/reference/config-files/connection.md     |  4 +-
 docs/reference/config-files/partition.md      | 11 ++-
 .../env-vars/tailpipe_install_dir.md          |  7 +-
 docs/reference/env-vars/tailpipe_workspace.md |  2 +-
 docs/reference/glossary.md                    |  4 +-
 docs/sql/tips.md                              |  6 +-
 16 files changed, 86 insertions(+), 104 deletions(-)

diff --git a/docs/learn.md b/docs/learn.md
index bb55a38..d7930f6 100644
--- a/docs/learn.md
+++ b/docs/learn.md
@@ -69,8 +69,7 @@ Create a file, e.g. `~/.tailpipe/config/aws.tpc`, with a `connection` and `parti
 > ```hcl
 > partition "aws_cloudtrail_log" "flaws" {
 > source "file" {
->    paths       = ["/Users/dboeke/flaws/flaws_cloudtrail_logs"]
->    file_layout = "%{DATA}.json.gz"
+    paths       = ["/Users/dboeke/flaws/flaws_cloudtrail_logs"]
 >  }
 >}
 >```
@@ -84,21 +83,21 @@ tailpipe collect aws_cloudtrail_log
 ```
 
 
-Tailpipe will download the files from the source, decompress and parse them, and add the data to the Tailpipe database in the [standard hive file structure](/docs/reference/glossary#hive).
+Tailpipe will download the files from the source, decompress and parse them, and add the data to the Tailpipe database in the [standard hive file structure](/docs/manage/hive).
 
 ![](/learn/collection.png)
 
-To see the table that was created:
-
-```bash
-$ tailpipe table list
-NAME                  PLUGIN                                       LOCAL SIZE    FILES    ROWS
-aws_cloudtrail_log    hub.tailpipe.io/plugins/turbot/aws@latest    42 MB         2        160,581
-```
 
 ## Query your logs
 
-Tailpipe provides an interactive SQL shell for analyzing your collected data. Run `tailpipe query` to start the query shell.
+Tailpipe provides an interactive SQL shell for analyzing your collected data. Run `tailpipe query` to start the query shell. To see the table that was created:
+
+```bash
+$ tailpipe query
+> .inspect
+Table              Plugin          
+aws_cloudtrail_log aws@0.1.0
+```
 
 You can count the records in the table:
 
diff --git a/docs/manage/collection.md b/docs/manage/collection.md
index a69b07f..ba414e3 100644
--- a/docs/manage/collection.md
+++ b/docs/manage/collection.md
@@ -26,7 +26,7 @@ Collect a specific partition.
 tailpipe collect aws_cloudtrail_log.dev
 ```
 
-See [/docs/reference/cli/collect](/docs/reference/cli/collect) for more examples.
+See [collect](/docs/reference/cli/collect) for more examples.
 
 
 The collection process always writes to a local [workspace](/docs/manage/workspace), and does so on a per-partition basis.  While you may specify multiple partitions on the command line, `partition` is the unit of collection.
@@ -51,7 +51,7 @@ tailpipe collect aws_cloudtrail_log.test --from T-180d
 tailpipe collect aws_cloudtrail_log.test --from 2024-01-01
 ```
 
-- Subsequent collection runs occur chronologically resuming from the last collection by default, so there are no time gaps while the data is being collected.
+Subsequent collection runs occur chronologically resuming from the last collection by default, so there are no time gaps while the data is being collected.
 
 <!--
 - The data is available for querying even while partition collection is still occurring.
diff --git a/docs/manage/plugin.md b/docs/manage/plugin.md
index 09acaf7..d556dfb 100644
--- a/docs/manage/plugin.md
+++ b/docs/manage/plugin.md
@@ -19,8 +19,6 @@ This will download the latest aws plugin from the hub registry, and will set up
 > [!NOTE]
 > If you install multiple versions of a plugin only the first installation will create a connection automatically for you, you will need to create/edit a [connection](/docs/manage/connection) configuration file in order to use the additional versions of the plugin. 
 
-> ^ Will this apply to tailpipe?
-
 ## Installing a Specific Version
 
 To install a specific version, simply specify the version tag after the plugin name, separated by `@` or `:`
@@ -108,9 +106,6 @@ For example, consider a `myplugin` plugin that you have developed.  To install i
     }
     ```
 
-> [!WARNING]
-> ^ Keep? If so, change how?
-
 
 ## Installing Missing Plugins
 
@@ -134,15 +129,15 @@ tail
 ## Viewing Installed Plugins
 You can list the installed plugins with the `tailpipe plugin list` command:
 
-```
+```hcl
 $ tailpipe plugin list
 ┌─────────────────────────────────────────────────────┬─────────┬────────────────────────────────────────────┐
 │ NAME                                                │ VERSION │ CONNECTIONS                                │
 ├─────────────────────────────────────────────────────┼─────────┼────────────────────────────────────────────┤
-│ hub.tailpipe.io/plugins/turbot/aws@latest           │ 0.1.0   │ aws,aws_account_aaa,aws_account_aab         │
-│ hub.tailpipe.io/plugins/turbot/gcp@latest           │ 0.0.6   │ gcp_project_a,gcp,gcp_project_b             │
-│ hub.tailpipe.io/plugins/turbot/github@latest        │ 0.0.5   │ github                                      │
-└─────────────────────────────────────────────────────┴─────────┴─────────────────────────────────────────────┘
+│ hub.tailpipe.io/plugins/turbot/aws@latest           │ 0.1.0   │ aws,aws_account_aaa,aws_account_aab        │
+│ hub.tailpipe.io/plugins/turbot/gcp@latest           │ 0.0.6   │ gcp_project_a,gcp,gcp_project_b            │
+│ hub.tailpipe.io/plugins/turbot/github@latest        │ 0.0.5   │ github                                     │
+└─────────────────────────────────────────────────────┴─────────┴────────────────────────────────────────────┘
 ```
 
 ## Updating Plugins
@@ -192,7 +187,7 @@ $ tailpipe plugin list
 |                    NAME                    | VERSION | CONNECTIONS |
 +--------------------------------------------+---------+-------------+
 | hub.tailpipe.io/plugins/turbot/aws@latest  | 0.0.5   | aws         |
-    +--------------------------------------------+---------+-------------+
++--------------------------------------------+---------+-------------+
 ```
 
 ## Tailpipe Plugin Registry Support Lifecycle
diff --git a/docs/manage/source.md b/docs/manage/source.md
index 3807201..793ef53 100644
--- a/docs/manage/source.md
+++ b/docs/manage/source.md
@@ -27,12 +27,10 @@ partition "aws_cloudtrail_log" "test" {
   source "aws_s3_bucket" {
     connection    = connection.aws.logs
     bucket        = "my-logs-bucket"
-    file_layout   = "{%DATA}.json.gz"
   }
   
   source "file" {
     path       = "/path/to/files"
-    file_layout   = "{%DATA}.json.gz"
   }
 }
 ```
diff --git a/docs/pipes-ecosystem/index.md b/docs/pipes-ecosystem/index.md
index b331c1c..a41a820 100644
--- a/docs/pipes-ecosystem/index.md
+++ b/docs/pipes-ecosystem/index.md
@@ -10,6 +10,6 @@ Tailpipe is a part of a larger ecosystem of products that provide a flexible pla
 
 - [Steampipe](/docs/pipes-ecosystem/steampipe) provides a dynamic cloud inventory, allowing you to to query and analyze data from multiple sources via SQL.  Its plugin-based architecture ensures extensibility, enabling connections to APIs, cloud services, databases, and more.  
 
-- [Flowpipe](/docs/pipes-ecosystem/flowpipe) further enriches the platform with workflow orchestration.  Flowpipe allows you to create "pipelines as code" to define workflows and other tasks that run in a sequence.  With Flowpipe, you can turn your Steampipe and Tailpipe ;insights into into action!
+- [Flowpipe](/docs/pipes-ecosystem/flowpipe) further enriches the platform with workflow orchestration.  Flowpipe allows you to create "pipelines as code" to define workflows and other tasks that run in a sequence.  With Flowpipe, you can turn your Steampipe and Tailpipe insights into into action!
 
 - [Turbot Pipes](/docs/pipes-ecosystem/pipes) provides a hosted cloud intelligence, automation & security platform built specifically for DevOps. Pipes provides a managed Steampipe database instances, shared Powerpipe dashboards & snapshots, Flowpipe triggers & pipelines, and more!
\ No newline at end of file
diff --git a/docs/reference/cli/compact.md b/docs/reference/cli/compact.md
index 2c8a1b5..30c8183 100644
--- a/docs/reference/cli/compact.md
+++ b/docs/reference/cli/compact.md
@@ -2,10 +2,10 @@
 title: tailpipe compact
 ---
 
-Compact multiple Parquet files per day to one per day.
-
 # tailpipe compact
 
+Compact multiple Parquet files per day to one per day.
+
 ## Usage
 ```bash
  tailpipe compact [table] [table.partition] [args]
diff --git a/docs/reference/cli/connect.md b/docs/reference/cli/connect.md
index 1fbb4b3..a6b2274 100644
--- a/docs/reference/cli/connect.md
+++ b/docs/reference/cli/connect.md
@@ -53,6 +53,9 @@ Connect to the Tailpipe database, filtered to records after the start time:
 
 ```bash
 tailpipe connect --from 2025-01-01
+```
+
+```bash
 /home/jon/.tailpipe/data/default/tailpipe_20250115140447.db
 ```
 
@@ -61,19 +64,13 @@ tailpipe connect --from 2025-01-01
 > 
 > duckdb /home/jon/.tailpipe/data/default/tailpipe_20241212134120.db
 
-```bash
-tailpipe connect --from 2025-01-01
-/home/jon/.tailpipe/data/default/tailpipe_20250115140447.db
-```
+Connect with no filter, show output as json:
 
 ```bash
-tailpipe connect --from 2025-01-01
-/home/jon/.tailpipe/data/default/tailpipe_20250115140447.db
+tailpipe connect --output json
 ```
 
-Show the filepath for the connected database:
-
 ```bash
-tailpipe connect --output json
+{"database_filepath":"/Users/jonudell/.tailpipe/data/default/tailpipe_20250129204416.db"}
 ```
 
diff --git a/docs/reference/cli/partition.md b/docs/reference/cli/partition.md
index 4d22002..726a5cf 100644
--- a/docs/reference/cli/partition.md
+++ b/docs/reference/cli/partition.md
@@ -8,112 +8,112 @@ List, show, and delete Tailpipe partitions.
 
 ## Usage
 ```bash
-tailpipe partition delete table_name.partition_name [args]
 tailpipe partition list [args]
 tailpipe partition show table_name.partition_name [args]
+tailpipe partition delete table_name.partition_name [args]
 ```
 
 ## Sub-Commands
 
 | Command | Description
 |-|-
-| [delete](#tailpipe-partition-delete) | Delete a partition.
 | [list](#tailpipe-partition-list) | List all partitions.
 | [show](#tailpipe-partition-show)  | Show details of a partition.
+| [delete](#tailpipe-partition-delete) | Delete a partition.
 
-## tailpipe partition delete
-Delete a partition.
+
+## tailpipe partition list
+List all partitions.
 
 ### Arguments
 
 | Flag | Description
 |-|-
-|  `--force`     |  Force delete without confirmation
-|  `--from`      |  Specify the start time
-|  `--help`      |  Help for delete
+|  `--help`      |  Show help.
+|  `--output`    |  Output format: json, text (default)
+|  `--to`        |  Delete days older than than a relative or absolute date.
 
 ### Examples
 
-Delete an entire partition.
+List all partitions in table format.
 
 ```bash
-tailpipe partition delete aws_cloudtrail_log.dev
+tailpipe partition list
 ```
 
-Delete days newer than a relative date.
+List all partitions in `JSON` format. 
 
 ```bash
-tailpipe partition delete aws_cloudtrail_log.dev --from T-7d
+tailpipe partition list --output json
 ```
 
-Delete days newer than an absolute date with no confirmation.
+## tailpipe partition show
+Show details for a partition.
 
-```bash
-tailpipe partition delete aws_cloudtrail_log.dev --from 1/1/24 --force
-```
+Flag | Description
+|-|-
+|  `--help`      |  Show help.
+|  `--output`    |  Output format: json, text (default)
 
-Delete days older than a relative date.
+
+### Examples
+
+Show details in text format.
 
 ```bash
-tailpipe partition delete aws_cloudtrail_log.dev --to T-7d
+tailpipe partition show aws_cloudtrail-log.prod
 ```
 
-Delete days older than an absolute date.
+Show details in JSON format.
 
 ```bash
-tailpipe partition delete aws_cloudtrail_log.dev --to 1/1/24
+tailpipe partition show aws_cloudtrail-log.prod --output json
 ```
 
-## tailpipe partition list
-List all partitions.
+## tailpipe partition delete
+Delete a partition.
 
 ### Arguments
 
 | Flag | Description
 |-|-
-|  `--help`      |  Show help.
-|  `--output`    |  Output format: json, text (default)
-|  `--to`        |  Delete days older than than a relative or absolute date.
+|  `--force`     |  Force delete without confirmation
+|  `--from`      |  Specify the start time
+|  `--help`      |  Help for delete
 
 ### Examples
 
-List partitions in table format.
+Delete an entire partition.
 
 ```bash
-tailpipe partition list
+tailpipe partition delete aws_cloudtrail_log.dev
 ```
 
-List all partitions in `JSON` format. 
+Delete days newer than a relative date.
 
 ```bash
-tailpipe partition list --output json
+tailpipe partition delete aws_cloudtrail_log.dev --from T-7d
 ```
 
-## tailpipe partition show
-Show details for a partition.
-
-Flag | Description
-|-|-
-|  `--help`      |  Show help.
-|  `--output`    |  Output format: json, text (default)
-
+Delete days newer than an absolute date with no confirmation.
 
-### Examples
+```bash
+tailpipe partition delete aws_cloudtrail_log.dev --from 2024-01-01  --force
+```
 
-Show details in text format.
+Delete days older than a relative date.
 
 ```bash
-tailpipe partition show aws_cloudtrail-log.prod
+tailpipe partition delete aws_cloudtrail_log.dev --to T-7d
 ```
 
-Show details in JSON format.
+Delete days older than an absolute date.
 
 ```bash
-tailpipe partition show aws_cloudtrail-log.prod --output json
+tailpipe partition delete aws_cloudtrail_log.dev --to 2024-01-01
 ```
 
 
-
 ## Global Flags
 
 <table>
diff --git a/docs/reference/cli/plugin.md b/docs/reference/cli/plugin.md
index 6b6d9e6..17bec40 100644
--- a/docs/reference/cli/plugin.md
+++ b/docs/reference/cli/plugin.md
@@ -2,11 +2,9 @@
 title: tailpipe plugin
 ---
 
-
 # tailpipe plugin
-tailpipe plugin management
 
-Plugins extend tailpipe to work with many different services and providers. Find plugins using the public registry at [hub.tailpipe.io](https://hub.tailpipe.io).
+Tailpipe plugin management. Plugins extend tailpipe to work with many different services and providers. Find plugins using the public registry at [hub.tailpipe.io](https://hub.tailpipe.io).
 
 
 ## Usage
diff --git a/docs/reference/cli/query.md b/docs/reference/cli/query.md
index f9d7428..3d6cc46 100644
--- a/docs/reference/cli/query.md
+++ b/docs/reference/cli/query.md
@@ -4,7 +4,7 @@ title: tailpipe query
 
 # tailpipe query
 
-Query a Tailpipe table
+Query a Tailpipe table.
 
 ## Usage
 ```bash
@@ -119,7 +119,6 @@ Run the SQL command in the `my_queries/my_query.sql` file:
 tailpipe query my_queries/my_query.sql
 ```
 
-```
 Run a query and return output in CSV format:
 ```bash
 tailpipe query "select * from aws_cloudtrail_log limit 1000" --output csv
diff --git a/docs/reference/config-files/connection.md b/docs/reference/config-files/connection.md
index 90eb5c5..00af8c3 100644
--- a/docs/reference/config-files/connection.md
+++ b/docs/reference/config-files/connection.md
@@ -28,9 +28,9 @@ Each connection has a type label and a name. There is a type for each service: [
 
 ### Default connections
 
-Tailpipe also creates a single **implicit default** connection for each connection type. The connection is named `default`, eg `connection.aws.default`, `connection.azure.defaut`, etc. The intent of the default connection is that Tailpipe can "just work" with your existing setup, and is similar to the default connection that Steampipe creates for each plugin. For example, the AWS default connection will use the standard AWS SDK connection resolution mechanism to create a Tailpipe connection that will use the same connection that the `aws` CLI would use.
+Tailpipe also creates a single **implicit default** connection for each connection type. The connection is named `default`, eg `connection.aws.default`, `connection.azure.default`, etc. The intent of the default connection is that Tailpipe can "just work" with your existing setup, and is similar to the default connection that Steampipe creates for each plugin. For example, the AWS default connection will use the standard AWS SDK connection resolution mechanism to create a Tailpipe connection that will use the same connection that the `aws` CLI would use.
 
-You can override the default by simply creating a connection for that type that is named `default`:
+You can override the default by creating a connection for that type that is named `default`:
 
 ```hcl
 connection "aws" "default" {
diff --git a/docs/reference/config-files/partition.md b/docs/reference/config-files/partition.md
index 55f372e..b71e680 100644
--- a/docs/reference/config-files/partition.md
+++ b/docs/reference/config-files/partition.md
@@ -4,7 +4,7 @@ title:  partition
 
 # partition
 
-The `partition` block defines the set of log rows, in a plugin-defined Tailpipe table, that come from a specified `source`. A given Tailpipe table, like `aws_cloudtrail_log`, can include multiple partitions that use one or several `source` types. 
+The [partition](/docs/manage/partition) block defines the set of log rows, in a plugin-defined Tailpipe table, that come from a specified [source](/docs/manage/source). A given Tailpipe table, like `aws_cloudtrail_log`, can include multiple partitions that use one or several `source` types. 
 
 ## Examples
 
@@ -26,18 +26,17 @@ partition "aws_cloudtrail_log" "s3_bucket_us_east_1" {
   source "aws_s3_bucket" {
     connection = connection.aws.account_a
     bucket     = "aws-cloudtrail-logs-account-a"
-    file_layout   = "AWSLogs/%{NUMBER:account_id}/CloudTrail/us-east-1/%{YEAR:year}/%{MONTHNUM:month}/%{MONTHDAY:day}/%{NUMBER:prefix}_CloudTrail_%{DATA:region_file}_%{YEAR:year_file}%{MONTHNUM:month_file}%{MONTHDAY:day_file}T%{HOUR:hour}%{MINUTE:minute}Z_%{DATA:suffix}.json.gz"    
+    file_layout   = "AWSLogs/%{NUMBER:account_id}/CloudTrail/us-east-1/%{DATA}.json.gz"    
   }
 }
 ```
 
-Another `source` type, `file`, enables you to collect from local log files that you've downloaded. This partition collects one of the [flaws.cloud](https://flaws.cloud) files.
+Another `source` type, `file`, enables you to collect from local log files that you've downloaded. This partition collects the [flaws.cloud](https://flaws.cloud) files.
 
 ```hcl
-partition "aws_cloudtrail_log" "file00" {
+partition "aws_cloudtrail_log" "flaws" {
   source "file"  {
-  paths = ["~/tailpipe/flaws"]
-    file_layout = "flaws_cloudtrail00.json.gz"
+  paths       = ["/Users/dboeke/flaws/flaws_cloudtrail_logs"]    
   }
 }
 ```
diff --git a/docs/reference/env-vars/tailpipe_install_dir.md b/docs/reference/env-vars/tailpipe_install_dir.md
index 43e09e1..52a55a9 100644
--- a/docs/reference/env-vars/tailpipe_install_dir.md
+++ b/docs/reference/env-vars/tailpipe_install_dir.md
@@ -6,14 +6,11 @@ sidebar_label: TAILPIPE_INSTALL_DIR
 # TAILPIPE_INSTALL_DIR
 Sets the directory for the Tailpipe installation, in which the Tailpipe database, plugins, and supporting files can be found.
 
-Tailpipe is distributed as a single binary - when you install Tailpipe, either via `brew install` or via the `curl` script, the `tailpipe` binary is installed into your path.  The first time that you run Tailpipe, it will download and install the embedded database, foreign data wrapper extension, and other required files.   By default, these files are installed to `~/.tailpipe`, however you can change this location with the `TAILPIPE_INSTALL_DIR` environment variable or the `--install-dir` command line argument.
+Tailpipe is distributed as a single binary. When you install Tailpipe, either via `brew install` or via the `curl` script, the `tailpipe` binary is installed by default to `~/.tailpipe`, however you can change this location with the `TAILPIPE_INSTALL_DIR` environment variable or the `--install-dir` command line argument.
 
 Tailpipe will read the `TAILPIPE_INSTALL_DIR` variable each time it runs; if it's not set, Tailpipe will use the default path (`~/.tailpipe`). If you wish to **ALWAYS** run Tailpipe from the alternate path, you should set your environment variable in a way that will persist across sessions (in your `.profile` for example).
 
-To install a new Tailpipe instance into an alternate path, simply specify the path in `TAILPIPE_INSTALL_DIR` and then run a `tailpipe` command (alternatively, use the `--install-dir` argument).  If the specified directory is empty or files are missing, Tailpipe will install and update the database and files to `TAILPIPE_INSTALL_DIR`.  If the directory does not exist, Tailpipe will create it.  
-
-It is possible to have multiple, parallel tailpipe instances on a given machine using `TAILPIPE_INSTALL_DIR` as long as they are running on a different port.
-
+To install a new Tailpipe instance into an alternate path, simply specify the path in `TAILPIPE_INSTALL_DIR` and then run a `tailpipe` command (alternatively, use the `--install-dir` argument).  If the directory does not exist, Tailpipe will create it.  
 
 
 ## Usage 
diff --git a/docs/reference/env-vars/tailpipe_workspace.md b/docs/reference/env-vars/tailpipe_workspace.md
index d749241..ee99f3d 100644
--- a/docs/reference/env-vars/tailpipe_workspace.md
+++ b/docs/reference/env-vars/tailpipe_workspace.md
@@ -10,7 +10,7 @@ Sets the Tailpipe [workspace](/docs/reference/config-files/workspace).
 
 A Tailpipe `workspace` is a "profile" that allows you to define a unified environment that the Tailpipe client can interact with. 
 
-To learn more, see **[Managing Workspaces →](/docs/managing/workspaces)**
+To learn more, see [Managing Workspaces](/docs/manage/workspace).
 
 
 
diff --git a/docs/reference/glossary.md b/docs/reference/glossary.md
index 8f860e3..6b83113 100644
--- a/docs/reference/glossary.md
+++ b/docs/reference/glossary.md
@@ -26,7 +26,7 @@ A connection represents a reusable connection to a service. In a `.tpc` file, th
 
 ## Detection
 
-A detection is a Tailpipe query, optionally bundled into a benchmark, that is runs in the context of a mod. The detection's query looks for a specific pattern. In a Cloudtrail log, for example, an `UpdateTrail` event with a null `KmsKeyId` in its request parameters indicates the removal of a KMS key. The AWS detections mod includes `cloudtrail_logs_detect_cloudtrail_trails_with_encryption_disabled`, a detection that queries for this pattern and associates it with Mitre Attack `TA0005:T1562.001`.
+A detection is a Tailpipe query, optionally bundled into a benchmark, that runs in the context of a mod. The detection's query looks for a specific pattern. In a Cloudtrail log, for example, an `UpdateTrail` event with a null `KmsKeyId` in its request parameters indicates the removal of a KMS key. The AWS detections mod includes `cloudtrail_logs_detect_cloudtrail_trails_with_encryption_disabled`, a detection that queries for this pattern and associates it with MITRE ATT&CK `TA0005:T1562.001`.
 
 ## DuckDB
 
@@ -46,7 +46,7 @@ A Tailpipe mod provides the context for detections (usually organized into bench
 
 ## Source
 
-A plugin-defined mechanism for acquiring log data. When you configure a collection in a `.tpc` file, you use the `source` argument. Example values include `file` and `aws_s3_bucket`, which are generic ways to acquire log files (enhanced by plugin-specific configuration). A source like `pipes_audit_log` is an example of a plugin-specific mechanism to acquire log data via an API.
+A plugin-defined mechanism for acquiring log data. When you configure a collection in a `.tpc` file, you use the `source` argument. Example values include `file` and `aws_s3_bucket`, which are generic ways to acquire log files (enhanced by plugin-specific configuration). A source like [pipes_audit_log_api](https://hub-tailpipe.io/plugins/turbot/pipes/sources/pipes_audit_log_api) is an example of a plugin-specific mechanism to acquire log data via an API.
 
 ## Parquet
 
diff --git a/docs/sql/tips.md b/docs/sql/tips.md
index a191aae..09c9522 100644
--- a/docs/sql/tips.md
+++ b/docs/sql/tips.md
@@ -8,13 +8,13 @@ title: Tips and Tricks
 
 You can speed up a query by using a `where` or `join` clause to restrict the number of files Tailpipe will read to satisfy the query. This restriction operates at three levels.
 
-*Partition*. When a table defines more than one partition, you can filter to include only files belonging to other partitions.
+*Partition*. When a table defines more than one partition, you can filter to include only files belonging to that partition.
 
 ```sql
 select count(*) from aws_cloudtrail_log where partition = 'prod'
 ```
 
-*Index*. When a partition defines more than one index, you can filter to include  all files belonging to other indexes.
+*Index*. When a partition defines more than one index, you can filter to include  all files belonging to that index.
 
 ```sql
 select count(*) from aws_cloudtrail_log where partition = 'prod' and index = 123456789
@@ -26,7 +26,7 @@ select count(*) from aws_cloudtrail_log where partition = 'prod' and index = 123
 select count(*) from aws_cloudtrail_log where partition = 'prod' and index = 123456789 and tp_date = '2024-12-01'
 ```
 
-The [hive directory structure](docs/manage/hive) enables you to exclude large numbers of Parquet files.
+The [hive directory structure](/docs/manage/hive) enables you to exclude large numbers of Parquet files.
 
 ## Use common fields