fix: DAH-3187 update FCFS how to apply link translations

[cliu02]

Description

Update translations for FCFS how to apply link.

Jira ticket

https://sfgovdt.jira.com/browse/DAH-3187

Before requesting eng review

Version Control

• branch name begins with angular if it contains updates to Angular code
• branch name contains the Jira ticket number
• PR name follows type: TICKET-NUMBER Description format, e.g. feat: DAH-123 New Feature. If the PR is urgent and does not need a ticket then use the format urgent: Description

Code quality

• the set of changes is small
• all automated code checks pass (linting, tests, coverage, etc.)
• code irrelevant to the ticket is not modified e.g. changing indentation due to automated formatting
• if the code changes the UI, it matches the UI design exactly

Review instructions

• instructions specify which environment(s) it applies to
• instructions work for PA testers
• instructions have already been performed at least once

Request eng review

• PR has needs review label
• Use Housing Eng group to automatically assign reviewers, and/or assign specific engineers
• If time sensitive, notify engineers in Slack

Before merging

Request product acceptance testing

• Code change is behind a feature flag
• If code change is not behind a feature flag, it has been PA tested in the review environment (use needs product acceptance label to indicate that the PR is waiting for PA testing)

[jimlin-sfgov]

@cliu02 This PR modifies non-english translation keys. Did you first make the changes in Phrase, and then do a phrasePull per our guide?

[cade-exygy]

Looks Good!

[cliu02]

@jimlin-sfgov not yet, I can do that! My understanding from our team eng sync is that we decided to remove the translations checkbox for the PR review template and work with Bridget to update Phrase before sending each round instead.

[jimlin-sfgov]

we decided to remove the translations checkbox for the PR review template and work with Bridget to update Phrase before sending each round instead

@cliu02 I guess we didn't make it clear enough during eng. sync. For the "standard" workflow of adding new translations, engineers do not need to interact with Phrase. For other translation workflows, there are additional steps that needed to be followed in the guide. Especially for this PR's case, changes must be made in Phrase first, otherwise it becomes problematic for whoever manages the next batch of human translations.

[cliu02]

@jimlin-sfgov got it sorry about that, @chadbrokaw has helped update these strings in Phrase!

[jimlin-sfgov]

LGTM