X-Git-Url: http://git.dujemihanovic.xyz/?a=blobdiff_plain;f=content%2Fposts%2Fwindows-backup%2Findex.md;fp=content%2Fposts%2Fwindows-backup%2Findex.md;h=d8020a7c45f09cbaf6955098bf58760dce79d5b0;hb=2418d7d31036b2a211d521b1313f8073bf8cf497;hp=e6ab8bba409efc34e888ec5f65ecbc0ef789404f;hpb=83710f57f69cce08f7eb726cb8c4a3c55f4819b7;p=dujemihanovic.xyz.git

diff --git a/content/posts/windows-backup/index.md b/content/posts/windows-backup/index.md
index e6ab8bb..d8020a7 100644
--- a/content/posts/windows-backup/index.md
+++ b/content/posts/windows-backup/index.md
@@ -2,7 +2,7 @@
 title: "Windows Backup fails with 0x81000037? Check your filesystem"
 date: 2023-08-17T17:58:49+02:00
 ---
-# The Problem
+## The Problem
 Yesterday, in preparation for a "downgrade" to Windows 10 from 11, I was trying
 to make a backup of my Windows files *(using the Windows 7 Backup and Restore
 control panel)*. Not long after it actually started copying the files, it spat
@@ -28,7 +28,7 @@ me that there are certain cache files that caused it to fail, so I deleted them
 and tried again. The backup again failed and I tried doing this a few more
 times, but as nothing helped I eventually gave up.
 
-# The Solution
+## The Solution
 Having been unable to fix Windows' backup utility, I decided to just copy the
 files to the backup drive and copy them over back after the "downgrade". This is
 when the actual solution to my problem becomes visible: Windows Explorer
@@ -49,7 +49,7 @@ running, then amazed by how fast and snappy Windows 10 is compared to its
 
 (I don't expect to get around to writing such post anytime soon though.)
 
-# *"Why are you writing about this?"*
+## *"Why are you writing about this?"*
 As you may know, Microsoft stuff is notorious for being not very well documented
 and it's entirely possible *(even if very unlikely)* that someone else encounters
 the same issue I have and is left helpless thanks to Windows' lack of a