Fix some docs bugs

Fixes #2967, fixes #3086, fixes #3114

entity-framework/core/cli/powershell.md

@@ -65,9 +65,9 @@ Before using the tools:
 
 The commands refer to a *project* and a *startup project*.
 
-* The *project* is also known as the *target project* because it's where the commands add or remove files. By default, the **Default project** selected in **Package Manager Console** is the target project. You can specify a different project as target project by using the <nobr>`--project`</nobr> option.
+* The *project* is also known as the *target project* because it's where the commands add or remove files. By default, the **Default project** selected in **Package Manager Console** is the target project. You can specify a different project as target project by using the <nobr>`-Project`</nobr> parameter.
 
-* The *startup project* is the one that the tools build and run. The tools have to execute application code at design time to get information about the project, such as the database connection string and the configuration of the model. By default, the **Startup Project** in **Solution Explorer** is the startup project. You can specify a different project as startup project by using the <nobr>`--startup-project`</nobr> option.
+* The *startup project* is the one that the tools build and run. The tools have to execute application code at design time to get information about the project, such as the database connection string and the configuration of the model. By default, the **Startup Project** in **Solution Explorer** is the startup project. You can specify a different project as startup project by using the <nobr>`-StartupProject`</nobr> parameter.
 
 The startup project and target project are often the same project. A typical scenario where they are separate projects is when:
 

entity-framework/core/modeling/data-seeding.md

@@ -43,7 +43,7 @@ See the [full sample project](https://github.com/dotnet/EntityFramework.Docs/tre
 Once the data has been added to the model, [migrations](xref:core/managing-schemas/migrations/index) should be used to apply the changes.
 
 > [!TIP]
-> If you need to apply migrations as part of an automated deployment you can [create a SQL script](xref:core/managing-schemas/migrations/index#generate-sql-scripts) that can be previewed before execution.
+> If you need to apply migrations as part of an automated deployment you can [create a SQL script](xref:core/managing-schemas/migrations/applying#sql-scripts) that can be previewed before execution.
 
 Alternatively, you can use `context.Database.EnsureCreated()` to create a new database containing the seed data, for example for a test database or when using the in-memory provider or any non-relation database. Note that if the database already exists, `EnsureCreated()` will neither update the schema nor seed data in the database. For relational databases you shouldn't call `EnsureCreated()` if you plan to use Migrations.
 

samples/core/Schemas/Migrations/CustomOperation.cs

@@ -5,7 +5,7 @@
 using Microsoft.EntityFrameworkCore.Migrations.Operations.Builders;
 
 #region snippet_CreateUserOperation
-internal class CreateUserOperation : MigrationOperation
+public class CreateUserOperation : MigrationOperation
 {
     public string Name { get; set; }
     public string Password { get; set; }
@@ -15,7 +15,7 @@ internal class CreateUserOperation : MigrationOperation
 internal static class MigrationBuilderExtensions
 {
     #region snippet_MigrationBuilderExtension
-    private static OperationBuilder<CreateUserOperation> CreateUser(
+    public static OperationBuilder<CreateUserOperation> CreateUser(
         this MigrationBuilder migrationBuilder,
         string name,
         string password)
@@ -29,7 +29,7 @@ private static OperationBuilder<CreateUserOperation> CreateUser(
 }
 
 #region snippet_MigrationsSqlGenerator
-internal class MyMigrationsSqlGenerator : SqlServerMigrationsSqlGenerator
+public class MyMigrationsSqlGenerator : SqlServerMigrationsSqlGenerator
 {
     public MyMigrationsSqlGenerator(
         MigrationsSqlGeneratorDependencies dependencies,

samples/core/Schemas/Migrations/CustomOperationMultiSql.cs

@@ -6,7 +6,7 @@
 internal static class MultiSqlMigrationBuilderExtensions
 {
     #region snippet_CustomOperationMultiSql
-    private static OperationBuilder<SqlOperation> CreateUser(
+    public static OperationBuilder<SqlOperation> CreateUser(
         this MigrationBuilder migrationBuilder,
         string name,
         string password)

samples/core/Schemas/Migrations/CustomOperationSql.cs

@@ -5,7 +5,7 @@
 internal static class SqlMigrationBuilderExtensions
 {
     #region snippet_CustomOperationSql
-    private static OperationBuilder<SqlOperation> CreateUser(
+    public static OperationBuilder<SqlOperation> CreateUser(
         this MigrationBuilder migrationBuilder,
         string name,
         string password)

samples/core/Spatial/Projections/GeometryExtensions.cs

@@ -6,7 +6,7 @@
 namespace NetTopologySuite.Geometries
 {
     #region snippet_GeometryExtensions
-    internal static class GeometryExtensions
+    public static class GeometryExtensions
     {
         private static readonly CoordinateSystemServices _coordinateSystemServices
             = new CoordinateSystemServices(

samples/core/Spatial/SqlServer/Models/City.cs

@@ -5,7 +5,7 @@ namespace SqlServer.Models
 {
     #region snippet_City
     [Table("Cities", Schema = "Application")]
-    internal class City
+    public class City
     {
         public int CityID { get; set; }
 

samples/core/Spatial/SqlServer/Models/Country.cs

@@ -5,7 +5,7 @@ namespace SqlServer.Models
 {
     #region snippet_Country
     [Table("Countries", Schema = "Application")]
-    internal class Country
+    public class Country
     {
         public int CountryID { get; set; }