Fix incorrect Scoop settings.json path in documentation

[Copilot]

The documentation incorrectly stated that Scoop installations store settings.json in %LOCALAPPDATA%\Microsoft\Windows Terminal\settings.json. User verification shows Scoop actually uses its persist directory.

Changes

• Separated Scoop from other unpackaged installations in the settings path list
• Updated Scoop path to ~\scoop\persist\windows-terminal\settings\settings.json
• Retained %LOCALAPPDATA%\Microsoft\Windows Terminal\settings.json for Chocolatey and other unpackaged methods

Before:

- Terminal (unpackaged: Scoop, Chocolatey, etc): `%LOCALAPPDATA%\Microsoft\Windows Terminal\settings.json`

After:

- Terminal (Scoop): `~\scoop\persist\windows-terminal\settings\settings.json`
- Terminal (unpackaged: Chocolatey, etc): `%LOCALAPPDATA%\Microsoft\Windows Terminal\settings.json`

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Wrong path for Scoop's settings.json file</issue_title>
<issue_description>### Type of issue

Outdated article

Feedback

Hi

On the Installation guide for Windows Terminal, both French and original English versions, the config file for Scoop is said to sit in %LOCALAPPDATA%:

Terminal (unpackaged: Scoop, Chocolatey, etc): %LOCALAPPDATA%\Microsoft\Windows Terminal\settings.json

However, opening the config file through Shift-Click on Parameters, the Scoop version opens a file in Scoop's app folder:
~\scoop\apps\windows-terminal\1.21.3231.0\settings\settings.json. (it's also present in ~\scoop\persist\windows-terminal\settings)

Page URL

https://learn.microsoft.com/fr-fr/windows/terminal/install

Content source URL

https://github.com/MicrosoftDocs/terminal/blob/main/TerminalDocs/install.md

Author

@cinnamon-msft

Document Id

d7838521-160a-6b6e-6795-a8049f18ede6</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Wrong path for Scoop's settings.json file #822

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[learn-build-service-prod]

Learn Build status updates of commit a963a93:

✅ Validation status: passed

For more details, please refer to the build report.

[learn-build-service-prod]

Learn Build status updates of commit 5818402:

✅ Validation status: passed

File	Status	Preview URL	Details
TerminalDocs/install.md	✅Succeeded	View

For more details, please refer to the build report.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.