From 6db8b0aad4e69b0eb67fad91dcd2aade94cb3f7d Mon Sep 17 00:00:00 2001
From: DrJRMyers <89800750+DrJRMyers@users.noreply.github.com>
Date: Wed, 15 Sep 2021 16:18:38 -0400
Subject: [PATCH] Update resolve-high-cardinality.md (#3130)

Fixed a typo for clarity
---
 .../v2.0/write-data/best-practices/resolve-high-cardinality.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/influxdb/v2.0/write-data/best-practices/resolve-high-cardinality.md b/content/influxdb/v2.0/write-data/best-practices/resolve-high-cardinality.md
index dfc0f56b6..c073ee0a6 100644
--- a/content/influxdb/v2.0/write-data/best-practices/resolve-high-cardinality.md
+++ b/content/influxdb/v2.0/write-data/best-practices/resolve-high-cardinality.md
@@ -87,7 +87,7 @@ These queries should help to identify the sources of high cardinality in each of
 Usually, resolving high cardinality is as simple as changing a tag with many unique values to a field. Review the following potential solutions for resolving high cardinality:
 
 - Delete data to reduce high cardinality
-- Design schema or read performance
+- Design schema for read performance
 
 ### Delete data to reduce high cardinality