diff --git a/content/influxdb/cloud-dedicated/admin/custom-partitions/_index.md b/content/influxdb/cloud-dedicated/admin/custom-partitions/_index.md
index 10cd92f68..b609d0118 100644
--- a/content/influxdb/cloud-dedicated/admin/custom-partitions/_index.md
+++ b/content/influxdb/cloud-dedicated/admin/custom-partitions/_index.md
@@ -36,7 +36,7 @@ you can define a custom partitioning strategy by specifying tag values and diffe
 > Consider custom partitioning if:
 > 
 > 1. You have taken steps to [optimize your queries](/influxdb/cloud-dedicated/query-data/troubleshoot-and-optimize/optimize-queries/), and
-> 2. Performance for _single series queries_ (returns data with a specific tag value or tag set) is still unsatisfactory. 
+> 2. Performance for _single-series queries_ (querying for a specific [tag value](/influxdb/cloud-dedicated/reference/glossary/#tag-value) or [tag set](/influxdb/cloud-dedicated/reference/glossary/#tag-set)) is still unsatisfactory. 
 > 
 > Before choosing a partitioning strategy, weigh the [advantages](#advantages), [disadvantages](#disadvantages), and [limitations](#limitations) of custom partitioning.
 
diff --git a/content/influxdb/cloud-dedicated/reference/glossary.md b/content/influxdb/cloud-dedicated/reference/glossary.md
index f182ba9a6..8e9e84714 100644
--- a/content/influxdb/cloud-dedicated/reference/glossary.md
+++ b/content/influxdb/cloud-dedicated/reference/glossary.md
@@ -331,6 +331,7 @@ Related entries:
 [field](#field),
 [field key](#field-key),
 [field set](#field-set),
+[tag set](#tag-set),
 [tag value](#tag-value),
 [timestamp](#timestamp)