diff --git a/content/influxdb/v2.5/write-data/best-practices/schema-design.md b/content/influxdb/v2.5/write-data/best-practices/schema-design.md
index c43b7ac96..521306f8d 100644
--- a/content/influxdb/v2.5/write-data/best-practices/schema-design.md
+++ b/content/influxdb/v2.5/write-data/best-practices/schema-design.md
@@ -137,7 +137,7 @@ In addition to keeping your keys free of data, follow these additional guideline
 To simplify query writing, don't include reserved keywords or special characters in tag and field keys.
 If you use [Flux keywords](/{{< latest "flux" >}}/spec/lexical-elements/#keywords) in keys,
 then you'll have to wrap the keys in double quotes.
-If you use non-alphanumeric characters in keys, then you'll have to use [bracket notation](/{{< latest "flux" >}}/data-types/composite/record/#bracket-notation) in [Flux]((/{{< latest "flux" >}}/).
+If you use non-alphanumeric characters in keys, then you'll have to use [bracket notation](/{{< latest "flux" >}}/data-types/composite/record/#bracket-notation) in [Flux](/{{< latest "flux" >}}/).
 
 ##### Avoid duplicate names for tags and fields
 
@@ -249,4 +249,4 @@ from(bucket:"example-bucket")
 
 For an overview of the InfluxDB data model, watch the following video:
 
-{{< youtube 3qTTqsL27lI >}}
\ No newline at end of file
+{{< youtube 3qTTqsL27lI >}}