Add note about dotnet restore in README

core/console-apps/HelloMsBuild/README.md

@@ -1,20 +1,19 @@
-Hello Sample
-================
+# Hello Sample
 
 This sample is part of the [step-by-step tutorial](https://docs.microsoft.com/dotnet/core/tutorials/using-with-xplat-cli)
 for creating .NET Core Console Applications. Please see that topic for detailed steps on the code
 for this sample.
 
-Key Features
-------------
+## Key Features
 
 This is the basic Hello World sample. It demonstrates the basics of the environment.
 
-Build and Run
--------------
+## Build and Run
 
 To build and run the sample, type the following command:
 
 `dotnet run`
 
 `dotnet run` builds the sample and runs the output assembly. It implicitly calls `dotnet restore` on .NET Core 2.0 and later versions. If you're using a .NET Core 1.x SDK, you first have to call `dotnet restore` yourself.
+
+**Note:** Starting with .NET Core 2.0 SDK, you don't have to run [`dotnet restore`](https://docs.microsoft.com/dotnet/core/tools/dotnet-restore) because it's run implicitly by all commands that require a restore to occur, such as `dotnet new`, `dotnet build` and `dotnet run`. It's still a valid command in certain scenarios where doing an explicit restore makes sense, such as [continuous integration builds in Azure DevOps Services](https://docs.microsoft.com/azure/devops/build-release/apps/aspnet/build-aspnet-core) or in build systems that need to explicitly control the time at which the restore occurs.

core/console-apps/NewTypesMsBuild/README.md

@@ -27,3 +27,5 @@ dotnet test
 
 `dotnet build` will follow the dependency on the `NewTypesMsBuild` project and build both the app and unit tests projects. It implicitly runs `dotnet restore` on .NET Core 2.0 and later versions. If you're using .NET Core 1.0 or .NET Core 1.1, you first have to run `dotnet restore` yourself. 
 
+<a name="dotnet-restore-note"></a>
+**Note:** Starting with .NET Core 2.0 SDK, you don't have to run [`dotnet restore`](https://docs.microsoft.com/dotnet/core/tools/dotnet-restore) because it's run implicitly by all commands that require a restore to occur, such as `dotnet new`, `dotnet build` and `dotnet run`. It's still a valid command in certain scenarios where doing an explicit restore makes sense, such as [continuous integration builds in Azure DevOps Services](https://docs.microsoft.com/azure/devops/build-release/apps/aspnet/build-aspnet-core) or in build systems that need to explicitly control the time at which the restore occurs.

core/getting-started/golden/README.md

@@ -1,24 +1,23 @@
-Getting Started using Visual Studio Code Sample
-================
+# Getting Started using Visual Studio Code Sample
 
-This sample is part of the [Getting started with .NET Core on macOS, using Visual Studio Code](../../../../docs/core/tutorials/using-on-macos.md)
+This sample is part of the [Tutorial: Create a .NET Core solution in macOS using Visual Studio Code](https://docs.microsoft.com/dotnet/core/tutorials/using-on-macos)
 walkthrough. Please see that topic for detailed steps on the code
 for this sample.
 
-Key Features
-------------
+## Key Features
 
 This sample builds a program and an associated unit test assembly. You'll learn how to structure
 projects as part of a larger solution, and incorporate unit tests into your projects.
 
-Build and Run
--------------
+## Build and Run
 
 To build and run the sample, change to the `src/library` directory and
 type the following two commands:
 
-`dotnet restore`
-`dotnet build`
+```
+dotnet restore
+dotnet build
+```
 
 `dotnet restore` ([see note](#dotnet-restore-note)) installs all the dependencies for this sample into the current directory.
 `dotnet build` creates the output assembly (or assemblies).
@@ -36,11 +35,13 @@ After that, type this command:
 To run the tests, change to the `test-library` directory and
 type the following three commands:
 
-`dotnet restore`
-`dotnet build`
-`dotnet test`
+```
+dotnet restore
+dotnet build
+dotnet test
+```
 
-`dotnet test` runs all the configure tests 
+`dotnet test` runs all the configure tests.
 
 Note that you must run `dotnet restore` ([see note](#dotnet-restore-note)) in the `src/library` directory before you can run
 the tests. `dotnet build` will follow the dependency and build both the library and unit
@@ -51,4 +52,4 @@ as your development editor. The topic walks through all the setup and configurat
 that environment.
 
 <a name="dotnet-restore-note"></a>
-[!INCLUDE[DotNet Restore Note](~/includes/dotnet-restore-note.md)]
+**Note:** Starting with .NET Core 2.0 SDK, you don't have to run [`dotnet restore`](https://docs.microsoft.com/dotnet/core/tools/dotnet-restore) because it's run implicitly by all commands that require a restore to occur, such as `dotnet new`, `dotnet build` and `dotnet run`. It's still a valid command in certain scenarios where doing an explicit restore makes sense, such as [continuous integration builds in Azure DevOps Services](https://docs.microsoft.com/azure/devops/build-release/apps/aspnet/build-aspnet-core) or in build systems that need to explicitly control the time at which the restore occurs.

core/getting-started/unit-testing-using-nunit/README.md

@@ -18,5 +18,5 @@ dotnet test
 `dotnet restore` restores the packages of both projects.
 `dotnet test` builds both projects and runs all of the configured tests.
 
-[!INCLUDE[DotNet Restore Note](~/includes/dotnet-restore-note.md)]
-
+<a name="dotnet-restore-note"></a>
+**Note:** Starting with .NET Core 2.0 SDK, you don't have to run [`dotnet restore`](https://docs.microsoft.com/dotnet/core/tools/dotnet-restore) because it's run implicitly by all commands that require a restore to occur, such as `dotnet new`, `dotnet build` and `dotnet run`. It's still a valid command in certain scenarios where doing an explicit restore makes sense, such as [continuous integration builds in Azure DevOps Services](https://docs.microsoft.com/azure/devops/build-release/apps/aspnet/build-aspnet-core) or in build systems that need to explicitly control the time at which the restore occurs.

core/linq/csharp/README.md

@@ -1,103 +1,87 @@
-101 C# LINQ Samples
-================
+# 101 C# LINQ Samples
 
 Learn how to use LINQ in your applications with these code samples, covering the entire range of LINQ functionality and demonstrating LINQ
 to objects, and LINQ to XML.
 
-aggregate
----------
+## aggregate
 
 Learn how to generate a single value from a sequence
 
-concatenation
----------
+## concatenation
 
 Combine multiple sequences into a single source sequence.
 
-conversion
----------
+## conversion
 
 Convert sequences of one type into another.
 
-customsequence
----------
+## customsequence
 
 Learn how to build seqeunces from multiple inputs.
 
-element
----------
+## element
 
 Use the index of items in a sequence during a query.
 
-equality
----------
+## equality
 
 Compare sequences for equality.
 
-generation
----------
+## generation
 
 Generate sequences by running a query.
 
-grouping
----------
+## grouping
 
 Group items into sub-sequences.
 
-join
----------
+## join
 
 Combine multiple sequences into a single sequence
 by matching values on properties.
 
 
-ordering
----------
+## ordering
 
 Sort sequences.
 
-partitioning
----------
+## partitioning
 
 Dividing an input sequence into two parts without rearranging
 them and then returning one of the parts.
 
-projection
----------
+## projection
 
 Transform sequences into new types.
 
-quantifer
----------
+## quantifier
 
 Test for all or any elements matching a condition.
 
-queryexecution
----------
+## queryexecution
 
 Learn about deferred and immediate query execution.
 
-restriction
----------
+## restriction
 
 Filter sequences using `Where`.
 
-setoperators
----------
+## setoperators
 
 Learn about set operations such as `Distinct`, `Except`, `Intersect`,
 and `Union`. 
 
-Build and Run
-=============
+# Build and Run
 
 To build and run the sample, type the following two commands in any of the subdirectories:
 
-`dotnet restore`
-`dotnet run`
+```
+dotnet restore
+dotnet run
+```
 
 `dotnet restore` restores the dependencies for this sample.
-`dotnet run` builds the sample and runs the output assembly.
 
-[!INCLUDE[DotNet Restore Note](~/includes/dotnet-restore-note.md)]
+`dotnet run` builds the sample and runs the output assembly.
 
+**Note:** Starting with .NET Core 2.0 SDK, you don't have to run [`dotnet restore`](https://docs.microsoft.com/dotnet/core/tools/dotnet-restore) because it's run implicitly by all commands that require a restore to occur, such as `dotnet new`, `dotnet build` and `dotnet run`. It's still a valid command in certain scenarios where doing an explicit restore makes sense, such as [continuous integration builds in Azure DevOps Services](https://docs.microsoft.com/azure/devops/build-release/apps/aspnet/build-aspnet-core) or in build systems that need to explicitly control the time at which the restore occurs.

csharp/branches-quickstart/README.md

@@ -1,22 +1,24 @@
-C# Branches and Loops Sample
-================
+# C# Branches and Loops Sample
 
 This sample is part of the [Branches and Loops tutorial](https://docs.microsoft.com/dotnet/csharp/tutorials/intro-to-csharp/branches-and-loops-local)
 for learning C# features. Please see that topic for detailed steps on the code
 for this sample.
 
-Key Features
-------------
+## Key Features
 
 This sample demonstrates usage of if-else branches to make decisions in the execution path, loops (while, do-while and for) to perform repeatable operations.
 
-Build and Run
--------------
+## Build and Run
 
 To build and run the sample, type the following two commands:
 
-`dotnet restore`
-`dotnet run`
+```
+dotnet restore
+dotnet run
+````
 
 `dotnet restore` restores the dependencies for this sample.
+
 `dotnet run` builds the sample and runs the output assembly.
+
+**Note:** Starting with .NET Core 2.0 SDK, you don't have to run [`dotnet restore`](https://docs.microsoft.com/dotnet/core/tools/dotnet-restore) because it's run implicitly by all commands that require a restore to occur, such as `dotnet new`, `dotnet build` and `dotnet run`. It's still a valid command in certain scenarios where doing an explicit restore makes sense, such as [continuous integration builds in Azure DevOps Services](https://docs.microsoft.com/azure/devops/build-release/apps/aspnet/build-aspnet-core) or in build systems that need to explicitly control the time at which the restore occurs.

csharp/classes-quickstart/README.md

@@ -1,22 +1,24 @@
-C# Classes and Objects Sample
-================
+# C# Classes and Objects Sample
 
 This sample is part of the [Classes and Objects tutorial](https://docs.microsoft.com/dotnet/csharp/tutorials/intro-to-csharp/introduction-to-classes)
 for learning C# features. Please see that topic for detailed steps on the code
 for this sample.
 
-Key Features
-------------
+## Key Features
 
 This sample demonstrates introduction of object oriented programming with classes and objects in C#, which explains about creation and usage of classes, objects, constructors, properties and methods.
 
-Build and Run
--------------
+## Build and Run
 
 To build and run the sample, type the following two commands:
 
-`dotnet restore`
-`dotnet run`
+```
+dotnet restore
+dotnet run
+```
 
 `dotnet restore` restores the dependencies for this sample.
+
 `dotnet run` builds the sample and runs the output assembly.
+
+**Note:** Starting with .NET Core 2.0 SDK, you don't have to run [`dotnet restore`](https://docs.microsoft.com/dotnet/core/tools/dotnet-restore) because it's run implicitly by all commands that require a restore to occur, such as `dotnet new`, `dotnet build` and `dotnet run`. It's still a valid command in certain scenarios where doing an explicit restore makes sense, such as [continuous integration builds in Azure DevOps Services](https://docs.microsoft.com/azure/devops/build-release/apps/aspnet/build-aspnet-core) or in build systems that need to explicitly control the time at which the restore occurs.

csharp/list-quickstart/README.md

@@ -1,22 +1,24 @@
-C# List Collections Sample
-================
+# C# List Collections Sample
 
 This sample is part of the [List Collections tutorial](https://docs.microsoft.com/dotnet/csharp/tutorials/intro-to-csharp/arrays-and-collections)
 for learning C# features. Please see that topic for detailed steps on the code
 for this sample.
 
-Key Features
-------------
+## Key Features
 
 This sample demonstrates management of data collections using generic list type which explains about creation of generic [List<T>](https://docs.microsoft.com/dotnet/api/system.collections.generic.list-1) type. It also explains about modification, searching and sorting of list items.
 
-Build and Run
--------------
+## Build and Run
 
 To build and run the sample, type the following two commands:
 
-`dotnet restore`
-`dotnet run`
+```
+dotnet restore
+dotnet run
+```
 
 `dotnet restore` restores the dependencies for this sample.
+
 `dotnet run` builds the sample and runs the output assembly.
+
+**Note:** Starting with .NET Core 2.0 SDK, you don't have to run [`dotnet restore`](https://docs.microsoft.com/dotnet/core/tools/dotnet-restore) because it's run implicitly by all commands that require a restore to occur, such as `dotnet new`, `dotnet build` and `dotnet run`. It's still a valid command in certain scenarios where doing an explicit restore makes sense, such as [continuous integration builds in Azure DevOps Services](https://docs.microsoft.com/azure/devops/build-release/apps/aspnet/build-aspnet-core) or in build systems that need to explicitly control the time at which the restore occurs.

csharp/numbers-quickstart/README.md

@@ -1,22 +1,24 @@
-C# Numbers Sample
-================
+# C# Numbers Sample
 
 This sample is created during the [Numbers in C# tutorial](https://docs.microsoft.com/dotnet/csharp/tutorials/intro-to-csharp/numbers-in-csharp-local)
 for learning C# features. Please see that topic for detailed steps on the code
 for this sample.
 
-Key Features
-------------
+## Key Features
 
 This sample demonstrates about numbers and math operations on integer, floating point numbers in C# and also explains about precedence of the different mathematical operations.
 
-Build and Run
--------------
+## Build and Run
 
 To build and run the sample, type the following two commands:
 
-`dotnet restore`
-`dotnet run`
+```
+dotnet restore
+dotnet run
+```
 
 `dotnet restore` restores the dependencies for this sample.
+
 `dotnet run` builds the sample and runs the output assembly.
+
+**Note:** Starting with .NET Core 2.0 SDK, you don't have to run [`dotnet restore`](https://docs.microsoft.com/dotnet/core/tools/dotnet-restore) because it's run implicitly by all commands that require a restore to occur, such as `dotnet new`, `dotnet build` and `dotnet run`. It's still a valid command in certain scenarios where doing an explicit restore makes sense, such as [continuous integration builds in Azure DevOps Services](https://docs.microsoft.com/azure/devops/build-release/apps/aspnet/build-aspnet-core) or in build systems that need to explicitly control the time at which the restore occurs.