From 0605fc54df6cd303b3148eb9f6230e9dd4b8528f Mon Sep 17 00:00:00 2001
From: Philipp Oppermann <dev@phil-opp.com>
Date: Tue, 19 Mar 2019 13:24:41 +0100
Subject: [PATCH] Move the ToC of Paging Implementation after the aside

---
 .../second-edition/posts/10-paging-implementation/index.md     | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/blog/content/second-edition/posts/10-paging-implementation/index.md b/blog/content/second-edition/posts/10-paging-implementation/index.md
index 7e2483f1..9ecbadcf 100644
--- a/blog/content/second-edition/posts/10-paging-implementation/index.md
+++ b/blog/content/second-edition/posts/10-paging-implementation/index.md
@@ -15,7 +15,6 @@ This blog is openly developed on [GitHub]. If you have any problems or questions
 [at the bottom]: #comments
 [post branch]: https://github.com/phil-opp/blog_os/tree/post-10
 
-<!-- toc -->
 
 <aside class="post_aside">
 
@@ -32,6 +31,8 @@ I hope that you enjoy this new post!
 
 </aside>
 
+<!-- toc -->
+
 ## Introduction
 
 The [previous post] gave an introduction to the concept of paging. It motivated paging by comparing it with segmentation, explained how paging and page tables work, and then introduced the 4-level page table design of `x86_64`. We found out that the bootloader already set up a page table hierarchy for our kernel, which means that our kernel already runs on virtual addresses. This improves safety since illegal memory accesses cause page fault exceptions instead of modifying arbitrary physical memory.