Fix attestation participant glossary entry

[nrichers]

Pull Request Description

What and why?

Fixed incorrect attestation participant definition in the glossary (site/about/glossary/_attestation.qmd).

Before: "A user assigned to one of three roles in the attestation workflow — submitter, reviewer, or approver. Submitters must be model stakeholders; reviewers and approvers can be assigned by stakeholder or role."

After: "A user who participates in the attestation workflow as a submitter, reviewer, or approver. Submitters are assigned from model stakeholders; reviewers and approvers are assigned from organization roles."

Issues fixed:

1. Removed confusing "three roles" phrasing — submitters aren't assigned by role, they're assigned from model stakeholders
2. Corrected "can be assigned by stakeholder or role" to accurately reflect that reviewers/approvers are assigned from organization roles only
3. Aligned terminology with the UI ("Attestation Participants")

How to test

This is a small change, just review the file changed please.

What needs special review?

N/A

Dependencies, breaking changes, and deployment notes

None

Release notes

N/A (internal)

Checklist

• What and why
• Labels applied
• PR linked to Shortcut
• Documentation updated (if required)

[github-actions]

PR Summary

This pull request refines the definitions in the attestation glossary, particularly for the term "attestation participant." The description has been updated to clearly distinguish the roles: submitter, reviewer, and approver, and to specify that submitters are assigned from model stakeholders while reviewers and approvers are assigned from organizational roles. This change aims to improve the clarity and precision of the documentation related to the attestation process without altering any underlying functionality.

Test Suggestions

• Verify that the updated glossary definitions are correctly reflected in the generated documentation.
• Check for consistency in how roles and responsibilities are presented across related documentation files.
• Perform a spelling and grammar review to ensure the text meets the project’s style guide.

[github-actions]

Validate docs site

✓ INFO: A live preview of the docs site is available — Open the preview

[github-actions]

Lighthouse check results

⚠️ WARN: Average accessibility score is 0.87 (required: >0.9) — Check the workflow run

Show Lighthouse scores

Folder depth level checked: 0

Commit SHA: 1710a31

Modify the workflow to check a different depth:

• 0: Top-level navigation only — /index.html, /guide/guides.html, ...
• 1: All first-level subdirectories — /guide/.html, /developer/.html, ...
• 2: All second-level subdirectories — /guide/attestation/*.html, ...

Page	Accessibility	Performance	Best Practices	SEO
/developer/validmind-library.html	0.85	0.65	1.00	0.82
/get-started/get-started.html	0.85	0.68	1.00	0.73
/guide/guides.html	0.85	0.68	1.00	0.82
/index.html	0.93	0.66	1.00	0.82
/releases/all-releases.html	0.86	0.68	1.00	0.73
/support/support.html	0.91	0.62	1.00	0.82
/training/training.html	0.85	0.67	0.96	0.73