Updates documentation to clarify #155.

[jtdub]

closes #155

[Copilot]

Pull Request Overview

This PR adds clarifying documentation to explain the difference between HConfig.merge() and HConfig.future() methods, addressing issue #155. The documentation helps users understand when to use each method and what to expect from their behavior.

• Adds a new section in future-config.md explaining the distinct purposes of merge() vs future()
• Adds a note in custom-workflows.md explaining merge()'s strict behavior and when to use future() instead
• Includes minor formatting fixes to code blocks

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
docs/future-config.md	Adds new section explaining merge() vs future(), clarifying that merge() is strict and raises DuplicateChildError for overlapping sections while future() allows overlapping configuration
docs/custom-workflows.md	Adds contextual note about merge() behavior with link to future() documentation; updates code block syntax highlighting to text for output examples

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.