fix: use npm update instead of npm install in update notification

[Jamkris]

Summary by CodeRabbit

• Bug Fixes
  • Updated the update command instructions in English and Korean locales from npm install -g git-env-manager to npm update -g git-env-manager.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 6d29d582-0be2-4e24-a2e5-01fd9e4d496c

📥 Commits

Reviewing files that changed from the base of the PR and between 598259e and 98d8eaf.

📒 Files selected for processing (2)

• src/i18n/locales/en.ts
• src/i18n/locales/ko.ts

---

Walkthrough

Updates the update command instruction in English and Korean i18n locale files from npm install -g git-env-manager to npm update -g git-env-manager. No logic, control flow, or exported declarations changed.

Changes

Cohort / File(s)	Summary
i18n Locale Messages src/i18n/locales/en.ts, src/i18n/locales/ko.ts	Updated updateCommand string value to recommend npm update instead of npm install for package updates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• PR #13: Directly related—updates the same i18n message keys (updateCommand) with an alternative npm command recommendation.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the primary change: updating the command text from 'npm install -g' to 'npm update -g' in update notification messages across English and Korean locales.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/update-command-text

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}