From 5ff020fac98fd06ee7de4b9d1b40b685dd91a15c Mon Sep 17 00:00:00 2001
From: Lars Wirzenius <liw@liw.fi>
Date: Sun, 5 Jan 2020 15:47:40 +0200
Subject: Change: code block markup

---
 blog/2020/01/05/data_files_for_tests.mdwn | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/blog/2020/01/05/data_files_for_tests.mdwn b/blog/2020/01/05/data_files_for_tests.mdwn
index 3885a4a..f786d26 100644
--- a/blog/2020/01/05/data_files_for_tests.mdwn
+++ b/blog/2020/01/05/data_files_for_tests.mdwn
@@ -35,8 +35,8 @@ all stakeholders.
 The syntax would look something like below, which is an example of a
 test data file containing a Subplot document.
 
-~~~~markdown
-~~~{.file .markdown numberLines}
+~~~~~~~~markdown
+~~~~~{.file .markdown numberLines}
 ---
 title: Test scenario
 bindings: b.yaml
@@ -51,8 +51,8 @@ given precondition foo
 when I do bar
 then bar was done
 ```
-~~~
-~~~~
+~~~~~
+~~~~~~~~
 
 Pandoc allows attributes to fenced code blocks. Above, we declare the
 block is a file, in markdown, and its lines should be numbered.
-- 
cgit v1.2.1