Distinguish a linked help block from an identical pasted copy

Equal text does not establish a shared link

In this original composition model, A1 links B-support; A2 stores an inline copy of B-support’s original text; A3 links B-login. A linked article reads the current block text, while an inline article retains its own text. Updating a block does not change any article’s stored published/draft status. That unchanged status is not evidence that new text was reviewed.

Inspect actual before-and-after text

Initially A1 and A2 both say “Send the export task reference.” Change B-support to add “and selected filter”: only A1 changes. A2 keeps the original text and A3 retains its login instruction. A1 remains published and A3 remains draft.

1. Identify linked and inline records
2. Edit only B-support
3. Resolve linked text
4. Compare text and stored status

An absent block creates a missing-block outcome; do not silently use an old pasted copy.

Edit text without implying verification

The local input edits the support block text and the preview shows each article’s resolved text, storage form and status. Reset restores the original block. Export contains the complete block/article source and resolution trace.

Removing B-support leaves A1 unresolved with text null; A2 remains its intact inline copy. Block IDs and article IDs are distinct within their respective lists, each list has at most 30 records, and text is nonempty up to 120 characters. Text is displayed as text, never executable HTML.

A content-maintenance brief should record linked versus copied content, affected locale blocks and required reviews. Use the language-revision example next; use the existing dependency lesson for deeper graph traversal.