From f43d8dadfd1a86403338ff6fe7faba23a09c6b2a Mon Sep 17 00:00:00 2001
From: Sooter Saalu <53571625+Soot3@users.noreply.github.com>
Date: Thu, 20 Mar 2025 08:35:43 +0100
Subject: [PATCH] Update naming.md

Fix broken bullet points rendering

Signed-off-by: Sooter Saalu <53571625+Soot3@users.noreply.github.com>
---
 content/docs/practices/naming.md | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/content/docs/practices/naming.md b/content/docs/practices/naming.md
index 12876a06..e7519543 100644
--- a/content/docs/practices/naming.md
+++ b/content/docs/practices/naming.md
@@ -43,9 +43,8 @@ A metric name...
   * <code>prometheus\_tsdb\_head\_truncations\_closed\_total</code>
   * <code>prometheus\_tsdb\_head\_truncations\_established\_total</code>
   * <code>prometheus\_tsdb\_head\_truncations\_failed\_total</code>
-  * <code>prometheus\_tsdb\_head\_truncations\_total</code>
-
-  The following examples are also valid, but are following a different trade-off. They are easier to read individually, but unrelated metrics like <code>prometheus\_tsdb\_head\_series</code> might get sorted in between.
+  * <code>prometheus\_tsdb\_head\_truncations\_total</code><br/>
+  The following examples are also valid, but are following a different trade-off. They are easier to read individually, but unrelated metrics like <code>prometheus\_tsdb\_head\_series</code> might get sorted in between.  
   * <code>prometheus\_tsdb\_head\_closed\_truncations\_total</code>
   * <code>prometheus\_tsdb\_head\_established\_truncations\_total</code>
   * <code>prometheus\_tsdb\_head\_failed\_truncations\_total</code>