jjanuszkiewicz
diff --git a/‎docs/TOC.md
Lines changed: 4 additions & 3 deletions b/‎docs/TOC.md
Lines changed: 4 additions & 3 deletions
diff --git a/‎docs/api/overview.md
Lines changed: 5 additions & 4 deletions b/‎docs/api/overview.md
Lines changed: 5 additions & 4 deletions
diff --git a/‎docs/api/symbol-package-publish-resource.md
Lines changed: 78 additions & 0 deletions b/‎docs/api/symbol-package-publish-resource.md
Lines changed: 78 additions & 0 deletions
diff --git a/‎docs/consume-packages/Overview-and-Workflow.md
Lines changed: 1 addition & 1 deletion b/‎docs/consume-packages/Overview-and-Workflow.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/consume-packages/Package-Restore.md
Lines changed: 4 additions & 4 deletions b/‎docs/consume-packages/Package-Restore.md
Lines changed: 4 additions & 4 deletions
diff --git a/‎docs/consume-packages/Package-restore-troubleshooting.md
Lines changed: 1 addition & 1 deletion b/‎docs/consume-packages/Package-restore-troubleshooting.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/create-packages/Creating-a-Package.md
Lines changed: 4 additions & 4 deletions b/‎docs/create-packages/Creating-a-Package.md
Lines changed: 4 additions & 4 deletions
diff --git a/‎docs/create-packages/Source-and-Config-File-Transformations.md
Lines changed: 1 addition & 1 deletion b/‎docs/create-packages/Source-and-Config-File-Transformations.md
Lines changed: 1 addition & 1 deletion
@@ -24,10 +24,10 @@
 ## [Source and config file transformations](create-packages/source-and-config-file-transformations.md)
 ## [Creating localized packages](create-packages/creating-localized-packages.md)
 ## [Prerelease packages](create-packages/prerelease-packages.md)
-## [Native packages](create-packages/native-packages.md)
-## [Symbol packages](create-packages/symbol-packages.md)
+## [Creating Native packages](create-packages/native-packages.md)
+## [Creating Symbol packages](create-packages/symbol-packages-snupkg.md)
 ## [Signing packages](create-packages/sign-a-package.md)
-## [Publish a package](create-packages/publish-a-package.md)
+## [Publishing a package](create-packages/publish-a-package.md)
 ## Guides
 ### [Create UWP packages](guides/create-uwp-packages.md)
 ### [Creating UI controls as NuGet packages](guides/create-UI-controls.md)
@@ -198,6 +198,7 @@
 ## [How-to: query for all packages using the API](guides/api/query-for-all-published-packages.md)
 ## [Service index](api/service-index.md)
 ## [Push and delete](api/package-publish-resource.md)
+## [Push symbol packages](api/symbol-package-publish-resource.md)
 ## [Search](api/search-query-service-resource.md)
 ## [Autocomplete](api/search-autocomplete-service-resource.md)
 ## [Package metadata](api/registration-base-url-resource.md)
 
@@ -53,16 +53,17 @@ Non-breaking protocol changes have been made to the API since it was first relea
 
 The **service index** describes a variety of resources. The current set of supported resources are as follows:
 
-Resource name                                                          | Required | Description
----------------------------------------------------------------------- | -------- | -----------
+Resource name                                                           | Required | Description
+----------------------------------------------------------------------  | -------- | -----------
 [`PackagePublish`](package-publish-resource.md)                        | yes      | Push and delete (or unlist) packages.
 [`SearchQueryService`](search-query-service-resource.md)               | yes      | Filter and search for packages by keyword.
 [`RegistrationsBaseUrl`](registration-base-url-resource.md)            | yes      | Get package metadata.
 [`PackageBaseAddress`](package-base-address-resource.md)               | yes      | Get package content (.nupkg).
 [`SearchAutocompleteService`](search-autocomplete-service-resource.md) | no       | Discover package IDs and versions by substring.
 [`ReportAbuseUriTemplate`](report-abuse-resource.md)                   | no       | Construct a URL to access a "report abuse" web page.
-[`RepositorySignatures`](repository-signatures-resource.md)            | no       | Get certificates used for repository signing.
-[`Catalog`](catalog-resource.md)                                       | no       | Full record of all package events.
+[`RepositorySignatures`](repository-signatures-resource.md)             | no      | Get certificates used for repository signing.
+[`Catalog`](catalog-resource.md)                                         | no      | Full record of all package events.
+[`SymbolPackagePublish`](symbol-package-publish-resource.md)            | no      | Push symbol packages.
 
 In general, all non-binary data returned by a API resource are serialized using JSON. The response schema
 returned by each resource in the service index is defined individually for that resource. For more information about
 
