Standardize requirement rendering

[daisykucharski]

Description

Use 1 instead of one

Type of change

Please tick the boxes that best match your changes.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• This requires a run of yarn install
• This has migration changes and requires a run of yarn dev:migration:run

How Has This Been Tested?

Please describe how you tested this PR (both manually and with tests) Provide instructions so we can reproduce.

• Test A
• Test B

Checklist:

• I have run the production builds in docker for the frontend/backend and ensure things run fine. Check README of repo on how to run if not sure.
• I have performed a self-review of my own code
• I have commented my code where needed
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I've run the end to end tests
• Any dependent changes have been merged and published in downstream modules

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
graduatenu-frontend-v2	❌ Failed (Inspect)			Nov 12, 2023 8:11pm

[BrandonLim8890]

so clean