From 51e21083d2a6a9efb9c1591b04ad2f98442572d8 Mon Sep 17 00:00:00 2001
From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
Date: Mon, 2 Sep 2024 16:05:51 +0100
Subject: [PATCH] Update metricflow-time-spine.md (#6000)

fix file name position
---
 .../docs/docs/build/metricflow-time-spine.md  | 19 +++----------------
 1 file changed, 3 insertions(+), 16 deletions(-)

diff --git a/website/docs/docs/build/metricflow-time-spine.md b/website/docs/docs/build/metricflow-time-spine.md
index ec2d9bf1862..9730313d60d 100644
--- a/website/docs/docs/build/metricflow-time-spine.md
+++ b/website/docs/docs/build/metricflow-time-spine.md
@@ -47,9 +47,9 @@ The example creates a time spine at a daily grain and an hourly grain. A few thi
 * You can add a time spine for each granularity you intend to use if query efficiency is more important to you than configuration time, or storage constraints. For most engines, the query performance difference should be minimal and transforming your time spine to a coarser grain at query time shouldn't add significant overhead to your queries.
 * We recommend having a time spine at the finest grain used in any of your dimensions to avoid unexpected errors. i.e., if you have dimensions at an hourly grain, you should have a time spine at an hourly grain.
 
-<VersionBlock lastVersion="1.6">
+<File name="metricflow_time_spine.sql">
 
-<File name='time_spine_daily.sql'>
+<VersionBlock lastVersion="1.6">
 
 ```sql
 {{
@@ -80,14 +80,11 @@ select * from final
 where date_day > dateadd(year, -4, current_timestamp()) 
 and date_hour < dateadd(day, 30, current_timestamp())
 ```
-</File
 
 </VersionBlock>
 
 <VersionBlock firstVersion="1.7">
 
-<File name="metricflow_time_spine.sql">
-
 ```sql
 {{
     config(
@@ -116,15 +113,9 @@ select * from final
 where date_day > dateadd(year, -4, current_timestamp()) 
 and date_hour < dateadd(day, 30, current_timestamp())
 ```
-</File>
-
 </VersionBlock>
 
-</File>
-
 <VersionBlock lastVersion="1.6">
-
-<File name="metricflow_time_spine.sql">
   
 ```sql
 -- BigQuery supports DATE() instead of TO_DATE(). Use this model if you're using BigQuery
@@ -149,13 +140,10 @@ from final
 where date_day > dateadd(year, -4, current_timestamp()) 
 and date_hour < dateadd(day, 30, current_timestamp())
 ```
-</File>
 
 </VersionBlock>
 
 <VersionBlock firstVersion="1.7">
-
-<File name="metricflow_time_spine.sql">
   
 ```sql
 -- BigQuery supports DATE() instead of TO_DATE(). Use this model if you're using BigQuery
@@ -180,9 +168,8 @@ from final
 where date_day > dateadd(year, -4, current_timestamp()) 
 and date_hour < dateadd(day, 30, current_timestamp())
 ```
-</File>
-
 </VersionBlock>
+</File>
 
 ## Hourly time spine
 <File name='time_spine_hourly.sql'>