cleanup

Author: nkolev92

docs/TOC.md

@@ -32,6 +32,7 @@
 ### [PackageDownload functionality](consume-packages/packagedownload-functionality.md)
 ## Reference packages in your project
 ### [PackageReference in project files](consume-packages/package-references-in-project-files.md)
+### [Targeting multiple frameworks in a project file](consume-packages/package-reference-multi-targeting.md)
 ### [Migrate packages.config to PackageReference](consume-packages/migrate-packages-config-to-package-reference.md)
 ### [packages.config](reference/packages-config.md)
 ### [Central Package Management](consume-packages/Central-Package-Management.md)

docs/consume-packages/Package-References-in-Project-Files.md

@@ -142,6 +142,82 @@ Note that because `build` is not included with `PrivateAssets`, targets and prop
 > [!NOTE]
 > When `developmentDependency` is set to `true` in a `.nuspec` file, this marks a package as a development-only dependency, which prevents the package from being included as a dependency in other packages. With PackageReference *(NuGet 4.8+)*, this flag also means that it will exclude compile-time assets from compilation. For more information, see [DevelopmentDependency support for PackageReference](https://github.com/NuGet/Home/wiki/DevelopmentDependency-support-for-PackageReference).
 
+## Targeting multiple frameworks
+
+SDK-style projects support multi-targeting by listing multiple values in the `TargetFrameworks` property. When a project targets multiple frameworks, NuGet restore produces a separate dependency graph for each framework, and `dotnet pack` creates a package with framework-specific assets for each target.
+
+```xml
+<Project Sdk="Microsoft.NET.Sdk">
+  <PropertyGroup>
+    <TargetFrameworks>net10.0;netstandard2.0</TargetFrameworks>
+  </PropertyGroup>
+</Project>
+```
+
+For a step-by-step guide on setting up a multi-targeted project, see [Support multiple .NET frameworks in your project file](../create-packages/multiple-target-frameworks-project-file.md).
+
+### How TargetFramework values work
+
+The `TargetFramework` property in a project file is a friendly name — an alias — that gets translated into a canonical framework identity. The .NET SDK performs this translation by setting the `TargetFrameworkMoniker` (TFM), and when applicable, the `TargetPlatformMoniker` properties.
+
+NuGet uses these moniker properties — not the `TargetFramework` string — for package compatibility checks. This means the `TargetFramework` value itself can be any string, as long as the moniker properties are set correctly.
+
+For more details on the aliasing mechanism, see [TargetFramework values are aliases](../reference/target-frameworks.md#targetframework-values-are-aliases).
+
+### Multi-targeting with duplicate frameworks
+
+*This feature requires [NuGet 7.6](../release-notes/NuGet-7.6.md) / .NET SDK 10.0.300 or later.*
+
+Because `TargetFramework` values are aliases, multiple aliases can resolve to the *same* effective framework. Starting with [NuGet 7.6](../release-notes/NuGet-7.6.md) / .NET SDK 10.0.300, NuGet and the .NET SDK support this scenario.
+
+This enables use cases such as:
+
+- **Multi-RID builds**: Build platform-specific assemblies from a single project.
+
+  ```xml
+  <Project Sdk="Microsoft.NET.Sdk">
+    <PropertyGroup>
+      <TargetFrameworks>apple;banana</TargetFrameworks>
+    </PropertyGroup>
+
+    <PropertyGroup>
+      <TargetFrameworkIdentifier>.NETCoreApp</TargetFrameworkIdentifier>
+      <TargetFrameworkVersion>v10.0</TargetFrameworkVersion>
+      <TargetFrameworkMoniker>.NETCoreApp,Version=v10.0</TargetFrameworkMoniker>
+    </PropertyGroup>
+  </Project>
+  ```
+
+- **Multi-version extensions**: Target multiple versions of a host application, such as Visual Studio.
+
+  ```xml
+  <Project Sdk="Microsoft.VisualStudio.Extensibility.Sdk">
+    <PropertyGroup>
+      <TargetFrameworks>vs18;vs17.14</TargetFrameworks>
+    </PropertyGroup>
+  </Project>
+  ```
+
+  In this example, the Visual Studio Extensibility SDK is responsible for setting the canonical moniker properties for each alias.
+
+#### Pack
+
+A NuGet package can only contain one set of build output and one dependency group per effective framework. When you pack a project with duplicate effective frameworks, you must tell NuGet which alias contributes these assets or the pack raises [NU5051](../reference/errors-and-warnings/NU5051.md). See [NU5051](../reference/errors-and-warnings/NU5051.md) for resolution steps and examples.
+
+#### Lock file
+
+When a project uses duplicate effective frameworks, the [packages lock file](#locking-dependencies) is automatically upgraded to a format that uses the alias as the key instead of the effective framework. This upgrade happens transparently — locked mode and CI/CD scenarios continue to work as before.
+
+#### Project references
+
+When a project references another project that has multiple aliases resolving to the same framework, NuGet uses the alias name as a tiebreaker. If the referencing project has an alias with the same name as one in the referenced project, that alias is preferred. If there’s no matching name and multiple candidates exist, NuGet reports an error.
+
+#### Limitations
+
+- Only SDK-style projects support duplicate effective frameworks.
+- Aliases that contain path separator characters (`/` or `\`) are blocked.
+- Visual Studio’s Package Manager UI doesn’t have special support for duplicate frameworks, but you can manage packages by editing the project file directly or using the `dotnet` CLI.
+
 ## Adding a PackageReference condition
 
 You can use a condition to control whether a package is included. Conditions can use any MSBuild variable or a variable defined in the targets or props file. However, at present, only the `TargetFramework` variable is supported.
@@ -239,60 +315,6 @@ namespace PackageReferenceAliasesExample
 
 ```
 
-## Multi-targeting with duplicate frameworks
-
-*This feature requires [NuGet 7.6](../release-notes/NuGet-7.6.md) / .NET SDK 10.0.300 or later.*
-
-SDK-style projects support [multi-targeting](../create-packages/multiple-target-frameworks-project-file.md) by listing multiple values in the `TargetFrameworks` property. Because [TargetFramework values are aliases](../reference/target-frameworks.md#targetframework-values-are-aliases), multiple aliases can resolve to the *same* effective framework. Starting with [NuGet 7.6](../release-notes/NuGet-7.6.md) / .NET SDK 10.0.300, NuGet and the .NET SDK support this scenario.
-
-This enables use cases such as:
-
-- **Multi-RID builds**: Build platform-specific assemblies from a single project.
-
-  ```xml
-  <Project Sdk="Microsoft.NET.Sdk">
-    <PropertyGroup>
-      <TargetFrameworks>apple;banana</TargetFrameworks>
-    </PropertyGroup>
-
-    <PropertyGroup>
-      <TargetFrameworkIdentifier>.NETCoreApp</TargetFrameworkIdentifier>
-      <TargetFrameworkVersion>v10.0</TargetFrameworkVersion>
-      <TargetFrameworkMoniker>.NETCoreApp,Version=v10.0</TargetFrameworkMoniker>
-    </PropertyGroup>
-  </Project>
-  ```
-
-- **Multi-version extensions**: Target multiple versions of a host application, such as Visual Studio.
-
-  ```xml
-  <Project Sdk="Microsoft.VisualStudio.Extensibility.Sdk">
-    <PropertyGroup>
-      <TargetFrameworks>vs18;vs17.14</TargetFrameworks>
-    </PropertyGroup>
-  </Project>
-  ```
-
-  In this example, the Visual Studio Extensibility SDK is responsible for setting the canonical moniker properties for each alias.
-
-### Pack
-
-A NuGet package can only contain one set of build output and one dependency group per effective framework. When you pack a project with duplicate effective frameworks, you must tell NuGet which alias contributes these assets or the pack raises [NU5051](../reference/errors-and-warnings/NU5051.md). See [NU5051](../reference/errors-and-warnings/NU5051.md) for resolution steps and examples.
-
-### Lock file
-
-When a project uses duplicate effective frameworks, the [packages lock file](#locking-dependencies) is automatically upgraded to a format that uses the alias as the key instead of the effective framework. This upgrade happens transparently — locked mode and CI/CD scenarios continue to work as before.
-
-### Project references
-
-When a project references another project that has multiple aliases resolving to the same framework, NuGet uses the alias name as a tiebreaker. If the referencing project has an alias with the same name as one in the referenced project, that alias is preferred. If there's no matching name and multiple candidates exist, NuGet reports an error.
-
-### Limitations
-
-- Only SDK-style projects support duplicate effective frameworks.
-- Aliases that contain path separator characters (`/` or `\`) are blocked.
-- Visual Studio's Package Manager UI doesn't have special support for duplicate frameworks, but you can manage packages by editing the project file directly or using the `dotnet` CLI.
-
 ## NuGet warnings and errors
 
 *This feature is available with NuGet **4.3** or above and with Visual Studio 2017 **15.3** or above.*

docs/create-packages/multiple-target-frameworks-project-file.md

@@ -70,7 +70,7 @@ Here is the *.csproj* file that is generated using the preceding steps and .NET
 
 Starting with [NuGet 7.6](../release-notes/NuGet-7.6.md) / .NET SDK 10.0.300, you can use multiple `TargetFrameworks` values that resolve to the same underlying framework. This enables scenarios like building for multiple runtimes or targeting multiple versions of a host application from a single project.
 
-For details on how this works with restore and pack, see [Multi-targeting with duplicate frameworks](../consume-packages/package-references-in-project-files.md#multi-targeting-with-duplicate-frameworks).
+For details on how this works with restore and pack, see [Targeting multiple frameworks](../consume-packages/package-references-in-project-files.md#multi-targeting-with-duplicate-frameworks).
 
 ## See also
 

docs/reference/errors-and-warnings/NU5051.md

@@ -98,4 +98,4 @@ Suppress the default build output and dependencies for the secondary aliases, an
 
 With this configuration, `net10.0` contributes the default `lib/net10.0/` build output and dependencies, while `linux` and `ios` place their assemblies under `runtimes/linux/lib/net10.0/` and `runtimes/ios/lib/net10.0/` respectively.
 
-For more information about multi-targeting with duplicate frameworks, see [PackageReference in project files](../../consume-packages/package-references-in-project-files.md#multi-targeting-with-duplicate-frameworks). For more information about pack extensibility, see [pack target](../msbuild-targets.md#pack-target).
+For more information about multi-targeting with duplicate frameworks, see [Targeting multiple frameworks](../../consume-packages/package-references-in-project-files.md#multi-targeting-with-duplicate-frameworks). For more information about pack extensibility, see [pack target](../msbuild-targets.md#pack-target).

docs/reference/target-frameworks.md

@@ -47,7 +47,7 @@ This project restores and builds for .NET 10.0, even though the `TargetFramework
 
 ## Multi-targeting with duplicate frameworks
 
-Starting with [NuGet 7.6](../release-notes/NuGet-7.6.md) / .NET SDK 10.0.300, multiple `TargetFrameworks` aliases can resolve to the same effective framework. This enables scenarios like multi-RID builds and multi-version extension targeting. For details on how this works with restore, pack, lock files, and project references, see [Multi-targeting with duplicate frameworks](../consume-packages/package-references-in-project-files.md#multi-targeting-with-duplicate-frameworks).
+Starting with [NuGet 7.6](../release-notes/NuGet-7.6.md) / .NET SDK 10.0.300, multiple `TargetFrameworks` aliases can resolve to the same effective framework. This enables scenarios like multi-RID builds and multi-version extension targeting. For details on how this works with restore, pack, lock files, and project references, see [Targeting multiple frameworks](../consume-packages/package-references-in-project-files.md#multi-targeting-with-duplicate-frameworks).
 
 ## Supported frameworks
 

docs/release-notes/NuGet-7.5.md

@@ -2,7 +2,7 @@
 title: NuGet 7.5 Release Notes
 description: Release notes for NuGet 7.5 including new features, bug fixes, and DCRs.
 author: nikolev
-ms.topic: conceptual
+ms.topic: release-notes
 ---
 # NuGet 7.5 Release Notes