Merge pull request NuGet#636 from NuGet/master

Publish to live

Author: Kraig Brockschmidt

.openpublishing.redirection.json

@@ -0,0 +1,34 @@
+{
+    "redirections": [
+        {
+            "source_path": "docs/API/introduction.md",
+            "redirect_url": "/nuget/api/overview",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/API/NuGet-API-V3.md",
+            "redirect_url": "/nuget/reference/nuget-client-sdk",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/API/NuGet-Credential-Providers-for-Visual-Studio.md",
+            "redirect_url": "/nuget/reference/extensibility/nuget-credential-providers-for-visual-studio",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/API/nuget-exe-Credential-Providers.md",
+            "redirect_url": "/nuget/reference/extensibility/nuget-exe-credential-providers",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/Create-Packages/Dependency-Versions.md",
+            "redirect_url": "/nuget/reference/package-versioning",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/Quickstart/restore.md",
+            "redirect_url": "/nuget/consume-packages/package-restore-troubleshooting",
+            "redirect_document_id": false
+        }
+    ]
+}

README.md

@@ -17,11 +17,11 @@ NuGet follows the [.NET Foundation Contributors Code of Conduct](https://github.
 
 No contribution is too big or too small--
 
-1. Visit the page to edit on [docs.microsoft.com/nuget](https://docs.microsoft.com/en-us/nuget/), then click the **Edit** button on the top right. This brings you to the appropriate markdown page in the repo.    
+1. Visit the page to edit on [docs.microsoft.com/nuget](/en-us/nuget/), then click the **Edit** button on the top right. This brings you to the appropriate markdown page in the repo.    
 1. Edit the markdown:
     1. If you're including images (use PNGs, generally), place them in the media folder that's in the topic's folder. Links are then `media/<image_name>.png`.
     1. Relative links to other pages in this docset should be in the form `../<folder>/<topic-file>.md` including the training `.md`. If you're linking to another topic in the same folder, then `../<folder>/` can be omitted. When using anchors, always remember to include the `.md` before the `#`.
-    1. When using external links, especially to docs.microsoft.com or msdn.microsoft.com, omit any language tag like "en-us" so that a reader in another language lands on a target page in that same language if it's available.
+    1. When using external links, especially to docs.microsoft.com (or msdn.microsoft.com for any older content), omit any language tag like "en-us" so that a reader in another language lands on a target page in that same language if it's available.
 1. When you're done, enter a commit message below, and click **Propose file change**.
 1. Send a pull request for your change. We review PRs on a regular basis.
 1. Thank you!
@@ -121,16 +121,16 @@ The only case when you should use ``` without a language tag is when creating a
 
 docs.microsoft.com uses blockquotes for callouts, that is, lines starting with ">".
 
-Callout sections with ">" only will appear with a solid gray line to the left. See [Creating NuGet packages](https://docs.microsoft.com/en-us/nuget/create-packages/creating-a-package) for examples.
+Callout sections with ">" only will appear with a solid gray line to the left. See [Creating NuGet packages](/en-us/nuget/create-packages/creating-a-package) for examples.
 
 You can also use one of the following callout tags on the first line that will create a shaded callout in the indicated color:
 
 | Tag | Shading color | Topic with examples | 
 | --- | --- | --- |
-| `> [!Note]` | Light blue, use for callouts without any special emphasis. | [Creating NuGet packages](https://docs.microsoft.com/nuget/create-packages/creating-a-package) |
-| `> [!Tip]` | Green, use for callouts that share special tips and tricks or other helpful knowledge. | [Package consumption overview](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow) | 
-| `> [!Important]` | Yellow, use for callouts that describe cautions. | [NuGet.Server](https://docs.microsoft.com/nuget/hosting-packages/nuget-server) |
-| `> [!Warning]` | Red, use for callouts that warn readers about situations that could cause data loss or unexpected consequences. | [Dependency resolution](https://docs.microsoft.com/nuget/consume-packages/dependency-resolution) |
+| `> [!Note]` | Light blue, use for callouts without any special emphasis. | [Creating NuGet packages](/nuget/create-packages/creating-a-package) |
+| `> [!Tip]` | Green, use for callouts that share special tips and tricks or other helpful knowledge. | [Package consumption overview](/nuget/consume-packages/overview-and-workflow) | 
+| `> [!Important]` | Yellow, use for callouts that describe cautions. | [NuGet.Server](/nuget/hosting-packages/nuget-server) |
+| `> [!Warning]` | Red, use for callouts that warn readers about situations that could cause data loss or unexpected consequences. | [Dependency resolution](/nuget/consume-packages/dependency-resolution) |
 
 ### Links
 
@@ -139,7 +139,7 @@ You can also use one of the following callout tags on the first line that will c
 - Links to other markdown files on docs.microsoft.com are case-insensitive (unlike links to files in GitHub, which are).
 - If you're linking to another topic in the same folder, then `../<folder>/` can be omitted.
 - When using anchors, always remember to include the `.md` before the `#`.
-- When using external links, especially to docs.microsoft.com or msdn.microsoft.com, omit any language tag like "en-us" so that a reader in another language lands on a target page in that same language if it's available.
+- When using external links, especially to docs.microsoft.com (or msdn.microsoft.com for any older content), omit any language tag like "en-us" so that a reader in another language lands on a target page in that same language if it's available.
 - Bare URLs are not automatically converted into links.
 
 ### Inline HTML

docs/API/NuGet-API-V3.md

@@ -52,8 +52,8 @@ Clients are required to pass the following header when they make API calls to **
 X-NuGet-Protocol-Version: 4.1.0
 ```
 
-Note that the pre-existing `X-NuGet-Client-Version` header has the same purpose but is now deprecated and should no
-longer be used.
+Note that the `X-NuGet-Client-Version` header has similar semantics but is reserved to only be used by the official
+NuGet client. Third party clients should use the `X-NuGet-Protocol-Version` header and value.
 
 The **push** protocol itself is described in the documentation for the
 [`PackagePublish` resource](package-publish-resource.md).

docs/API/NuGet-Credential-Providers-for-Visual-Studio.md

@@ -266,7 +266,7 @@ requireLicenseAgreement | boolean                    | no       | Assume `false`
 summary                 | string                     | no       |
 tags                    | array of strings           | no       |
 title                   | string                     | no       |
-verbatimVersion         | string                     | no       | The version string as it is originally found in the .nuspec
+verbatimVersion         | string                     | no       | The version string as it's originally found in the .nuspec
 
 The package `version` property is the full, normalized version string. This means that SemVer 2.0.0 build data can
 be included here.

docs/API/NuGet-Protocols.md

@@ -31,7 +31,7 @@ The NuGet API is a set of HTTP endpoints that can be used to download packages,
 and perform most other operations available in the official NuGet clients.
 
 This API is used by the NuGet client in Visual Studio, nuget.exe, and the .NET CLI to perform NuGet operations such as
-[`dotnet restore`](https://docs.microsoft.com/dotnet/articles/core/preview3/tools/dotnet-restore), search in the Visual
+[`dotnet restore`](/dotnet/articles/core/preview3/tools/dotnet-restore), search in the Visual
 Studio UI, and [`nuget.exe push`](../tools/cli-ref-push.md).
 
 Note in some cases, nuget.org has additional requirements that are not enforced by other package sources. These
@@ -62,7 +62,7 @@ version string's minor version will be increased.
 Older clients (such as nuget.exe 2.x) do not support the V3 API and only support the older V2 API, which is not
 documented here.
 
-The NuGet V3 API is named as such because it is the successor of the V2 API, which was the OData-based protocol
+The NuGet V3 API is named as such because it's the successor of the V2 API, which was the OData-based protocol
 implemented by the 2.x version of the official NuGet client. The V3 API was first supported by the 3.0 version of the
 official NuGet client and is still the latest major protocol version supported by the NuGet client, 4.0 and on. 
 

docs/API/catalog-resource.md

@@ -71,8 +71,7 @@ Name     | In     | Type    | Required | Notes
 LOWER_ID | URL    | string  | yes      | The package ID, lowercase
 
 The `LOWER_ID` value is the desired package ID lowercased using the rules implemented by .NET's
-[`System.String.ToLowerInvariant()`](https://msdn.microsoft.com/en-us/library/system.string.tolowerinvariant.aspx)
-method.
+[`System.String.ToLowerInvariant()`](/dotnet/api/system.string.tolowerinvariant?view=netstandard-2.0#System_String_ToLowerInvariant) method.
 
 ### Response
 
@@ -119,7 +118,7 @@ LOWER_ID      | URL    | string | yes      | The package ID, lowercase
 LOWER_VERSION | URL    | string | yes      | The package version, normalized and lowercased
 
 Both `LOWER_ID` and `LOWER_VERSION` are lowercased using the rules implemented by .NET's
-[`System.String.ToLowerInvariant()`](https://msdn.microsoft.com/en-us/library/system.string.tolowerinvariant.aspx)
+[`System.String.ToLowerInvariant()`](/dotnet/api/system.string.tolowerinvariant?view=netstandard-2.0#System_String_ToLowerInvariant)
 method.
 
 The `LOWER_VERSION` is the desired package version normalized using NuGet's version
@@ -160,8 +159,7 @@ LOWER_ID      | URL    | string  | yes      | The package ID, lowercase
 LOWER_VERSION | URL    | integer | yes      | The package version, normalized and lowercased
 
 Both `LOWER_ID` and `LOWER_VERSION` are lowercased using the rules implemented by .NET's
-[`System.String.ToLowerInvariant()`](https://msdn.microsoft.com/en-us/library/system.string.tolowerinvariant.aspx)
-method.
+[`System.String.ToLowerInvariant()`](/dotnet/api/system.string.tolowerinvariant?view=netstandard-2.0#System_String_ToLowerInvariant) method.
 
 The `LOWER_VERSION` is the desired package version normalized using NuGet's version
 [normalization rules](../reference/package-versioning.md#normalized-version-numbers). This means that build metadata