Correction on "Burial in a private cemetery" page

[strelichl]

Issue Description

Pulling this into the current sprint since it should be a quick fix.

On Burial In A Private Cemetery, we need a correction to the response “Is a spouse or dependent child eligible for an inscription on the Veteran’s headstone or marker in a private cemetery?"

Currently:
Yes. If the spouse or dependent child is eligible for burial in a VA national cemetery (but isn’t buried there), we’ll pay for an inscription on the Veteran’s headstone or marker.

Correction: Yes. A spouse or dependent child can have their name, dates of birth and death, and a term of endearment inscribed (at VA’s expense) on a Government-furnished headstone or marker that is placed in a private cemetery if the Veteran died on or after October 1, 2019.

---

Tasks

• [x] Update text on the page (Derek)
  • [ ] Review page changes (Megan)
  • [ ] Publish updated page (Megan)

Acceptance Criteria

• [ ] Updated page is live on the site

[d-beyer]

@strelichl I have a few questions about this change:

• The correction text basically mirrors the text in the accordion lower on the page (see screenshot). Is it necessary to repeat this information?
• The line that's being corrected mentions being "eligible for burial in a VA national cemetery", which leads into the link "Learn about eligibility for burial in a national cemetery". This is removed in the correction. Is that information incorrect or unnecessary?
• The correction only covers "if the Veteran died on or after October 1, 2019", but the current page also has an accordion about Veterans who died before that date. Is that information still correct and relevant?

[strelichl]

@d-beyer great questions!

• The correction text basically mirrors the text in the accordion lower on the page (see screenshot). Is it necessary to repeat this information? Yes, there's enough difference in detail/phrasing to list twice (especially with one "hidden" in an accordion)
• The line that's being corrected mentions being "eligible for burial in a VA national cemetery", which leads into the link "Learn about eligibility for burial in a national cemetery". This is removed in the correction. Is that information incorrect or unnecessary? The link will stay! The stakeholder just copy-pasted the one relevant sentence so didn't include it in the request.
• The correction only covers "if the Veteran died on or after October 1, 2019", but the current page also has an accordion about Veterans who died before that date. Is that information still correct and relevant? Yes, they just asked about this one section.

[d-beyer]

@strelichl Gotcha, thanks.

@megzehn I've made this update and it's ready for your review.

[strelichl]

Capturing our discussion around this:

• Correction text IS redundant (sorry Derek! Randi and I were both looking at it wrong)
• Simplest solution is to leave the page as-is

Randi took this back to the stakeholder and got this response:

The issue is the statement on the site is incorrect. The statement says NCA will pay for an inscription, which is being interpreting that NCA will pay to have a local monument company inscribe the marker. We are asking for the entire statement to be replaced with the highlighted statement below: Correction: Yes. A spouse or dependent child can have their name, dates of birth and death, and a term of endearment inscribed (at VA’s expense) on a Government-furnished headstone or marker that is placed in a private cemetery if the Veteran died on or after October 1, 2019.

Next steps:

• Our edits to those accordions last year maybe changed the meaning. So those should be updated to say: VA will pay for that inscription but the Veteran’s family is responsible for getting the inscription done.
• The content under the H2 “Is a spouse or dependent child eligible for an inscription on the Veteran’s headstone or marker in a private cemetery?” is still correct. But add line of text there furthering the point that it’s the Veteran’s responsibility to take care of getting the inscription.

@d-beyer if you can draft these changes in Drupal, that would be ideal. Randi will bring it back to the stakeholder and hopefully we can wrap this up today or tomorrow. I'm happy to help the word-smithing (let's use the same Slack thread) and let me know if you have any questions.

[RLHecht]

@strelichl we wound up working with the stakeholders directly on a Teams call and in email to make these changes. We can close this ticket out since the changes are now live!