@@ -0,0 +1,78 @@
+---
+title: Push Symbol Packages, NuGet API | Microsoft Docs
+author:
+- cristinamanum
+- kraigb
+ms.author:
+- cmanu
+- kraigb
+manager: skofman
+ms.date: 10/30/2018
+ms.topic: reference
+ms.prod: nuget
+ms.technology: null
+description: The publish service allows clients to publish new symbol packages.
+keywords: NuGet API push symbol package
+ms.reviewer: karann
+---
+
+# Push Symbol Packages
+
+It is possible to push symbols packages ([snupkg](../create-packages/Symbol-Packages-snupkg.md)) using the NuGet V3 API.
+These operations are based off of the `SymbolPackagePublish` resource found in the [service index](service-index.md).
+
+## Versioning
+
+The following `@type` value is used:
+
+@type value                 | Notes
+--------------------        | -----
+SymbolPackagePublish/4.9.0  | The initial release
+
+## Base URL
+
+The base URL for the following APIs is the value of the `@id` property of the `SymbolPackagePublish/4.9.0` resource in the
+package source's [service index](service-index.md). For the documentation below, nuget.org's URL is used. Consider 
+`https://www.nuget.org/api/v2/symbolpackage` as a placeholder for the `@id` value found in the service index.
+
+## HTTP methods
+
+The `PUT` HTTP method is supported by this resource. 
+
+## Push a symbol package
+
+nuget.org supports pushing new symbol packages format ([snupkg](../create-packages/Symbol-Packages-snupkg.md)) using the following API. 
+
+    PUT https://www.nuget.org/api/v2/symbolpackage
+
+Symbol packages with the same ID and version
+can be submitted multiple times. A symbol package will be rejected in the following cases.
+- A package with the same ID and version does not exist.
+- A symbol package with the same ID and version was pushed but is not yet published.
+- The symbol package ([snupkg](../create-packages/Symbol-Packages-snupkg.md)) is invalid (see [symbol package constraints](../create-packages/Symbol-Packages-snupkg.md)).
+
+### Request parameters
+
+Name           | In     | Type   | Required | Notes
+-------------- | ------ | ------ | -------- | -----
+X-NuGet-ApiKey | Header | string | yes      | For example, `X-NuGet-ApiKey: {USER_API_KEY}`
+
+The API key is an opaque string gotten from the package source by the user and configured into the client. No
+particular string format is mandated but the length of the API key should not exceed a reasonable size for HTTP header
+values.
+
+### Request body
+
+The request body for the symbol push is same as with the request body of a package push request (see [package push and delete](package-publish-resource.md)). 
+
+### Response
+
+Status Code | Meaning
+----------- | -------
+201         | The symbol package was successfully pushed.
+400         | The provided symbol package is invalid.
+401         | The user is not authorized to perform this action.
+404         | A corresponding package with the provided ID and version does not exist.
+409         | A symbol package with the provided ID and version was pushed but it is not available yet.
+413         | The package is too large.
+
@@ -13,7 +13,7 @@ Between nuget.org and private package galleries that your organization might est
 
 ![Flow of going to a package source, finding a package, installing it in a project, then adding a using statement and calls to the package API](media/Overview-01-GeneralFlow.png)
 
-\* _Visual Studio and dotnet.ex` only. The nuget install command does not modify project files or packages.config; entries must be managed manually._
+\* _Visual Studio and `dotnet.exe` only. The `nuget install` command does not modify project files or the `packages.config` file; entries must be managed manually._
 
 For further details, see [Finding and Choosing Packages](../consume-packages/finding-and-choosing-packages.md) and [Different ways to install a NuGet package](ways-to-install-a-package.md).
 
 
@@ -57,9 +57,9 @@ Package restore is primarily enabled through **Tools > Options > NuGet Package M
         </packageRestore>
     </configuration>
     ```
-    <br/>
-    > [!Note]
-    >  The `packageRestore/enabled` setting can be overridden globally by setting an environment variable called **EnableNuGetPackageRestore** with a value of TRUE or FALSE before launching Visual Studio or starting a build.
+
+> [!Note]
+>  The `packageRestore/enabled` setting can be overridden globally by setting an environment variable called **EnableNuGetPackageRestore** with a value of TRUE or FALSE before launching Visual Studio or starting a build.
 
 - **Automatically check for missing packages during build in Visual Studio**: controls automatic restore by changing the `packageRestore/automatic` setting in the `NuGet.Config` file as shown below (`%AppData%\NuGet\NuGet.Config` on Windows, `~/.nuget/NuGet/NuGet.Config` on Mac/Linux). When this option is set, running a build from Visual Studio automatically restores any missing packages. The option does not affect builds run from the command line using MSBuild.
 
@@ -120,4 +120,4 @@ To avoid using the cache for HTTP sources, do one of the following:
 
 ## Troubleshooting
 
