Update links to NuGet documentation

Also a couple tweaks to say "a Nuget package" rather than just "a NuGet"

Author: Kraig Brockschmidt

docs/extensibility/how-to-migrate-extensibility-projects-to-visual-studio-2015.md

@@ -55,7 +55,7 @@ Here's how to upgrade your extension.
 
 2.  Remove the VS SDK reference assemblies from the project by selecting them, right click and **Remove**.  
 
-3.  Add the NuGet versions of the VS SDK reference assemblies.  While still in the **Solution Explorer References** node, open the **Manage NuGet Packages...** dialog.  If you want to learn more about this dialog, see [Manage NuGet Packages Using the Dialog](http://docs.nuget.org/Consume/Package-Manager-Dialog). The VS SDK reference assemblies are published on [nuget.org](http://www.nuget.org) by [VisualStudioExtensibility](http://www.nuget.org/profiles/VisualStudioExtensibility).  
+3.  Add the NuGet versions of the VS SDK reference assemblies.  While still in the **Solution Explorer References** node, open the **Manage NuGet Packages...** dialog.  If you want to learn more about this dialog, see [Package Manager UI](http://docs.microsoft.com/NuGet/Tools/Package-Manager-UI). The VS SDK reference assemblies are published on [nuget.org](http://www.nuget.org) by [VisualStudioExtensibility](http://www.nuget.org/profiles/VisualStudioExtensibility).  
 
 4.  Using **nuget.org** as your **Package Source**, search for the NuGet package name which matches the desired reference assembly (for example: Microsoft.VisualStudio.Shell.14.0) and install it in your project.  NuGet may add multiple reference assemblies in order to satisfy the initial assembly's dependencies.  
 

docs/extensibility/signing-vsix-packages.md

@@ -48,7 +48,7 @@ Extension assemblies do not need to be signed before they can run in Visual Stud
 
 1.  Add your VSIX to a project.  
 
-2.  Right click on the project node in Solution Explorer, selecting **Add | Manage NuGet Packages**.  For more information on NuGet and adding NuGet packages see [NuGet Overview](http://docs.nuget.org/) and [Manage NuGet Packages Using the Dialog](http://docs.nuget.org/Consume/Package-Manager-Dialog).  
+2.  Right click on the project node in Solution Explorer, selecting **Add | Manage NuGet Packages**.  For more information on NuGet and adding NuGet packages see see the [NuGet documentation](http://docs.microsoft.com/NuGet) and [Package Manager UI](http://docs.microsoft.com/NuGet/Tools/Package-Manager-UI) topics.  
 
 3.  Search for VSIXSignTool from VisualStudioExtensibility and install the NuGet package.  
 

docs/extensibility/what-s-new-in-the-visual-studio-2015-sdk.md

@@ -62,7 +62,7 @@ The Visual Studio SDK has the following new and updated features for Visual Stud
  For C++, the VSPackage Wizard support menu commands, tool windows, and custom editors. Look for it in the **New Project** dialog in **Visual C++ / Extensibility**.  
 
 ## VS SDK Reference Assemblies via NuGet  
- For increased portability and sharing of extensibility projects, you can use the NuGet versions of the VS SDK reference assemblies.  These are available on [nuget.org](http://www.nuget.org) published by [VisualStudioExtensibility](http://www.nuget.org/profiles/VisualStudioExtensibility) and can be easily added to your project or solution through the Visual Studio **References / Manage NuGet Packages** dialog. You can add individual references to specific extensibility assemblies or add all the VS SDK references assemblies at once using the VS SDK [Meta package](http://www.nuget.org/packages/VSSDK_Reference_Assemblies). To learn more about NuGet, see [NuGet Overview](http://docs.nuget.org/) and [Manage NuGet Packages Using the Dialog](http://docs.nuget.org/Consume/Package-Manager-Dialog).  
+ For increased portability and sharing of extensibility projects, you can use the NuGet versions of the VS SDK reference assemblies.  These are available on [nuget.org](http://www.nuget.org) published by [VisualStudioExtensibility](http://www.nuget.org/profiles/VisualStudioExtensibility) and can be easily added to your project or solution through the Visual Studio **References / Manage NuGet Packages** dialog. You can add individual references to specific extensibility assemblies or add all the VS SDK references assemblies at once using the VS SDK [Meta package](http://www.nuget.org/packages/VSSDK_Reference_Assemblies). To learn more about NuGet, see the [NuGet documentation](http://docs.microsoft.com/NuGet) and [Package Manager UI](http://docs.microsoft.com/NuGet/Tools/Package-Manager-UI) topics.  
 
  When you use the NuGet versions of the VS SDK reference assemblies, another user doesn't need to install the VS SDK to open and build your project.  The NuGet reference assemblies and VS SDK build tools will automatically be installed on their computer for that project.  
 

docs/ide/adding-references-using-nuget-versus-an-extension-sdk.md

@@ -31,7 +31,7 @@ translation.priority.ht:
 # Adding References Using NuGet Versus an Extension SDK
 You can provide a package for consumption within Visual Studio projects by using either the NuGet extension to Visual Studio or a software development kit (SDK). By describing the similarities and differences between the two mechanisms, this topic can help you choose the best one for your task.  
 
--   NuGet is an open-source, package-management system that simplifies the process of incorporating libraries into a project solution. For more information, see [NuGet Overview](http://go.microsoft.com/fwlink/?LinkId=254877).  
+-   NuGet is an open-source, package-management system that simplifies the process of incorporating libraries into a project solution. For more information, see the [NuGet documentation](http://docs.microsoft.com/nuget).  
 
 -   An SDK is a collection of files that Visual Studio treats as a single reference item. The **Reference Manager** dialog box lists all SDKs that are relevant to the project that's open when you display that dialog box. When you add an SDK to a project, you can access all of the contents of that SDK through IntelliSense, the **Toolbox**, designers, the **Object Browser**, MSBuild, deployment, debugging, and packaging. For more information about SDKs, see [Creating a Software Development Kit](../extensibility/creating-a-software-development-kit.md).  
 

mac/TOC.md

@@ -19,7 +19,7 @@
 ## [Adding and removing Project Items](add-and-remove-project-items.md)
 ## [Managing Solutions and Project properties](managing-solutions-and-project-properties.md)
 ## [Managing references in a project](managing-references-in-a-project.md)
-### [Walkthrough - Including a NuGet in your project](nuget-walkthrough.md)
+### [Walkthrough - Including a NuGet package in your project](nuget-walkthrough.md)
 ## [Managing App Resources](managing-app-resources.md)
 
 # [Source Editor](source-editor.md)

mac/ide-tour.md

@@ -73,7 +73,7 @@ To add a dependency to your application, right click on the Dependencies / Packa
 
 ![Add a NuGet package](media/ide-tour-image21.png)
 
-Information on using a NuGet package in an application can be found in the [Including a NuGet in your project](~/nuget-walkthrough.md) topic.
+Information on using a NuGet package in an application can be found in the [Including a NuGet project in your project](~/nuget-walkthrough.md) topic.
 
 ## Refactoring
 

mac/managing-references-in-a-project.md

@@ -37,4 +37,4 @@ NuGet is the most popular package manager for .NET development. Visual Studio fo
 
 To do this, right-click on the **Package** folder in the Solution Pad, and select Add Packages.
 
-More information on using a NuGet Package is provided in the [Including NuGet in your Project](~/nuget-walkthrough.md) walkthrough.
+More information on using a NuGet Package is provided in the [Including a NuGet package in your Project](~/nuget-walkthrough.md) walkthrough.

mac/nuget-walkthrough.md

@@ -1,5 +1,5 @@
 ---
-title: "Walkthrough - Including a NuGet in your project"
+title: "Walkthrough - Including a NuGet package in your project"
 description: This document covers how to include a NuGet package in a Xamarin project. It walks through finding and downloading a package, as well as introducing the IDE integration features.
 author: asb3993
 ms.author: amburns
@@ -8,7 +8,7 @@ ms.topic: article
 ms.assetid: 5C800815-0B13-4B27-B017-95FCEF1A0EA2
 ---
 
-# Including a NuGet in your project
+# Including a NuGet package in your project
 
 NuGet is the most popular package manager for .NET development and is built in to Visual Studio for Mac and Visual Studio on Windows. You can search for and add packages to your Xamarin.iOS and Xamarin.Android projects using either IDE.
 
@@ -49,7 +49,7 @@ Once the package has been downloaded it will be added to your project. The solut
 
 *   The **References** node will contain a list of all the assemblies that are part of a NuGet package.
 *   The **Packages** node displays each NuGet package that you have downloaded. You can update or remove a package from this list.
-*   A **packages.config** file will be added to the project. This XML file is used by the IDE to track which package versions are referenced in this project. This file should not be hand-edited, but you should keep it in version control. Note that a project.json file can be used instead of a packages.config file. The project.json file is a new package file format introduced with NuGet 3, which supports transitive restore. More detailed information on project.json can be found in the [NuGet documentation](http://docs.nuget.org/consume/ProjectJson-Intro). The project.json file needs to be added manually and the project closed and re-opened before the project.json file is used in Visual Studio for Mac.
+*   A **packages.config** file will be added to the project. This XML file is used by the IDE to track which package versions are referenced in this project. This file should not be hand-edited, but you should keep it in version control. Note that a project.json file can be used instead of a packages.config file. The project.json file is a new package file format introduced with NuGet 3, which supports transitive restore. More detailed information on project.json can be found in the [NuGet documentation](http://docs.microsoft.com/NuGet/Schema/Project-Json). The project.json file needs to be added manually and the project closed and re-opened before the project.json file is used in Visual Studio for Mac.
 
 ## Using NuGet Packages
 
@@ -107,7 +107,7 @@ Different sources can then be selected when searching for packages:
 
 ## Version Control
 
-The NuGet documentation discusses [using NuGet without committing packages to source control](http://docs.nuget.org/docs/workflows/using-nuget-without-committing-packages). If you prefer not to store binaries and unused information in source control, you can configure the Visual Studio for Mac to automatically restore packages from the server. This means that when a developer retrieves the project from source control for the first time, the Visual Studio for Mac will automatically download and install the required packages.
+The NuGet documentation discusses [using NuGet without committing packages to source control](https://docs.microsoft.com/nuget/consume-packages/packages-and-source-control). If you prefer not to store binaries and unused information in source control, you can configure the Visual Studio for Mac to automatically restore packages from the server. This means that when a developer retrieves the project from source control for the first time, the Visual Studio for Mac will automatically download and install the required packages.
 
 ![Automatically restore packages](media/nuget-walkthrough-AutoRestore.png)