From 5cff735e02f7b092772e4e0e382be50ac7b9e1a1 Mon Sep 17 00:00:00 2001
From: Wei <15172118655@163.com>
Date: Mon, 13 Nov 2023 11:25:54 +0800
Subject: [PATCH] chore: metric-engine rfc format (#2735)

fix format
---
 docs/rfcs/2023-07-10-metric-engine.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/rfcs/2023-07-10-metric-engine.md b/docs/rfcs/2023-07-10-metric-engine.md
index 6ebd14759f5c..cf64295aa41f 100644
--- a/docs/rfcs/2023-07-10-metric-engine.md
+++ b/docs/rfcs/2023-07-10-metric-engine.md
@@ -50,10 +50,10 @@ The concept "Table" in GreptimeDB is a bit "heavy" compared to other time-series
 	```
 
 The following parts will describe these implementation details:
-    - How to route these metric region tables and how those table are distributed
-    - How to maintain the schema and other metadata of the underlying mito engine table
-    - How to maintain the schema of metric engine table
-    - How the query goes
+- How to route these metric region tables and how those table are distributed
+- How to maintain the schema and other metadata of the underlying mito engine table
+- How to maintain the schema of metric engine table
+- How the query goes
 
 ## Routing