Port Points navigation and field updates from PR #954 to branch 7.2

[promptless-for-oss]

Open in Promptless

Cherry-picks the Mautic UI-alignment change from PR #954 (branch 6.0) onto branch 7.2, aligning docs/points/points.rst with the Mautic 7.x Points UI. Renames the Point Action field to Action taken by Contact (singular, matching the product label), documents the new Point Group field on Point Actions, adds the Points > Manage Triggers navigation step, and expands the Point Triggers section with the Minimum number of Points, Contact color, and Trigger for existing applicable Contacts upon saving field descriptions. The 7.2 page already carried part of this alignment (the Manage Actions navigation and updated screenshots); this fills the remaining gaps. All navigation and field labels were verified against the Mautic 7.x product source before porting. No screenshots changed.

Trigger Events

• Comment on mautic/user-documentation#954 requesting cherry-picks to other branches

---

Review response (@adiati98 — navigation wording consistency)

Adopted PR #954's clearer, active-voice navigation wording on this branch so the three ports (#956/#957/#958) stay consistent with their source PR #954, rather than changing #954. Two lines in docs/points/points.rst changed:

• Point Actions: "On the left side, navigate to Points > Manage Actions and click the New button located in the top right corner to open the New Point Action window."
• Point Triggers: "To add a new trigger, on the left side, navigate to Points > Manage Triggers and click the New button located in the top right corner to create a new Point Trigger." (kept as a single sentence, per your earlier request to collapse the one-item list)

Both applied verbatim from #954's wording. Vale passes on the changed file.

[promptless-for-oss]

I noticed that some CI checks failed for this PR. I'm investigating whether the failures are caused by this suggestion. If they're unrelated or pre-existing, I'll leave this suggestion unchanged and create a separate suggestion if a standalone docs fix is needed.