[release-v2.5] doc: broken links in config overrides (#4000)

Co-authored-by: Javier Molina Reyes <javiermolinar@live.com>
Co-authored-by: Kim Nylander <104772500+knylander-grafana@users.noreply.github.com>

Author: 3 people

docs/sources/tempo/api_docs/_index.md

@@ -480,7 +480,7 @@ Meant to be used in a Query Visualization UI like Grafana to test that the Tempo
 
 ### Overrides API
 
-For more information about user-configurable overrides API, refer to the [user-configurable overrides]{{< relref "../operations/user-configurable-overrides#api" >}} documentation.
+For more information about user-configurable overrides API, refer to the [user-configurable overrides]({{< relref "../operations/user-configurable-overrides#api" >}}) documentation.
 
 ### Flush
 

docs/sources/tempo/operations/user-configurable-overrides.md

@@ -39,7 +39,7 @@ Tempo regularly polls this bucket and keeps a copy of the limits in-memory. When
 
 ### Supported fields
 
-User-configurable overrides are designed to be a subset of the runtime overrides. Refer to [Overrides]{{< relref "../configuration#overrides" >}} for information about all overrides.
+User-configurable overrides are designed to be a subset of the runtime overrides. Refer to [Overrides]({{< relref "../configuration#overrides" >}}) for information about all overrides. 
 When a field is set in both the user-configurable overrides and the runtime overrides, the value from the user-configurable overrides will take priority.
 
 {{< admonition type="note" >}}