From e723aa663ea62e5ddfda4a7ca360adf9e88d36e2 Mon Sep 17 00:00:00 2001
From: Craig Jennings <c@cjennings.net>
Date: Tue, 16 Jun 2026 00:02:22 -0500
Subject: docs(readme): point the save FAQ at pearl-save-issue

The first FAQ entry still told users to push titles and descriptions through separate sync commands, which contradicts the unified save model. It now describes `pearl-save-issue` / `pearl-save-all` saving every changed field in one pass, with the lower-level sync commands kept as the footnote.
---
 README.org | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'README.org')

diff --git a/README.org b/README.org
index 45aea33..e553321 100644
--- a/README.org
+++ b/README.org
@@ -540,9 +540,9 @@ Each test file runs in its own Emacs batch process for isolation. See [[file:TES
 :CUSTOM_ID: faq
 :END:
 
-*** I edited the heading title and synced the description. Why did the title stay the same?
+*** I edited the heading title and the description. Why did only one of them update?
 
-Titles and descriptions push through separate commands. Use =pearl-sync-current-issue= for the body and =pearl-sync-current-issue-title= for the heading title.
+=pearl-save-issue= (=s=) saves every changed field of the issue at point in one pass, title and description together; =pearl-save-all= (=S=) does the same across the whole file. If only one field updated, you likely pushed it with a lower-level command (=pearl-sync-current-issue= for the body, =pearl-sync-current-issue-title= for the title). Reach for =pearl-save-issue= and edit-then-save handles every field at once.
 
 *** Why did square brackets disappear from a synced title?
 
-- 
cgit v1.2.3