rebase prtest (#56)

* Fixes and improvements to Semantic analysis Get started (dotnet#4575) * Order the definitions to match the order of terms (dotnet#4576) The introductory sentence could be read as implying definitions that contradict the body of the article. * Fix invalid Windows file system paths (dotnet#4559) * Fix invalid Windows file system paths * Add escape characters * Fixing capitalization of Visual Basic (dotnet#4578) Changed "Visual basic" to "Visual Basic" for the description of the Get Visual Basic link. * Fixed broken links in interop docs (dotnet#4573) * Fixed broken links in interop docs * Updated additional links * Removed 'en-us' from URLs * Fixing broken link to MVA course (dotnet#4580) Visual Basic Fundamentals for Absolute Beginners link was directing to a list of courses, not really related to VB. I've updated the link directly to the course. I did check to see if the course was in other languages before putting in the en-US link - looks like it's available only in English. * Minor refactoring (dotnet#4582) Change "new ValidationResult(true, null)" to "ValidationResult.ValidResult", since it looks a little cleaner and the property was explicitly designed for that use. * Fixed link (dotnet#4583) * Update "How to: Modify string" (dotnet#4519) * article and code moved * interim checkin Switching tasks. * checkin to run test build I want to see if I can use local functions in C# interactive. * finish samples and new draft Ready for my first review. * fix build errors * proofread * update per feedback. * respond to feedback. * additional feedback. * respond to feedback. * Fix escape characters in HttpListener Remarks section (dotnet#4495) * Minor refactoring (dotnet#4584) Change "New ValidationResult(True, Nothing)" to "ValidationResult.ValidResult", since it looks a little cleaner and the property was explicitly designed for that use. * fix title (dotnet#4590) * fix broken links (dotnet#4588) * Add the closing token for an XML include (dotnet#4593) Without this, the rest of the file renders incorrectly. * Correct description of ROOT parameter (dotnet#4595) * Update tuples.md "Interoperation with C# Tuples" content (dotnet#4581) * Removed an excessive "and" * Removed some text that didn't seem overly clear. * Replaced link to UserVoice (dotnet#4594) * Removed link to UserVoice * Changed URL target * Fix typo (dotnet#4599) * Experiment: CodeOwners (dotnet#4597) * Experiment: CodeOwners Trying an experiment to see how we might use use the CODEOWNERS file to get reviews routed to the right person. * Added several sections * Update CODEOWNERS * Fixing anchor link to the "private protected access modifier" section (dotnet#4601) * fixes to the CODEOWNERS (dotnet#4602) * fixes to the CODEOWNERS The changes here: 1. The '@' is needed on each user name. 1. The C# Snippets was missing the 'csharp' directory component. 1. Order is important. * Add F# guide. * modify-string-contents.md: added interactive note (dotnet#4607) * Fix markdown table (dotnet#4603) Fix usage of `|` in markdown (use `|` instead) * Update infrastructure-persistence-layer-implemenation-entity-framework-core.md (dotnet#4610) Update link to the new address to avoid an extra 301 redirect. * csharp-interactive-note.md: style update (dotnet#4606) * parallel-diagnostic-tools.md: removed Visual Studio version (dotnet#4608) * adding missing language identifiers (dotnet#4611) * adding missing language identifiers (dotnet#4612) * adding missing language identifiers (dotnet#4613) * adding missing language identifiers (dotnet#4614) * adding missing language identifiers (dotnet#4615) * adding missing language identifiers (dotnet#4616) * adding missing language identifiers (dotnet#4617) * adding missing language identifiers (dotnet#4618) * adding missing language identifiers (dotnet#4619) * adding missing language identifiers (dotnet#4620) * adding missing language identifiers (dotnet#4621) * adding missing language identifiers (dotnet#4622) * adding missing language identifiers (dotnet#4623) * Fixed some attribute names (dotnet#4629) .NET puts the "Attribute" suffix in all its attribute *classes*, but not in the actual attribute. * Fix "whitespace" words - docs/standard (dotnet#4605) * base-types * fixes by pr rpetrusha * System.Reflection docs for ProcessorArchitecture is misleading (dotnet#4539) * clarify the difference betwen IA64 and AMD64 * Update ProcessorArchitecture.xml * Changed 'integer' to 'integral value' for consistency (dotnet#4586) * 👓 sweep docset for areas where `in` wasn't mentioned but should be (dotnet#4534) * sweep docset for areas where `in` wasn't mentioned but should be * respond to first round of feedback * create in-modifer article Also, update samples and snippets and make corresponding changs to 'ref' and 'out' article. * fix build errors * fix one more build error * wording change based on feedback. * respond to edits * commit changes from that unsaved window Yeah, I did that. Didn't save before committing. * added missing options (dotnet#3390) * Add warning regarding server host configuration (dotnet#4634) * Fix some xrefs (dotnet#4624) * Fix some xrefs * Fixed typo * Change hybrid xref links to normal xrefs * Remove redundant text with bad link * Update compiler-api-model.md (dotnet#4636) fix small typos * Corrected description of verbatim attribute usage (dotnet#4635) * removed sentence about migrating content (dotnet#4532) * removed sentence about migrating content * removed preview * Update the F# Guide page and some ms.date links (dotnet#4521) * Update to F# docs round 1 * yup * fix * feedback * Fix link * feedback * Updates * Updates * Updates * Make comments betteR * Feedback * Feedback * fixes * Improvements to Creating a Type Provider (dotnet#4592) * Improvements to Creating a Type Provider * Fixed assembly attribute * Revision of DateTime.Parse overloads (dotnet#4455) * Revision of DateTime.Parse * Additional modifications * Some further revisions * Additional revisions * Corrected bad XML tags * Moved examples * Additional revisions and .zip files * Added accidentally deleted file * Addressed review comments * keywords/string.md: link verbatim identifier page (dotnet#4639) * C13890: Show code for link in target versions (dotnet#4641) Hello, @BillWagner, Localization team has reported source content issue that causes localized version to have broken format compared to en-us version. Please, help to check my proposed file change into the article and help to merge if you agree with fix. If not, please, let me know either if you would like me to fix it in another way within this PR, if you prefer to fix it in another PR or if I should close this PR as by-design. In case of using another PR, please, let me know of your PR number, so we can confirm and close this PR. Many thanks in advance. * C13891: Show code for link in target versions (dotnet#4642) * Fix incorrect en dashes (dotnet#4644) * replace BNF grammar with ANTL grammar (dotnet#4643) * replace BNF grammar with ANTL grammar The BNF grammar rendering was quite messy. Antlr provides a much more clear rendering on the current engine. * fix typo and update metadata * Added output comment to verbatim string code snippet (dotnet#4646) * added missing entry (dotnet#4648) * simplify template (dotnet#4645) * simplify template * feedback * Fixed broken links to archived interop topics (dotnet#4647) * Changed HSB to HSL color model (dotnet#4652) * Changed HSB to HSL color model * Addressed review comments * Fix connect bug DevDiv # 93543 (dotnet#4653) * fix broken link (dotnet#4655) * Add displayProperty attribute to address customer complaint in SqlParameter.Value docs (dotnet#4660) * Fix connect bug DevDiv # 93543 * Add clarifications to links to address DevDiv Connect Bug # 104024 * add one more displayproperty * including the template in the treeview (dotnet#4662) Adding reference the hierarchical template in the treeview * Replace IIF with IF (dotnet#4665) * Added GetHashCode() implementation to ValueObject (dotnet#4185) This will be very helpful to readers. Picked it up from eShopOnContainers repo. * Provided correct enum members, method overloads (dotnet#4484) * Provided correct enum members, method overloads * Incorporated review comments, corrected other errors * Fixed 2 broken links * Fixed two additional links * Added exception information to SingleOrDefault (dotnet#4650) * Added information on string length >= desired string length (dotnet#4651) * Added information on string length >= desire string length * fixed broken link * Incorporated comments from @svick * TLS best practices (dotnet#4658) * IIF to IF on Tuples page (dotnet#4669) * fix: derrived --> derived typo (dotnet#4673) * Modified contributors guide to reflect contributors' project (dotnet#4666) * Add link to github issue to TLS doc (dotnet#4676) * fix link (dotnet#4672) * fix typo (dotnet#4678) * Remove extra backslash (dotnet#4680) * Fix markdown link (dotnet#4679) * Fix markdown link * feedback * update signalr info for 2.1 preview (dotnet#4681) * Fix typo (dotnet#4683) * fixed typo * fix typo * add PDF to preview serverless e-book (dotnet#4685) * Removed spaces in code (dotnet#4671) * Fixed typo in --x operator description (dotnet#4691) * Add syntax highlighting to inline code in stackalloc (dotnet#4690) Just noticed on docs.microsoft.com that these code blocks don't have syntax highlighting, which does not adhere to the style guide * Add UWP as platform that supports .NET Standard (dotnet#3813) * Add UWP as platform that supports .NET Standard https://blogs.msdn.microsoft.com/dotnet/2017/10/10/announcing-uwp-support-for-net-standard-2-0/ * Add platforms; remove versions; add link Instead of listing the same platforms that are listed on https://docs.microsoft.com/en-us/dotnet/standard/net-standard#net-implementation-support and having to maintain both lists as new versions are released, just mention the platforms here and link to the existing table with versions. Closes dotnet#3814 * feedback * < and > wrong (dotnet#4664) * < and > wrong < and > were not in code * Updated xref Updated xref to correct signature * removing tickmarks and overloads * some other minor fixes * Update net-standard.md (dotnet#4694) * Correct time complexity of List<T>.InsertRange (dotnet#4693) * Operator new doesn't create structs on the stack (dotnet#4667) * Operator new doesn't create structs on the stack * Small improvements to operator new * Structs can contain resources too * Mention garbage collector * Clarified when value types are destroyed
OPS-E2E-Prod · Mar 19, 2018 · 60b2012 · 60b2012
1 parent 130fa91
commit 60b2012
Show file tree

Hide file tree

Showing 838 changed files with 2,724 additions and 1,975 deletions.
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
@@ -0,0 +1,72 @@
+# Lines starting with '#' are comments.
+# Each line is a file pattern followed by one or more owners.
+
+# More details are here: https://help.github.com/articles/about-codeowners/
+
+# The '*' pattern is global owners.
+# Not adding in this PR, but I'd like to try adding a global owner set with the entire team.
+# One interpretation of their docs is that global owners are added only if not removed
+# by a more local rule.
+
+# Order is important. The last matching pattern has the most precedence.
+# The folders are ordered as follows:
+# . Guides are first.
+# . .NET Core sections are next
+# . .NET Framework sections
+# . .NET Standard 
+# . samples
+
+# In each subsection folders are order first by depth, then alphabetically.
+# This should make it easy to add new rules without breaking existing ones.
+
+
+############  GUIDES  ################
+# .NET Core
+/docs/core/** @mairaw
+
+# The C# Guide:
+/docs/csharp/** @BillWagner
+
+# The F# Guide:
+/docs/fsharp/** @cartermp
+
+# The Visual Basic Guide:
+/docs/visual-basic/** @rpetrusha
+
+############### .NET Core ########################
+# Docker
+/docs/core/docker/** @JRAlexander
+# What's New
+/docs/core/whats-new/** @rpetrusha
+
+################### .NET FRAMEWORK ##################
+# .NET Framework migration guide
+/docs/framework/migration-guide/** @rpetrusha
+# .NET Framework Security
+/docs/framework/security/** @mairaw
+# .NET Framework unmanaged API
+/docs/framework/unmanaged-api/** @rpetrusha
+# What's New
+/docs/framework/whats-new/** @rpetrusha
+
+################## .NET STANDARD ##################
+# Analyzers:
+/docs/standard/analyzers/** @BillWagner
+# What's New
+/docs/standard/whats-new/** @rpetrusha
+# .NET I/O
+/docs/standard/io/** @mairaw
+# .NET base types - Formatting
+/docs/standard/base-types/formatting-types/** @rpetrusha
+
+###########  SAMPLES ################
+# C# samples:
+/samples/csharp/**  @BillWagner
+
+#### Snippets (under samples)
+# C++ snippets
+/samples/snippets/cpp/** @rpetrusha
+# C# Snippets:
+/samples/snippets/csharp/** @BillWagner
+# Visual Basic snippets:
+/samples/snippets/visualbasic/** @rpetrusha
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,30 +1,5 @@
-# Title
-
-On the title describe
-what you've fixed (or created) with this Pull Request (PR).
-
 ## Summary
 
-Insert a short (one or two sentence) summary here.
-
-Fixes #Issue_Number
-
->Note: The "Fixes #nnn" syntax in the PR description causes
->GitHub to automatically close the issue when this PR is merged.
-> Remove that line if you don't have issues associated with this
-> PR. Click on the Guidelines for Contributing link above for details.
-
-## Details
-
-Explain your changes, and why you made them. If that
-information is already available in the issue referenced
-above, just referencing the issue is preferred to copying
-the text.
-
-This may not be necessary depending on the scope of the PR 
-changes. For example, "fix typo in introduction.md" is
-sufficient to describe that PR.
-
-## Suggested Reviewers
+Describe your changes here.
 
-If you know who should review this, use '@' to request a review.
+Fixes #Issue_Number (if available)
diff --git a/.openpublishing.publish.config.json b/.openpublishing.publish.config.json
@@ -10,6 +10,10 @@
       "Publish",
       "Intellisense"
     ],
+    "serverless-ebook": [
+      "Publish",
+      "Pdf"
+    ],    
     "ai-ebook": [
       "Publish",
       "Pdf"

diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -1105,6 +1105,10 @@
         {
             "source_path": "docs/csharp/programming-guide/strings/how-to-search-strings-using-regular-expressions.md",
             "redirect_url": "/dotnet/csharp/how-to/search-strings"
-        }    
+        },
+        {    
+            "source_path": "docs/csharp/programming-guide/strings/how-to-modify-string-contents.md",
+            "redirect_url": "/dotnet/csharp/how-to/modify-string-contents"
+        }
     ]
 }
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -13,10 +13,20 @@ The document covers the process for contributing to the articles and code sample
 
 You need a basic understanding of [Git and GitHub.com](https://guides.github.com/activities/hello-world/).
 
-**Step 1:** Skip this step for small changes. Open an [issue](https://github.com/dotnet/docs/issues) describing what you want to do, such as change an existing article or create a new one.
+**Step 1:** Skip this step for small changes. If you're interested in writing new content or in thoroughly revising existing content, open an [issue](https://github.com/dotnet/docs/issues) describing what you want to do.
 The content inside the **docs** folder is organized into sections that are reflected in the Table of Contents (TOC). Define where the topic will be located in the TOC. Get feedback on your proposal.
 
-You can also look at our [open issues](https://github.com/dotnet/docs/issues) list and volunteer to work on the ones you're interested in. We use the [up-for-grabs](https://github.com/dotnet/docs/labels/up-for-grabs) label to tag issues open for contribution.
+-or-
+
+You can also choose from existing issues for which community contributions are welcome. [Projects for .NET Community contributors](https://github.com/dotnet/docs/projects/35) lists many of the work items that are available for commmunity contributors. Depending on your interests and level of commitment, you can choose from issues in the following categories:
+
+- **Maintenance**. This category includes fairly simple contributions, such as fixing broken or incorrect links, adding missing code examples, or addressing limited content issues. In some cases, these issues may concern large numbers of files. In that case, you should let us know what you'd like to work on before you begin.
+
+- **Content updates**. Given the enormity of the doc set, content easily becomes outdated and requires revision. In addition, for a variety of reason, some content has been duplicated or even triplicated. Updating content involves making sure that individual topics are current or revising content in a feature area to eliminate duplication and ensure that all unique content is preserved in the smaller documentation set.
+
+- **New content authoring**. If you're interested in authoring your own topic, these issues list topics that we know we'd like to add to our doc set. Let us know before you begin working on a topic, though. If you're interested in writing a topic that isn't listed here, open an issue. 
+
+You can also look at our [open issues](https://github.com/dotnet/docs/issues) list and volunteer to work on the ones you're interested in. We use the [up-for-grabs](https://github.com/dotnet/docs/labels/up-for-grabs) label to tag issues open for contribution. 
 
 **Step 2:** Fork the `/dotnet/docs` repo and create a branch for your changes.
 

diff --git a/README.md b/README.md
@@ -2,7 +2,7 @@
 
 This repo contains work-in-progress documentation for .NET. To contribute, see the [Contributing Guide](https://github.com/dotnet/docs/blob/master/CONTRIBUTING.md) and the [issues list](https://github.com/dotnet/docs/issues). 
 
-We welcome contributions to help us improve and complete the .NET docs. Feel free to copy/paste documentation from [.NET Framework docs](https://msdn.microsoft.com/library/w0x726c2.aspx) as a starting point for .NET docs. We anticipate that [Xamarin](http://developer.xamarin.com/api/root/classlib/), [Mono](http://docs.go-mono.com/?link=root%3a%2fclasslib) and [Unity](http://docs.unity3d.com/Manual/index.html) will also use this documentation.
+We welcome contributions to help us improve and complete the .NET docs. We anticipate that [Xamarin](http://developer.xamarin.com/api/root/classlib/), [Mono](http://docs.go-mono.com/?link=root%3a%2fclasslib) and [Unity](http://docs.unity3d.com/Manual/index.html) will also use this documentation.
 
 This project has adopted the code of conduct defined by the Contributor Covenant
 to clarify expected behavior in our community.
@@ -11,7 +11,7 @@ For more information, see the [.NET Foundation Code of Conduct](https://dotnetfo
 Samples Build Status
 ===
 
-| Samples | Ubuntu 16.04<br/>_.NET Core 1.1.0_ | Ubuntu 16.04<br/>_.NET Core 2.0.0-preview_  |
+| Samples | Ubuntu 16.04<br/>_.NET Core 1.1.0_ | Ubuntu 16.04<br/>_.NET Core 2.0.0_  |
 | ------------- |------------| -----|
 | `/samples/core` | ![](https://constructors.visualstudio.com/_apis/public/build/definitions/3186585f-1677-4c9e-a8b2-baac48a4032a/56/badge)| ![](https://constructors.visualstudio.com/_apis/public/build/definitions/3186585f-1677-4c9e-a8b2-baac48a4032a/57/badge) |
 |`/samples/csharp`| ![](https://constructors.visualstudio.com/_apis/public/build/definitions/3186585f-1677-4c9e-a8b2-baac48a4032a/54/badge)| ![](https://constructors.visualstudio.com/_apis/public/build/definitions/3186585f-1677-4c9e-a8b2-baac48a4032a/55/badge) |
diff --git a/api/index.md b/api/index.md
@@ -10,4 +10,4 @@ ms.topic: landing-page
 
 # .NET API Browser
 
-Welcome to the .NET API Browser – your one-stop shop for all .NET-based APIs from Microsoft. Start searching for any managed APIs by typing in the box below. You can learn more about the API Browser [in our blog post](https://aka.ms/apibrowser). If you have any feedback,  use [our UserVoice site](https://aka.ms/apibrowserfeedback).
+Welcome to the .NET API Browser – your one-stop shop for all .NET-based APIs from Microsoft. Start searching for any managed APIs by typing in the box below. You can learn more about the API Browser [in our blog post](https://aka.ms/apibrowser). If you have any feedback, create a new issue in the [MicrosoftDocs/feedback repo on GitHub](https://github.com/MicrosoftDocs/feedback/issues). 
diff --git a/docs/core/packages.md b/docs/core/packages.md
@@ -1,5 +1,5 @@
 ---
-title: Packages, Metapackages and Frameworks
+title: Packages, metapackages and frameworks
 description: Learn terminology for packages, metapackages, and frameworks.
 keywords: .NET, .NET Core
 author: richlander
@@ -12,8 +12,7 @@ ms.assetid: 609b0845-49e7-4864-957b-21ffe1b93bf2
 ms.workload: 
   - dotnetcore
 ---
-
-# Packages, Metapackages and Frameworks
+# Packages, metapackages and frameworks
 
 .NET Core is a platform made of NuGet packages. Some product experiences benefit from fine-grained definition of packages while others from coarse-grained. To accommodate this duality, the product is distributed as a fine-grained set of packages and then described in coarser chunks with a package type informally called a "metapackage".
 
@@ -74,7 +73,7 @@ The .NET Standard metapackage is:
 
 The key .NET Core metapackages are:
 
-- [Microsoft.NETCore.App](https://www.nuget.org/packages/Microsoft.NETCore.App) - Describes the libraries that are part of the .NET Core distribution. Establishes the [`.NETCoreApp` framework](https://github.com/dotnet/core-setup/blob/master/pkg/projects/Microsoft.NETCore.App/Microsoft.NETCore.App.pkgproj). Depends on the smaller `NETStandard.Library`.
+- [Microsoft.NETCore.App](https://www.nuget.org/packages/Microsoft.NETCore.App) - Describes the libraries that are part of the .NET Core distribution. Establishes the [`.NETCoreApp` framework](https://github.com/dotnet/core-setup/blob/release/1.1.0/pkg/projects/Microsoft.NETCore.App/Microsoft.NETCore.App.pkgproj). Depends on the smaller `NETStandard.Library`.
 - [Microsoft.NETCore.Portable.Compatibility](https://www.nuget.org/packages/Microsoft.NETCore.Portable.Compatibility) - A set of compatibility facades that enable mscorlib-based Portable Class Libraries (PCLs) to run on .NET Core.
 
 ## Frameworks
@@ -93,7 +92,7 @@ The `.NETFramework,Version=4.6` framework represents the available APIs in the .
 
 The `.NETStandard,Version=1.3` framework is a package-based framework. It relies on packages that target the framework to define and expose APIs in terms of the framework.
 
-## Package-based Frameworks
+## Package-based frameworks
 
 There is a two-way relationship between frameworks and packages. The first part is defining the APIs available for a given framework, for example `netstandard1.3`. Packages that target `netstandard1.3` (or compatible frameworks, like `netstandard1.0`) define the APIs available for `netstandard1.3`. That may sound like a circular definition, but it isn't. By virtue of being "package-based", the API definition for the framework comes from packages. The framework itself doesn't define any APIs.
 
@@ -137,7 +136,7 @@ It may seem strange to target `netstandard1.3` but use the 1.6.0 version of `NET
 
 The reverse would not be valid: targeting `netstandard1.6` with the 1.3.0 version of `NETStandard.Library`. You cannot target a higher framework with a lower metapackage, since the lower version metapackage will not expose any assets for that higher framework. The versioning scheme for metapackages asserts that metapackages match the highest version of the framework they describe. By virtue of the versioning scheme, the first version of `NETStandard.Library` is v1.6.0 given that it contains `netstandard1.6` assets. v1.3.0 is used in the example above, for symmetry with the example above, but does not actually exist.
 
-### .NET Core Application
+### .NET Core application
 
 The .NET Core Application (TFM: `netcoreapp`) framework represents the packages and associated APIs that come with the .NET Core distribution and the console application model that it provides. .NET Core apps must use this framework, due to targeting the console application model, as should libraries that intended to run only on .NET Core. Using this framework restricts apps and libraries to running only on .NET Core. 
 

diff --git a/docs/core/tools/dotnet-build.md b/docs/core/tools/dotnet-build.md
@@ -3,7 +3,7 @@ title: dotnet build command - .NET Core CLI
 description: The dotnet build command builds a project and all of its dependencies.
 author: mairaw
 ms.author: mairaw
-ms.date: 08/13/2017
+ms.date: 03/10/2018
 ms.topic: article
 ms.prod: .net-core
 ms.technology: dotnet-cli
@@ -22,12 +22,14 @@ ms.workload:
 
 # [.NET Core 2.x](#tab/netcore2x)
 ```
-dotnet build [<PROJECT>] [-c|--configuration] [-f|--framework] [--force] [--no-dependencies] [--no-incremental] [--no-restore] [-o|--output] [-r|--runtime] [-v|--verbosity] [--version-suffix]
+dotnet build [<PROJECT>] [-c|--configuration] [-f|--framework] [--force] [--no-dependencies] [--no-incremental]
+    [--no-restore] [-o|--output] [-r|--runtime] [-v|--verbosity] [--version-suffix]
 dotnet build [-h|--help]
 ```
 # [.NET Core 1.x](#tab/netcore1x)
 ```
-dotnet build [<PROJECT>] [-c|--configuration] [-f|--framework] [--no-dependencies] [--no-incremental] [-o|--output] [-r|--runtime] [-v|--verbosity] [--version-suffix]
+dotnet build [<PROJECT>] [-c|--configuration] [-f|--framework] [--no-dependencies] [--no-incremental] [-o|--output]
+    [-r|--runtime] [-v|--verbosity] [--version-suffix]
 dotnet build [-h|--help]
 ```
 ---
@@ -40,7 +42,7 @@ If the project has third-party dependencies, such as libraries from NuGet, they'
 
 Building requires the *project.assets.json* file, which lists the dependencies of your application. The file is created when [`dotnet restore`](dotnet-restore.md) is executed. Without the assets file in place, the tooling cannot resolve reference assemblies, which results in errors. With .NET Core 1.x SDK, you needed to explicitily run the `dotnet restore` before running `dotnet build`. Starting with .NET Core 2.0 SDK, `dotnet restore` runs implicitily when you run `dotnet build`. If you want to disable implicit restore when running the build command, you can pass the `--no-restore` option.
 
-[!INCLUDE[DotNet Restore Note](~/includes/dotnet-restore-note.md)]
+[!INCLUDE[dotnet restore note + options](~/includes/dotnet-restore-note-options.md)]
 
 `dotnet build` uses MSBuild to build the project; thus, it supports both parallel and incremental builds. Refer to [Incremental Builds](/visualstudio/msbuild/incremental-builds) for more information.
 
@@ -162,4 +164,8 @@ Build a project and its dependencies using Release configuration:
 
 Build a project and its dependencies for a specific runtime (in this example, Ubuntu 16.04):
 
-`dotnet build --runtime ubuntu.16.04-x64`
+`dotnet build --runtime ubuntu.16.04-x64`
+
+Build the project and use the specified NuGet package source during the restore operation (.NET Core SDK 2.0 and later versions):
+
+`dotnet build --source c:\packages\mypackages`
diff --git a/docs/core/tools/dotnet-nuget-push.md b/docs/core/tools/dotnet-nuget-push.md
@@ -30,7 +30,7 @@ The `dotnet nuget push` command pushes a package to the server and publishes it.
 
 `ROOT`
 
-Specify the path to the package and your API key to push the package to the server.
+Specifies the file path to the package to be pushed.
 
 ## Options
 

diff --git a/docs/core/tools/dotnet-pack.md b/docs/core/tools/dotnet-pack.md
@@ -3,7 +3,7 @@ title: dotnet pack command - .NET Core CLI
 description: The dotnet pack command creates NuGet packages for your .NET Core project.
 author: mairaw
 ms.author: mairaw
-ms.date: 12/13/2017
+ms.date: 03/10/2018
 ms.topic: article
 ms.prod: .net-core
 ms.technology: dotnet-cli
@@ -23,7 +23,8 @@ ms.workload:
 # [.NET Core 2.x](#tab/netcore2x)
 
 ```
-dotnet pack [<PROJECT>] [-c|--configuration] [--force] [--include-source] [--include-symbols] [--no-build] [--no-dependencies] [--no-restore] [-o|--output] [--runtime] [-s|--serviceable] [-v|--verbosity] [--version-suffix]
+dotnet pack [<PROJECT>] [-c|--configuration] [--force] [--include-source] [--include-symbols] [--no-build] [--no-dependencies]
+    [--no-restore] [-o|--output] [--runtime] [-s|--serviceable] [-v|--verbosity] [--version-suffix]
 dotnet pack [-h|--help]
 ```
 
@@ -44,6 +45,8 @@ By default, `dotnet pack` builds the project first. If you wish to avoid this be
 
 You can provide MSBuild properties to the `dotnet pack` command for the packing process. For more information, see [NuGet metadata properties](csproj.md#nuget-metadata-properties) and the [MSBuild Command-Line Reference](/visualstudio/msbuild/msbuild-command-line-reference). The [Examples](#examples) section shows how to use the MSBuild /p switch for a couple of different scenarios.
 
+[!INCLUDE[dotnet restore note + options](~/includes/dotnet-restore-note-options.md)]
+
 ## Arguments
 
 `PROJECT`
@@ -154,7 +157,7 @@ Pack the project in the current directory:
 Pack the `app1` project:
 
 `dotnet pack ~/projects/app1/project.csproj`
-	
+
 Pack the project in the current directory and place the resulting packages into the `nupkgs` folder:
 
 `dotnet pack --output nupkgs`
@@ -174,3 +177,7 @@ Set the package version to `2.1.0` with the `PackageVersion` MSBuild property:
 Pack the project for a specific [target framework](../../standard/frameworks.md):
 
 `dotnet pack /p:TargetFrameworks=net45`
+
+Pack the project and use a specific runtime (Windows 10) for the restore operation (.NET Core SDK 2.0 and later versions):
+
+`dotnet pack --runtime win10-x64`