Freshness Edit: NuGet (#3548)

* Refresh article and screenshots

* Refresh article

* Refresh article

* Address warnings by fixing bookmarks; adjust formatting and language

* Address Copilot review: Adjust link capitalization; expand read-me section

* Address PR comment: fix path

Author: JKirsch1

docs/create-packages/Creating-a-Package.md

@@ -63,7 +63,7 @@ This guide walks you through creating a NuGet package targeting .NET Standard Li
     nuget spec
     ```
 
-1. Open `AppLogger.nuspec` in an editor and update it to match the following, replacing YOUR_NAME with an appropriate value. 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 `AppLogger.nuspec` in an editor and update it to match the following, replacing YOUR_NAME with an appropriate value. 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-set-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/create-packages/media/Create_01-ShowReadme.png

@@ -54,7 +54,7 @@ To create the initial `.nuspec` file, complete the following steps. The subseque
     nuget spec
     ```
 
-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.
+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-set-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/create-packages/media/package-read-me-file.png

@@ -53,7 +53,7 @@ To create the initial `.nuspec` file, do the three steps below. The sections tha
     nuget spec
     ```
 
-1. Open `ImageEnhancer.nuspec` in an editor and update it to match the following, replacing YOUR_NAME with an appropriate value. 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. 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-set-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-NET-Standard-Packages-VS2015.md

@@ -78,7 +78,7 @@ Although the following elements are the minimum requirements for a package, you
 These elements must appear within a `<metadata>` element.
 
 #### id 
-The case-insensitive package identifier, which must be unique across nuget.org or whatever gallery the package resides in. IDs may not contain spaces or characters that are not valid for a URL, and generally follow .NET namespace rules. See [Choosing a unique package identifier](../create-packages/Creating-a-Package.md#choose-a-unique-package-identifier-and-setting-the-version-number) for guidance.
+The case-insensitive package identifier, which must be unique across nuget.org or whatever gallery the package resides in. IDs may not contain spaces or characters that are not valid for a URL, and generally follow .NET namespace rules. See [Choosing a unique package identifier](../create-packages/Creating-a-Package.md#choose-a-unique-package-identifier-and-set-the-version-number) for guidance.
 
 When uploading a package to nuget.org, the `id` field is limited to 128 characters.