Freshness Pass User Story: 173521 (#3172)

Author: GitHubber17

docs/consume-packages/Package-Restore.md

@@ -41,7 +41,7 @@ After a successful restore:
 
 If the package references in your project file or your *packages.config* file are incorrect and don't match your desired state, install or update the correct packages instead of using Package Restore.
 
-If you have missing packages or package-related errors after you run Package Restore, such as error icons in Solution Explorer, follow the instructions in [Troubleshooting Package Restore errors](package-restore-troubleshooting.md), or [reinstall or update](../consume-packages/reinstalling-and-updating-packages.md) the packages. In Visual Studio, the Package Manager Console provides several options for reinstalling packages. For more information, see [Use Package-Update](reinstalling-and-updating-packages.md#using-update-package).
+If you have missing packages or package-related errors after you run Package Restore, such as error icons in Solution Explorer, follow the instructions in [Troubleshooting Package Restore errors](package-restore-troubleshooting.md), or [reinstall or update](../consume-packages/reinstalling-and-updating-packages.md) the packages. In Visual Studio, the Package Manager Console provides several options for reinstalling packages. For more information, see [Use Package-Update](reinstalling-and-updating-packages.md#update-package-command).
 
 <a name="restore-using-visual-studio"></a>
 ## Restore packages in Visual Studio
@@ -154,7 +154,7 @@ Azure DevOps Server and TFS 2013 and later automatically restore packages during
 
 NuGet restore through any method honors any version constraints you specify in *packages.config* or the project file.
 
-- In *packages.config*, you can specify an `allowedVersions` range in the dependency. For more information, see [Constrain upgrade versions](../consume-packages/reinstalling-and-updating-packages.md#constraining-upgrade-versions). For example:
+- In *packages.config*, you can specify an `allowedVersions` range in the dependency. For more information, see [Constraints on upgrade versions](../consume-packages/reinstalling-and-updating-packages.md#constraints-on-upgrade-versions). For example:
 
   ```xml
   <package id="Newtonsoft.json" version="6.0.4" allowedVersions="[6,7)" />

docs/consume-packages/Reinstalling-and-Updating-Packages.md

@@ -25,7 +25,7 @@ Visual Studio 2017 Version 15.7 and later supports migrating a project from the
 * Migration is not currently available for C++ and ASP.NET projects.
 * Some packages may not be fully compatible with PackageReference. For more information, see [package compatibility issues](#package-compatibility-issues).
 
-In addition, there are some differences in how PackageReferences work compared to packages.config. For example, [constraining upgrade versions](../consume-packages/reinstalling-and-updating-packages.md#constraining-upgrade-versions) is not supported by PackageReference, but PackageReference adds support for [Floating Versions](../consume-packages/package-references-in-project-files.md#floating-versions).
+In addition, there are some differences in how PackageReferences work compared to packages.config. For example, [Constraints on upgrade versions](../consume-packages/reinstalling-and-updating-packages.md#constraints-on-upgrade-versions) is not supported by PackageReference, but PackageReference adds support for [Floating Versions](../consume-packages/package-references-in-project-files.md#floating-versions).
 
 ### Known Issues
 

docs/consume-packages/migrate-packages-config-to-package-reference.md

@@ -3,7 +3,7 @@ title: Create NuGet Packages for the UWP Platform (C#)
 description: An end-to-end walkthrough of creating NuGet packages using a Windows Runtime Component for the Universal Windows Platform in C#.
 author: rrelyea
 ms.author: rrelyea
-ms.date: 02/28/2020
+ms.date: 11/01/2023
 ms.topic: tutorial
 ---
 
@@ -15,45 +15,46 @@ In this walkthrough you create a NuGet package with a C# UWP component (includin
 
 ## Prerequisites
 
-1. Visual Studio 2019. Install the 2019 Community edition for free from [visualstudio.com](https://www.visualstudio.com/); you can use the Professional and Enterprise editions as well.
+1. Visual Studio 2019. Install the 2019 Community edition for free from [visualstudio.com](https://www.visualstudio.com/). You can also use the Professional and Enterprise editions.
 
-1. NuGet CLI. Download the latest version of `nuget.exe` from [nuget.org/downloads](https://nuget.org/downloads), saving it to a location of your choice (the download is the `.exe` directly). Then add that location to your PATH environment variable if it isn't already. [More details](../reference/nuget-exe-cli-reference.md#windows).
+1. NuGet CLI. Download the latest version of `nuget.exe` from [nuget.org/downloads](https://nuget.org/downloads) and save the tool to a location of your choice. (The download is the `.exe` file directly.) Add the tool file location to your PATH environment variable, if it isn't already. For more information, see [Installing nuget.exe](../reference/nuget-exe-cli-reference.md#installing-nugetexe).
 
 ## Create a UWP Windows Runtime component
 
-1. In Visual Studio, choose **File > New > Project**, search for "uwp c#", select the **Windows Runtime Component (Universal Windows)** template, click next, change the name to ImageEnhancer, and click Create. Accept the default values for Target Version and Minimum Version when prompted.
+1. In Visual Studio, select **File > New > Project**, and search for "uwp c#". Select the **Windows Runtime Component (Universal Windows)** template and select **Next**. Change the name to ImageEnhancer, and select **Create**. Accept the default values for Target Version and Minimum Version when prompted.
 
     ![Creating a new UWP Windows Runtime Component project](media/UWP-NewProject-CS.png)
 
-1. Right click the project in Solution Explorer, select **Add > New Item**, select **Templated Control**, change the name to AwesomeImageControl.cs, and click **Add**:
+1. Right-click the project in Solution Explorer, select **Add > New Item**, select **Templated Control**, change the name to AwesomeImageControl.cs, and select **Add**:
 
     ![Adding a new XAML Templated Control item to the project](media/UWP-NewXAMLControl-CS.png)
 
 1. Right-click the project in Solution Explorer and select **Properties.** In the Properties page, choose **Build** tab and enable **XML Documentation File**:
 
     ![Setting Generate XML Documentation Files to Yes](media/UWP-GenerateXMLDocFiles-CS.png)
 
-1. Right click the *solution* now, select **Batch Build**, check the five build boxes in the dialog as shown below. This makes sure that when you do a build, you generate a full set of artifacts for each of the target systems that Windows supports.
+1. Right-click the *solution* and select **Batch Build**. Select the five build boxes, as shown in the following image. This makes sure that when you do a build, you generate a full set of artifacts for each of the target systems that Windows supports.
 
     ![Batch Build](media/UWP-BatchBuild-CS.png)
 
-1. In the Batch Build dialog, and click **Build** to verify the project and create the output files that you need for the NuGet package.
+1. In the Batch Build dialog, and select **Build** to verify the project and create the output files that you need for the NuGet package.
 
 > [!Note]
 > In this walkthrough you use the Debug artifacts for the package. For non-debug package, check the Release options in the Batch Build dialog instead, and refer to the resulting Release folders in the steps that follow.
 
 ## Create and update the .nuspec file
 
-To create the initial `.nuspec` file, do the three steps below. The sections that follow then guide you through other necessary updates.
+To create the initial `.nuspec` file, complete the following steps. The subsequent sections guide you through other necessary updates.
 
-1. Open a command prompt and navigate to the folder containing `ImageEnhancer.csproj` (this will be a subfolder below where the solution file is).
-1. Run the [`NuGet spec`](../reference/cli-reference/cli-ref-spec.md) command to generate `ImageEnhancer.nuspec` (the name of the file is taken from the name of the `.csroj` file):
+1. Open a command prompt and browse to the folder that contains the `ImageEnhancer.csproj` file, which should be a subfolder of the folder that contains the solution file.
+
+1. Run the [`NuGet spec`](../reference/cli-reference/cli-ref-spec.md) command to generate the `ImageEnhancer.nuspec` file. The name of the file is taken from the name of the `.csroj` file.
 
     ```cli
     nuget spec
     ```
 
-1. Open `ImageEnhancer.nuspec` in an editor and update it to match the following, replacing YOUR_NAME with an appropriate value. Do not leave any of the $propertyName$ values. The `<id>` value, specifically, must be unique across nuget.org (see the naming conventions described in [Creating a package](../create-packages/creating-a-package.md#choose-a-unique-package-identifier-and-setting-the-version-number)). Also note that you must also update the author and description tags or you get an error during the packing step.
+1. Open `ImageEnhancer.nuspec` in an editor and update it to match the following, replacing YOUR_NAME with an appropriate value. Don't leave any of the $propertyName$ values. The `<id>` value, specifically, must be unique across nuget.org (see the naming conventions described in [Creating a package](../create-packages/creating-a-package.md#choose-a-unique-package-identifier-and-setting-the-version-number)). Also note that you must also update the author and description tags or you get an error during the packing step.
 
     ```xml
     <?xml version="1.0"?>

docs/guides/Create-UWP-Packages-CS.md

@@ -1,30 +1,53 @@
-#### Windows
+---
+title: Include
+description: Installation steps for the nuget.exe CLI tool on Windows, macOS, and Linux.
+author: JonDouglas
+ms.author: jodou
+ms.date: 11/03/2023
+ms.topic: include
+---
 
-> [!Note]
-> NuGet.exe 5.0 and later require .NET Framework 4.7.2 or later to execute.
+# [Windows](#tab/windows)
 
-1. Visit [nuget.org/downloads](https://nuget.org/downloads) and select NuGet 3.3 or higher (2.8.6 is not compatible with Mono). The latest version is always recommended, and 4.1.0+ is required to publish packages to nuget.org.
-1. Each download is the `nuget.exe` file directly. Instruct your browser to save the file to a folder of your choice. The file is *not* an installer; you won't see anything if you run it directly from the browser.
-1. Add the folder where you placed `nuget.exe` to your PATH environment variable to use the CLI tool from anywhere.
+Always install the **latest** version of the tool that supports your configuration.
 
-#### macOS/Linux
+- You can download the latest recommended version at `https://dist.nuget.org/win-x86-commandline/latest/nuget.exe`.
+- If you already have the `nuget.exe` CLI tool installed, you can update the tool to the latest version with the command `nuget update -self`.
+- For compatibility with older continuous integration systems, a previous URL, `https://nuget.org/nuget.exe` currently provides the [deprecated version 2.8.6](https://github.com/NuGet/NuGetGallery/issues/5381) of the CLI tool.
 
-Behaviors may vary slightly by OS distribution.
+1. Visit [nuget.org/downloads](https://nuget.org/downloads) and download NuGet version 3.3 or later.
 
-1. Install [Mono 4.4.2 or later](https://www.mono-project.com/docs/getting-started/install/).
+   - Version 5.0 and later requires the .NET Framework version 4.7.2 or later.
+   - Version 4.1.0 and later is required to publish packages to `nuget.org`.
+   - Version 2.8.6 isn't compatible with [Mono](https://www.mono-project.com/docs/getting-started/install/).
+
+1. Each download is the `nuget.exe` file directly. Instruct your browser to save the file to a folder of your choice. The download file isn't an installer, so you don't see anything if you run the file directly from the browser.
+
+1. To use the CLI tool from anywhere, add the folder location for the `nuget.exe` file to your PATH environment variable.
+
+# [macOS / Linux](#tab/macos+linux)
+
+Behaviors can vary slightly based on your operating system distribution.
+
+> [!NOTE]
+> Visual Studio for Mac is scheduled for retirement by August 31, 2024 in accordance with [Microsoft's Modern Lifecycle Policy](/lifecycle/policies/modern). For more information, see [What's happening to Visual Studio for Mac](/visualstudio/mac/what-happened-to-vs-for-mac).
+
+1. Install [Mono version 4.4.2 or later](https://www.mono-project.com/docs/getting-started/install/).
 
 1. Execute the following command at a shell prompt:
 
-    ```bash
-    # Download the latest stable `nuget.exe` to `/usr/local/bin`
-    sudo curl -o /usr/local/bin/nuget.exe https://dist.nuget.org/win-x86-commandline/latest/nuget.exe
-    ```
+   ```bash
+   # Download the latest stable `nuget.exe` to `/usr/local/bin`
+   sudo curl -o /usr/local/bin/nuget.exe https://dist.nuget.org/win-x86-commandline/latest/nuget.exe
+   ```
+
+1. Create an alias by adding the following script to the appropriate file for your operating system (typically `~/.bash_aliases` or `~/.bash_profile`):
 
-1. Create an alias by adding the following script to the appropriate file for your OS (typically `~/.bash_aliases` or `~/.bash_profile`):
+   ```bash
+   # Create as alias for nuget
+   alias nuget="mono /usr/local/bin/nuget.exe"
+   ```
 
-    ```bash
-    # Create as alias for nuget
-    alias nuget="mono /usr/local/bin/nuget.exe"
-    ```
+1. Reload the shell. Test the installation by entering the command `nuget` with no parameters. NuGet CLI help should display.
 
-1. Reload the shell.  Test the installation by entering `nuget` with no parameters. NuGet CLI help should display.
+---