-See [Troubleshooting package restore](package-restore-troubleshooting.md).
+See [Troubleshooting package restore](package-restore-troubleshooting.md).
@@ -37,7 +37,7 @@ This project references NuGet package(s) that are missing on this computer.
 Use NuGet Package Restore to download them. The missing file is {name}.
 ```
 
-This error occurs you attempt to build a project that contains references to one or more NuGet packages, but those packages are not presently installed on the computer or in the project.
+This error occurs when you attempt to build a project that contains references to one or more NuGet packages, but those packages are not presently installed on the computer or in the project.
 
 - When using the PackageReference management format, the error means that the package is not installed in the *global-packages* folder as described on [Managing the global packages and cache folders](managing-the-global-packages-and-cache-folders.md).
 - When using `packages.config`, the error means that the package is not installed in the `packages` folder at the solution root.
 
@@ -46,7 +46,7 @@ Required properties:
 
 - The package identifier, which must be unique across the gallery that hosts the package.
 - A specific version number in the form *Major.Minor.Patch[-Suffix]* where *-Suffix* identifies [pre-release versions](prerelease-packages.md)
-- The package title as it should appears on the host (like nuget.org)
+- The package title as it should appear on the host (like nuget.org)
 - Author and owner information.
 - A long description of the package.
 
@@ -152,7 +152,7 @@ You then edit the file by hand so that it describes the exact content you want i
 
 ### From a convention-based working directory
 
-Because a NuGet package is just a ZIP file that's been renamed with the `.nupkg` extension, its often easiest to create the folder structure you want on your local file system, then create the `.nuspec` file directly from that structure. The `nuget pack` command then automatically adds all files in that folder structure (excluding any folders that begin with `.`, allowing you keep private files in the same structure).
+Because a NuGet package is just a ZIP file that's been renamed with the `.nupkg` extension, it's often easiest to create the folder structure you want on your local file system, then create the `.nuspec` file directly from that structure. The `nuget pack` command then automatically adds all files in that folder structure (excluding any folders that begin with `.`, allowing you to keep private files in the same structure).
 
 The advantage to this approach is that you don't need to specify in the manifest which files you want to include in the package (as explained later in this topic). You can simply have your build process produce the exact folder structure that goes into the package, and you can easily include other files that might not be part of a project otherwise:
 
@@ -172,7 +172,7 @@ The folder conventions are as follows:
 | build | MSBuild `.targets` and `.props` files | Automatically inserted into the project file or `project.lock.json` (NuGet 3.x+). |
 | tools | Powershell scripts and programs accessible from the Package Manager Console | The `tools` folder is added to the `PATH` environment variable for the Package Manager Console only (Specifically, *not* to the `PATH` as set for MSBuild when building the project). |
 
-Because your folder structure can contain any number of assemblies for any number of target frameworks, this method is necessary when creating packages that support multiple frameworks 
+Because your folder structure can contain any number of assemblies for any number of target frameworks, this method is necessary when creating packages that support multiple frameworks.
 
 In any case, once you have the desired folder structure in place, run the following command in that folder to create the `.nuspec` file:
 
@@ -316,7 +316,7 @@ When you include a file named `readme.txt` in the package root, Visual Studio di
 
 In some cases, you might want to add custom build targets or properties in projects that consume your package, such as running a custom tool or process during build. You do this by placing files in the form `<package_id>.targets` or `<package_id>.props` (such as `Contoso.Utility.UsefulStuff.targets`) within the `\build` folder of the project.
 
-Files in the root `\build` folder are considered suitable for all target frameworks. To provide framework-specific files, first place those within appropriate subfolders, such as the following:
+Files in the root `\build` folder are considered suitable for all target frameworks. To provide framework-specific files, first place them within appropriate subfolders, such as the following:
 
     \build
         \netstandard1.4
 
@@ -109,7 +109,7 @@ To see the effect of installing and uninstalling the package, create a new ASP.N
 
 ### XDT transforms
 
-You can modify config files using [XDT syntax](https://msdn.microsoft.com/library/dd465326.aspx). You can also have NuGet replace tokens with [project properties](/dotnet/api/vslangproj.projectproperties?view=visualstudiosdk-2017&viewFallbackFrom=netframework-4.7) by including the property name within `$` delimeters (case-insensitive).
+You can modify config files using [XDT syntax](https://msdn.microsoft.com/library/dd465326.aspx). You can also have NuGet replace tokens with [project properties](/dotnet/api/vslangproj.projectproperties?view=visualstudiosdk-2017&viewFallbackFrom=netframework-4.7) by including the property name within `$` delimiters (case-insensitive).
 
 For example, the following `app.config.install.xdt` file will insert an `appSettings` element into `app.config` containing the `FullPath`, `FileName`, and `ActiveConfigurationSettings` values from the project: