Audit and update Login.gov content across registrar and get.gov

[Katherine-MN]

Sub-issue description

Following discovery in #521, this ticket focuses on auditing existing content and implementing updates to improve clarity and consistency across the registrar experience.

The goal is to ensure users clearly understand what Login.gov is, when and why it’s used, and how it relates to their get.gov profile.

Acceptance criteria

• Audit all locations where Login.gov and get.gov profiles are referenced, including:
  • get.gov content
  • Registrar UI copy
• Assess whether messaging is clear, consistent, and contains the key points identified during discovery
• Propose revised and/or new content
• Share content with design and product leads
• Determine next steps for implementing the changes (e.g. who will write tickets)

Additional context

• Any revisions to registrar copy and emails will result in a pull request in the manage.get.gov repo.
• The links in the A/C are for the textual content, not the actual repo files where they'll need to be edited. Tag the team if you need help finding those files in the repos.

[waiwanwong]

@h-m-f-t / @katypies -- Ready for your review: get.gov recommendations and Registrar recommendations. Also posting a link in our disco channel.

[waiwanwong]

@h-m-f-t / @katypies -- Thanks for your feedback on the get.gov and registrar UI content. Should we move forward with implementing these changes you have approved or would you like for me to schedule a follow-up meeting to discuss next steps?