Trust & methodology

Corrections & Feedback

How to report inaccurate, insensitive or unclear wording in this resource.

Words around death deserve careful review. If you find a factual error, a broken page, insensitive wording, a privacy concern, or an example that does not fit the stated situation, please use the site’s normal contact channel and include the page URL plus the exact sentence.

What we correct

We correct factual mistakes, broken templates, unsafe assumptions, duplicate/canonical problems, mislabeled relationships, unclear guidance and source links that no longer support the stated principle.

Versioning

This engine uses a release date for sitemap last-modified values. Pages are not marked as freshly updated every day when their editorial content has not changed.

Correction priority

We prioritize issues that could mislead a grieving reader, expose private information, misstate a sensitive situation, break a virtual page, or create duplicate/canonical problems. Cosmetic wording preferences are lower priority than accuracy, safety, privacy, and page integrity.

What to include in a useful report

Send the exact page URL, the sentence or component involved, what appears wrong, and—when the issue is factual or source-related—the evidence that supports the correction. Screenshots can help with layout problems, but the page URL is still important because this site uses virtual routes.

How corrections should be made

Fix the smallest underlying cause rather than masking the symptom. A wrong relationship label should be corrected in the source profile; a broken route should be fixed in routing; a repeated message should be corrected in the generator; a misleading source note should be corrected where the source mapping is defined.

Transparency and release dates

Meaningful editorial or technical releases update the engine release date used by the sitemap. We do not refresh dates every day merely to create the appearance of freshness.