diff --git a/docs/buyables.md b/docs/buyables.md
index d85ae36..4ae7c58 100644
--- a/docs/buyables.md
+++ b/docs/buyables.md
@@ -5,18 +5,18 @@ the player can reset the purchases to get their currency back.
 
 Buyables should be formatted like this:
 
-`` buyables: {
-  rows: # of rows
-  cols: # of columns
-  respec() {}, **optional**, implement it to reset things and give back your currency.
-               Having this function makes a respec button appear
-  respecText: **optional**, text that appears on the respec button
-  11: {
-    desc: "Blah",
+``buyables: {
+    rows: # of rows
+    cols: # of columns
+    respec() {}, **optional**, implement it to reset things and give back your currency.
+                 Having this function makes a respec button appear
+    respecText: **optional**, text that appears on the respec button
+    11: {
+        desc: "Blah",
+        etc
+    }
     etc
-  }
-  etc
-} ``
+}``
 
 Features:
 
diff --git a/docs/challenges.md b/docs/challenges.md
index 29dd588..dafee20 100644
--- a/docs/challenges.md
+++ b/docs/challenges.md
@@ -3,13 +3,13 @@
 Challenges are stored in the following format:
 
 ``challs: {
-  rows: # of rows
-  cols: # of columns
-  11: {
-    name: "Ouch",
+    rows: # of rows
+    cols: # of columns
+    11: {
+        name: "Ouch",
+        etc
+    }
     etc
-  }
-  etc
 }``
 
 You can use inChall(layer, id) and hasChall(layer, id) to determine if the player is currently in a challenge,
diff --git a/docs/custom-tab-layouts.md b/docs/custom-tab-layouts.md
index 1498b71..773f71d 100644
--- a/docs/custom-tab-layouts.md
+++ b/docs/custom-tab-layouts.md
@@ -2,7 +2,8 @@
 
 Custom tab layouts can be used to do basically anything in a tab window, especially combined with the "style" layer feature. The tabFormat feature is an array of things, like this:
 
-`` tabFormat: ["main-display",
+``
+    tabFormat: ["main-display",
             ["prestige-button", function(){return "Melt your points into "}],
             ["raw-html", function() {return "<button onclick='console.log(`yeet`)'>'HI'</button>"}],
             ["display-text",
diff --git a/docs/layer-features.md b/docs/layer-features.md
index 937730e..e502531 100644
--- a/docs/layer-features.md
+++ b/docs/layer-features.md
@@ -11,7 +11,7 @@ Key:
 # Layer Definition features
 
 - startData(): A function to return the default save data for this layer. Add any variables you have to it.
-             Any nonstandard Decimal variables need to be added to convertToDecimal as well.
+            Any nonstandard Decimal variables need to be added to convertToDecimal as well.
     Standard values:
         Required:
             unl: a bool determining if this layer is unlocked or not
diff --git a/docs/milestones.md b/docs/milestones.md
index 3b7e1de..e73fecd 100644
--- a/docs/milestones.md
+++ b/docs/milestones.md
@@ -3,10 +3,10 @@
 Milestones should be formatted like this:
 
 ``milestones: {
-  0: {
-    requirementDesc: "123 waffles",
-  }
-  etc
+    0: {
+        requirementDesc: "123 waffles",
+    }
+    etc
 }``
 
 You can use inChall(layer, id) and hasChall(layer, id) to determine if the player is currently in a challenge,
diff --git a/docs/upgrades.md b/docs/upgrades.md
index f37154b..6e407fd 100644
--- a/docs/upgrades.md
+++ b/docs/upgrades.md
@@ -3,13 +3,13 @@
 Upgrades are stored in the following format:
 
 ``upgrades: {
-  rows: # of rows
-  cols: # of columns
-  11: {
-    desc: "Blah",
+    rows: # of rows
+    cols: # of columns
+    11: {
+        desc: "Blah",
+        etc
+    }
     etc
-  }
-  etc
 }``
 
 You can use hasUpg(layer, id) to determine if the player has an upgrade. This is useful for implementing bonuses.