From 4f6d6db4823a3ec6d6e332ff662d4b3a8838b2de Mon Sep 17 00:00:00 2001
From: tmathern <60901087+tmathern@users.noreply.github.com>
Date: Thu, 25 Jun 2026 14:22:28 -0700
Subject: [PATCH] docs: Fix header formatting for deprecated functions section

---
 docs/faqs.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/faqs.md b/docs/faqs.md
index d192d27..0863130 100644
--- a/docs/faqs.md
+++ b/docs/faqs.md
@@ -114,7 +114,7 @@ builder.sign(source, output, signer);
 
 When creating a new manifest, the chain is preserved once the original asset is added as an ingredient. The ingredient carries the original asset's manifest data, so validators can trace the full history. If the original is not added as an ingredient, the provenance chain is broken: the new manifest has no link to the original. This might be intentional (starting fresh) or a mistake (losing provenance).
 
-### What replaced `read_file`, `read_ingredient_file`, and `sign_file`?
+## What replaced `read_file`, `read_ingredient_file`, and `sign_file`?
 
 These file-based functions not attached to an API-exposed object, `read_file`, `read_ingredient_file`, and `sign_file`, were deprecated, then removed. Each legacy function maps to another implementation path using existing APIs on the `Reader` or `Builder` objects: