From 520b853a443d9bdfa5fc3ceace5e89ac08981fb2 Mon Sep 17 00:00:00 2001
From: Makihiro <13536348+mackysoft@users.noreply.github.com>
Date: Tue, 20 Oct 2026 17:45:40 +0900
Subject: [PATCH 1/3] docs(readme): link to the FAQ category

Why
Each FAQ question has its own discussion in the FAQ category, and the README only needs to point readers there.

What Changed
Replace the single discussion link and topic descriptions with one FAQ category link.

Impact
Documentation only; FAQ answers remain in their individual discussions.
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 011d682..1df0c5b 100644
--- a/README.md
+++ b/README.md
@@ -216,7 +216,7 @@ Unity does not allow `UnityEngine.Object` types, including `MonoBehaviour` and `
 
 <a id="if-the-type-is-renamed-the-reference-is-lost"></a>
 
-See the [FAQ in Discussions](https://github.com/mackysoft/Unity-SerializeReferenceExtensions/discussions/121) for shared references in collections, type migrations, custom Inspector integrations, and copy/paste scope.
+[FAQ](https://github.com/mackysoft/Unity-SerializeReferenceExtensions/discussions/categories/faq)
 
 # <a id="help-and-contribute" href="#help-and-contribute"> ✉ Help & Contribute </a>
 

From 295060775c0051b59d220c43b7b9e151c4c72cdd Mon Sep 17 00:00:00 2001
From: Makihiro <13536348+mackysoft@users.noreply.github.com>
Date: Tue, 20 Oct 2026 17:48:35 +0900
Subject: [PATCH 2/3] docs(readme): introduce the FAQ link in a sentence

Why
Readers need a natural introduction to the FAQ without a detailed list of its topics.

What Changed
Introduce the FAQ category link with a short sentence about answers to common questions.

Impact
Keep the answers in their individual FAQ discussions.
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 1df0c5b..4bd2e19 100644
--- a/README.md
+++ b/README.md
@@ -216,7 +216,7 @@ Unity does not allow `UnityEngine.Object` types, including `MonoBehaviour` and `
 
 <a id="if-the-type-is-renamed-the-reference-is-lost"></a>
 
-[FAQ](https://github.com/mackysoft/Unity-SerializeReferenceExtensions/discussions/categories/faq)
+For answers to common questions, see the [FAQ](https://github.com/mackysoft/Unity-SerializeReferenceExtensions/discussions/categories/faq).
 
 # <a id="help-and-contribute" href="#help-and-contribute"> ✉ Help & Contribute </a>
 

From fffdaf7075a35104fae05bb3173a7250cbbc20b8 Mon Sep 17 00:00:00 2001
From: Makihiro <13536348+mackysoft@users.noreply.github.com>
Date: Tue, 20 Oct 2026 17:50:30 +0900
Subject: [PATCH 3/3] docs(readme): clarify the path before opening an issue

Why
Readers should look for existing answers before opening a new issue.

What Changed
Ask readers to check Discussions and existing Issues, then open an issue if they cannot find a solution.

Impact
Keep the support guidance concise and preserve the FAQ category link.
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 4bd2e19..83cd60f 100644
--- a/README.md
+++ b/README.md
@@ -220,7 +220,7 @@ For answers to common questions, see the [FAQ](https://github.com/mackysoft/Unit
 
 # <a id="help-and-contribute" href="#help-and-contribute"> ✉ Help & Contribute </a>
 
-For usage questions and community discussions, visit [Discussions](https://github.com/mackysoft/Unity-SerializeReferenceExtensions/discussions). Feature requests and reproducible bug reports are welcome in [Issues](https://github.com/mackysoft/Unity-SerializeReferenceExtensions/issues).
+If you have a question, first check [Discussions](https://github.com/mackysoft/Unity-SerializeReferenceExtensions/discussions) and existing [Issues](https://github.com/mackysoft/Unity-SerializeReferenceExtensions/issues). If you cannot find a solution, open a new issue.
 
 If you feel that my works are worthwhile, I would greatly appreciate it if you could sponsor me.