Review and Align Language Across Documentation and Interface Elements

[kimberlyvaldez07]

Overview

We need to ensure that text used across the project follows consistent tone, terminology, and style conventions. This review will identify any inconsistencies in phrasing and recommend updates to improve clarity and alignment with our communication standards.

Action Items

• Conduct a comprehensive review of text across the project to evaluate tone, terminology, capitalization, phrasing, and overall consistency.
• Identify and document:
  • Inconsistent wording or terminology
  • Incorrect or outdated information
  • Capitalization discrepancies
  • Tone inconsistencies
  • Deviations from established communication standards
• Record each inconsistency or instance of incorrect information in a structured list (include page name, section, and specific text).
• Create separate issues for each inconsistency or correction needed, clearly referencing:
  • The page/component affected
  • The current text
  • The recommended correction
• Ensure all new issues are properly labeled and linked back to this audit issue for tracking purposes.

Resources/Instructions

• 1.01 Projects page: https://www.hackforla.org/projects/
• 1.02 URL of page on Hack for LA website: A project's detail page (e.g. https://www.hackforla.org/projects/100-automations)
• 1.03 URL of link to code search: repo:hackforla/website NOT language:SVG NOT path:/^_data/internal/credits// Project Info and Page

[github-actions]

Hi @kimberlyvaldez07.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Complexity, Role, Feature, Size

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels