Update live with current master (#5874)

* Update azure-apps-preview-notice.md (#5857)

* Link to .NET Core CLI publish command doc (#5864)

* Link to .NET Core CLI publish command doc

* Verbiage tweak

* fix typo (#5866)

* Update intro.md (#5869)

`classnameID` (where `classname` is the name of the class, such as `Student`) as the primary key. In `classnameID`, `classname` is the name of the class, such as `Student` in

* Update view-components.md (#5872)

altering range of code displayed to remove hanging closing } and closing table tag

aspnetcore/data/ef-rp/intro.md

@@ -96,7 +96,7 @@ Create a *Models* folder. In the *Models* folder, create a class file named *Stu
 
 [!code-csharp[](intro/samples/cu/Models/Student.cs?name=snippet_Intro)]
 
-The `ID` property becomes the primary key column of the database (DB) table that corresponds to this class. By default, EF Core interprets a property that's named `ID` or `classnameID` as the primary key.
+The `ID` property becomes the primary key column of the database (DB) table that corresponds to this class. By default, EF Core interprets a property that's named `ID` or `classnameID` as the primary key. In `classnameID`, `classname` is the name of the class, such as `Student` in the preceding example.
 
 The `Enrollments` property is a navigation property. Navigation properties link to other entities that are related to this entity. In this case, the `Enrollments` property of a `Student entity` holds all of the `Enrollment` entities that are related to that `Student`. For example, if a Student row in the DB has two related Enrollment rows, the `Enrollments` navigation property contains those two `Enrollment` entities. A related `Enrollment` row is a row that contains that student's primary key value in the `StudentID` column. For example, suppose the student with ID=1 has two rows in the `Enrollment` table. The `Enrollment` table has two rows with `StudentID` = 1. `StudentID` is a foreign key in the `Enrollment` table that specifies the student in the `Student` table.
 

aspnetcore/data/ef-rp/migrations.md

@@ -181,7 +181,7 @@ Use **SQL Server Object Explorer** to inspect the DB. Notice the addition of an
 
 Run the app and verify that everything works.
 
-## Appling migrations in production
+## Applying migrations in production
 
 We recommend production apps should **not** call [Database.Migrate](https://docs.microsoft.com/dotnet/api/microsoft.entityframeworkcore.relationaldatabasefacadeextensions.migrate?view=efcore-2.0#Microsoft_EntityFrameworkCore_RelationalDatabaseFacadeExtensions_Migrate_Microsoft_EntityFrameworkCore_Infrastructure_DatabaseFacade_) at application startup. `Migrate` shouldn't be called from an app in server farm. For example, if the app has been cloud deployed with scale-out (multiple instances of the app are running).
 

aspnetcore/includes/azure-apps-preview-notice.md

@@ -1,4 +1,4 @@
 > [!IMPORTANT]
 > **Notice for using ASP.NET Core 2.1 preview releases**
 >
-> Unlike previous preview releases, ASP.NET Core 2.1 preview releases won't be deployed to Azure App Service. To install an ASP.NET Core 2.1 preview release for use with Azure App Service, see [ASP.NET Core 2.1.0-preview1: Using ASP.NET Core Previews on Azure App Service](https://blogs.msdn.microsoft.com/webdev/2018/02/27/asp-net-core-2-1-0-preview1-using-asp-net-core-previews-on-azure-app-service/).
+> See [Deploy ASP.NET Core preview release to Azure App Service](xref:host-and-deploy/azure-apps/index#deploy-aspnet-core-preview-release-to-azure-app-service).

aspnetcore/mvc/views/view-compilation.md

@@ -48,7 +48,7 @@ Set `MvcRazorCompileOnPublish` to `true`, and include a package reference to `Mi
 
 ---
 
-Prepare the app for a [framework-dependent deployment](/dotnet/core/deploying/#framework-dependent-deployments-fdd) by executing a command such as the following at the project root:
+Prepare the app for a [framework-dependent deployment](/dotnet/core/deploying/#framework-dependent-deployments-fdd) with the [.NET Core CLI publish command](/dotnet/core/tools/dotnet-publish). For example, execute the following command at the project root:
 
 ```console
 dotnet publish -c Release

aspnetcore/mvc/views/view-components.md

@@ -238,7 +238,7 @@ If you want compile time safety, you can replace the hard-coded view component n
 
 Add a `using` statement to your Razor view file, and use the `nameof` operator:
 
-[!code-cshtml[](view-components/sample/ViewCompFinal/Views/Todo/IndexNameof.cshtml?range=1-6,33-)]
+[!code-cshtml[](view-components/sample/ViewCompFinal/Views/Todo/IndexNameof.cshtml?range=1-6,35-)]
 
 ## Additional resources