diff --git a/content/influxdb/cloud-dedicated/query-data/troubleshoot-and-optimize/optimize-queries.md b/content/influxdb/cloud-dedicated/query-data/troubleshoot-and-optimize/optimize-queries.md
index 42eae2edc..5a297bd9a 100644
--- a/content/influxdb/cloud-dedicated/query-data/troubleshoot-and-optimize/optimize-queries.md
+++ b/content/influxdb/cloud-dedicated/query-data/troubleshoot-and-optimize/optimize-queries.md
@@ -61,11 +61,13 @@ and learn how to [analyze a query plan](/influxdb/cloud-dedicated/query-data/tro
 
 #### Include a WHERE clause
 
-InfluxDB v3 stores data in a Parquet file for each measurement and day, and
-retrieves files from the Object store to answer a query.
+InfluxDB v3 stores data in a Parquet file for each partition.
+By default, {{< product-name >}} partitions tables by day, but you can also
+[custom-partition your data](/influxdb/cloud-dedicated/admin/custom-partitions/).
+At query time, InfluxDB retrieves files from the Object store to answer a query.
 To reduce the number of files that a query needs to retrieve from the Object store,
 include a [`WHERE` clause](/influxdb/cloud-dedicated/reference/sql/where/) that
-filters data by a time range.
+filters data by a time range or by specific tag values.
 
 #### SELECT only columns you need 
 
diff --git a/content/influxdb/cloud-dedicated/write-data/best-practices/schema-design.md b/content/influxdb/cloud-dedicated/write-data/best-practices/schema-design.md
index 0cf84c8dd..3455ffae5 100644
--- a/content/influxdb/cloud-dedicated/write-data/best-practices/schema-design.md
+++ b/content/influxdb/cloud-dedicated/write-data/best-practices/schema-design.md
@@ -129,7 +129,7 @@ Each row must include a time column.
 As a result, a table can have the following:
 
 - a time column
-- field and tag columns up to the configured maximum.
+- field and tag columns up to the configured maximum
 
 If you attempt to write to a table and exceed the column limit, then the write
 request fails and InfluxDB returns an error.
diff --git a/content/influxdb/cloud-serverless/write-data/best-practices/schema-design.md b/content/influxdb/cloud-serverless/write-data/best-practices/schema-design.md
index c7499c672..ec7525344 100644
--- a/content/influxdb/cloud-serverless/write-data/best-practices/schema-design.md
+++ b/content/influxdb/cloud-serverless/write-data/best-practices/schema-design.md
@@ -109,7 +109,7 @@ Each row must include a time column.
 As a result, a measurement can have the following:
 
 - a time column
-- field and tag columns up to the maximum number of columns.
+- field and tag columns up to the maximum number of columns
 
 If you attempt to write to a measurement and exceed the column limit, then the write
 request fails and InfluxDB returns an error.
diff --git a/content/influxdb/clustered/query-data/troubleshoot-and-optimize/optimize-queries.md b/content/influxdb/clustered/query-data/troubleshoot-and-optimize/optimize-queries.md
index 90724a553..b7751578e 100644
--- a/content/influxdb/clustered/query-data/troubleshoot-and-optimize/optimize-queries.md
+++ b/content/influxdb/clustered/query-data/troubleshoot-and-optimize/optimize-queries.md
@@ -61,11 +61,13 @@ and learn how to [analyze a query plan](/influxdb/clustered/query-data/troublesh
 
 #### Include a WHERE clause
 
-InfluxDB v3 stores data in a Parquet file for each measurement and day, and
-retrieves files from the Object store to answer a query.
+InfluxDB v3 stores data in a Parquet file for each partition.
+By default, {{< product-name >}} partitions tables by day, but you can also
+[custom-partition your data](/influxdb/clustered/admin/custom-partitions/).
+At query time, InfluxDB retrieves files from the Object store to answer a query.
 To reduce the number of files that a query needs to retrieve from the Object store,
 include a [`WHERE` clause](/influxdb/clustered/reference/sql/where/) that
-filters data by a time range.
+filters data by a time range or by specific tag values.
 
 #### SELECT only columns you need 
 
diff --git a/content/influxdb/clustered/write-data/best-practices/schema-design.md b/content/influxdb/clustered/write-data/best-practices/schema-design.md
index cbfd9e972..1b08b0204 100644
--- a/content/influxdb/clustered/write-data/best-practices/schema-design.md
+++ b/content/influxdb/clustered/write-data/best-practices/schema-design.md
@@ -129,7 +129,7 @@ Each row must include a time column.
 As a result, a table can have the following:
 
 - a time column
-- field and tag columns up to the configured maximum.
+- field and tag columns up to the configured maximum
 
 If you attempt to write to a table and exceed the column limit, then the write
 request fails and InfluxDB returns an error.