Ensure terminological consistency in Phase 1 Japanese Translations (Target updates required)

During the final review of the Phase 1 Japanese documentation, inconsistencies in the use of specific terms were identified. These inconsistencies are particularly evident when compared to the consistent expressions in the original English source content. Given the visibility of these issues to end users, it is critical to address them prior to the official launch date next month to uphold content quality.

Background:

• Many Phase 1 files have already been delivered to GitLab.
• The current translations contain inconsistencies that have been flagged by the Japanese content reviewer, Emi Kimura.
• Fixing these inconsistencies is essential for delivering a consistent user experience.
• Current TMs need to be clean, but if translations are not updated in GitLab, users will continue to see outdated or inconsistent translations in production.

Proposed solution:

We will perform target updates for the affected Phase 1 files to correct the inconsistencies without initiating full resend or recycle workflows.

Requirements for implementation:

• Argos Multilingual to support target updates for the relevant Phase 1 files.
• GitLab project managers to identify and list affected files/segments (with support from the reviewer).
• Translation requests must be reopened in Argo to enable target updates to be pushed back to GitLab.
• Timeline alignment to ensure updates are completed before the planned official release, or a plan for post-publication updates if necessary.

Action Items:

• Identify all affected files/segments with inconsistent terminology.
• Confirm method of update (target update confirmed as preferred).
• Reopen translation requests in Argo for the necessary files.
• Argos to apply updates and deliver corrected translations to GitLab.
• Final quality assurance check by reviewer prior to launch.

Let me know if there's anything else you'd like to add.

Thanks,

Vic