From b2c29246afb28cacb97846adffcd476db95343ba Mon Sep 17 00:00:00 2001
From: William Sandner <wsandner@gmail.com>
Date: Fri, 24 Aug 2018 13:35:41 +0200
Subject: [PATCH] moved hr

---
 Test-Case-Format.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Test-Case-Format.md b/Test-Case-Format.md
index c606d48..c701309 100644
--- a/Test-Case-Format.md
+++ b/Test-Case-Format.md
@@ -15,10 +15,10 @@ The test cases should be written in enough detail that they could be
 given to a new team member who would be able to quickly start to carry
 out the tests and find defects.
 
-### unique-test-case-id: Test Case Title
-
 ---
 
+### unique-test-case-id: Test Case Title
+
 **Purpose:**
 
 ::Short sentence or two about the aspect of the system is being tested. If this gets too long, break the test case up or put more information into the feature descriptions.