diff --git a/site/dump/posix/fsync-pitfalls.md b/site/dump/posix/fsync-pitfalls.md
index 7b30f59..0ecf2aa 100644
--- a/site/dump/posix/fsync-pitfalls.md
+++ b/site/dump/posix/fsync-pitfalls.md
@@ -41,8 +41,6 @@ This is a non-comprehensive list of the pitfalls of the `fsync` syscall.
 I will expand this list as I have more questions about all the questionable
 filesystems used and created by operating system enthusiasts.
 
----
-
 ## `fsync` does not ensure that a `fsync`'d file is visible in its parent directory
 
 From the manpage:
@@ -56,8 +54,6 @@ This means that that you cannot rely on a file being in the directory after
 
 Speaking about `fsync`ing a directory:
 
----
-
 ## `fsync` on a directory does not ensure children are `fsync`'d
 
 From the manpage: