From 75708f9d77315a94d2f933ea034f42e1e6f05633 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Timoth=C3=A9e=20Ravier?= <travier@redhat.com>
Date: Wed, 30 Sep 2020 18:11:03 +0200
Subject: [PATCH] docs: Move and update Background page

---
 docs/{manual => }/background.md | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)
 rename docs/{manual => }/background.md (95%)

diff --git a/docs/manual/background.md b/docs/background.md
similarity index 95%
rename from docs/manual/background.md
rename to docs/background.md
index a6372287..1fd67c17 100644
--- a/docs/manual/background.md
+++ b/docs/background.md
@@ -1,3 +1,13 @@
+---
+nav_order: 2
+---
+
+# Background
+{: .no_toc }
+
+1. TOC
+{:toc}
+
 ## Package systems versus image systems
 
 Broadly speaking, software update systems for operating systems tend
@@ -5,27 +15,27 @@ to fall cleanly into one of two camps: package-based or image-based.
 
 ### Package system benefits and drawbacks
 
-Benefits
+Benefits:
 
  * Highly dynamic, fast access to wide array of software
  * State management in `/etc` and `/var` is well understood
  * Can swap between major/minor system states (`apt-get upgrade` is similar to `apt-get dist-upgrade`)
  * Generally supports any filesystem or partition layout
 
-Drawbacks
+Drawbacks:
 
  * As package set grows, testing becomes combinatorially more expensive
  * Live system mutation, no rollbacks
 
 ### Image benefits and drawbacks
 
-Benefits
+Benefits:
 
  * Ensures all users are running a known state
  * Rollback supported
  * Easier to verify system integrity
 
-Drawbacks
+Drawbacks:
 
  * Many image systems have a read-only `/etc`, and writable partitions elsewhere
  * Must reboot for updates