diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-update.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-update.mdx
index 9073747930..a0d9ee5b67 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire-update.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-update.mdx
@@ -108,7 +108,7 @@ The following options are available:
Channel to update to (`stable`, `staging`, `daily`). When switching channels, `aspire update` applies all package version edits to your project first and then runs a single `dotnet restore`, ensuring that NuGet source mappings added for the target channel are in place before any restore is attempted.
- For non-stable channels (`staging`, `daily`), `aspire update` creates or updates a project-level `nuget.config` with the source mappings needed to resolve packages from that channel's feed. For the `stable` channel, no `nuget.config` is created because nuget.org is already the default NuGet source. If an existing `nuget.config` is present and the project has package or channel updates to apply when switching to or using `stable`, those changes are applied as part of that update to remove any stale channel-specific feed entries. If the project is already up to date, `aspire update` reports this and exits before touching `nuget.config`, so a stale channel-specific feed entry from a previous `staging` or `daily` switch can remain until the next update that actually applies changes.
+ For non-stable channels (`staging`, `daily`), `aspire update` creates or updates a project-level `nuget.config` with the selected channel's feed. The generated file contains only the selected feed and doesn't copy feeds or source mappings from your machine-level NuGet configuration. If your effective NuGet configuration doesn't use package source mappings, `aspire update` adds the feed without enabling mapping, so other dependencies continue to use your ambient feeds. If mapping is already enabled, it adds the Aspire-specific mappings for the selected feed and preserves your existing mappings. `aspire update` never adds a mapping `` or a catch-all nuget.org mapping, and it leaves entries you authored (including `` and disabled sources) untouched. For the `stable` channel, no `nuget.config` is created because nuget.org is already the default NuGet source. If an existing `nuget.config` is present and the project has package or channel updates to apply when switching to or using `stable`, those changes are applied as part of that update to remove any stale channel-specific feed entries. If the project is already up to date, `aspire update` reports this and exits before touching `nuget.config`, so a stale channel-specific feed entry from a previous `staging` or `daily` switch can remain until the next update that actually applies changes.
When you switch to a persistable channel, such as `daily`, `aspire update` also rewrites the top-level `channel` key in `aspire.config.json` when the file already exists. Only channels registered as _explicit_ channels are persisted, with one exception: the `stable` channel is treated as the portable default and is intentionally not pinned. The persisted channel keeps subsequent `aspire add` and `aspire update` runs resolving packages against the channel you just switched to.