From 8b909acdcf988bdbf43289d56e81cc46339e869d Mon Sep 17 00:00:00 2001
From: Cem Aksoylar <caksoylar@users.noreply.github.com>
Date: Tue, 13 Aug 2024 10:58:13 -0700
Subject: [PATCH] refactor(docs): Add subheaders for devicetree error types

---
 docs/docs/troubleshooting/building-issues.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/docs/troubleshooting/building-issues.md b/docs/docs/troubleshooting/building-issues.md
index a8d1fc99..5ea52611 100644
--- a/docs/docs/troubleshooting/building-issues.md
+++ b/docs/docs/troubleshooting/building-issues.md
@@ -23,6 +23,8 @@ If you get an error stating `Keymap node not found, check a keymap is available
 
 ### Devicetree Errors
 
+#### "parse error"
+
 A `devicetree error` followed by a reference to the line number on `<keyboard>.keymap` refers to an issue at the exact line position in that file. For example, below error message indicates a missing `;` at line 109 of the `cradio.keymap` file:
 
 ```
@@ -31,6 +33,8 @@ devicetree error: /__w/zmk-config/zmk-config/config/cradio.keymap:109 (column 4)
 
 Note that the provided number for the column corresponds to the numbering after the preprocessor expansion and it will likely not match the column numbers in your keymap.
 
+#### "lacks #binding-cells"
+
 A `devicetree error` followed by an `empty_file.c` reference with `lacks #binding-cells` string indicates possible problems with improper parameters for specific bindings:
 
 ```
@@ -39,6 +43,8 @@ devicetree error: <Node /soc/gpio@50000300 in '/tmp/tmp.vJq9sMwkcY/zephyr/misc/e
 
 This error can be triggered by incorrect binding syntax such as `&kp BT_SEL 0` instead of `&bt BT_SEL 0`.
 
+#### "devicetree_generated.h[...] undeclared here"
+
 A `devicetree_generated.h` error that follows with an "undeclared here" string indicates a problem with key bindings, like behavior nodes (e.g. `&kp` or `&mt`) with incorrect number of parameters:
 
 ```