review feedback

Author: dzsquared

docs/tools/sql-database-projects/concepts/package-references.md

@@ -41,7 +41,7 @@ The following example includes a package reference to the `Contoso.AdventureWork
 
 ### System databases
 
-The SQL system databases (`master`, `msdb`) are been published on NuGet.org as database reference packages. These packages contain the schema for the system databases and can be used as package references in SQL projects. The system database packages are versioned to align with the version of SQL Server they're associated with. For example, the `master` system database package for SQL Server 2022 is `Microsoft.SqlServer.Dacpacs.Master` version `160.2.1` and can be added to a SQL project as a package reference:
+The SQL system databases (`master`, `msdb`) are published on NuGet.org as database reference packages. These packages contain the schema for the system databases and can be used as package references in SQL projects. The system database packages are versioned to align with the version of SQL Server they're associated with. For example, the `master` system database package for SQL Server 2022 is `Microsoft.SqlServer.Dacpacs.Master` version `160.2.1` and can be added to a SQL project as a package reference:
 
 ```xml
 ...

docs/tools/sql-database-projects/concepts/pre-post-deployment-scripts.md

@@ -91,4 +91,4 @@ This script `scripts\before-script.sql` is executed before the deployment plan i
 
 - [SqlPackage Publish parameters, properties, and SQLCMD variables](../../sqlpackage/sqlpackage-publish.md)
 - [SQLCMD variables overview](sqlcmd-variables.md)
-- [Tutorial: Create and deploy a SQL project](../tutorials/creating-and-deploying-a-sql-project.md)
+- [Tutorial: Create and deploy a SQL project](../tutorials/create-deploy-sql-project.md)

docs/tools/sql-database-projects/concepts/schema-comparison.md

@@ -41,7 +41,7 @@ The differences between source and target appear in a grid for easy review. Comp
 - SQL database project
 - `.dacpac` file
 
-In schema compare you can drill into and review each difference in the results grid or in script form where line by line details of the changes are available. You can also selectively exclude specific differences before updating the target. The schema compare tooling is available in Visual Studio, Azure Data Studio, and the command line.
+In schema compare you can drill into and review each difference in the results grid or in script form where details of the changes are available at a per-line level. You can also selectively exclude specific differences before updating the target. The schema compare tooling is available in Visual Studio, Azure Data Studio, and the command line.
 
 ### Schema comparison options
 
@@ -57,7 +57,7 @@ The object types that are included in the comparison can also be configured. The
 
 ### Schema compare files
 
-The comparison definition for schema compare can be saved as an `.scmp` file. This file stores information about the schema comparison in XML and includes:
+The comparison definition for schema compare can be saved as an `.scmp` file, known as a *schema compare file*. This file stores information about the schema comparison in XML and includes:
 
 - source and target connection information
 - comparison options
@@ -99,7 +99,7 @@ An `.scmp` file can be opened in Visual Studio or Azure Data Studio to easily ru
 
    To change the grouping preference, select the **Group Results** dropdown list in the toolbar. Select **Type** to group the results by object type (for example, by tables, views, or stored procedures).
 
-7. By default all differences are included in the scope of the Update Target action. You can exclude differences that you don't want to synchronize. To do so, uncheck the **Action** column in the center of each row. Alternatively, right-click a row in the Schema pane, and select **Exclude**. The row is immediately grayed out. When it's time to update the target database, this row isn't considered for any pending changes.
+7. By default all differences are included in the scope of the Update Target action. You can exclude differences that you don't want to synchronize. To do so, uncheck the **Action** column in the center of each row. Alternatively, right-click a row in the Schema pane, and select **Exclude**. The row is immediately grayed out. When schema compare is used to update the target database, this row isn't considered for any pending changes.
 
    You can also right-click on a group row and select **Exclude All** or **Include All**, which is equivalent to unchecking or checking all differences in that group. When you group results by schema this is a useful way to include or exclude all changes to a specific schema.
 
@@ -144,7 +144,7 @@ To update the schema of the target, you have two options. You can update the tar
 
     :::image type="content" source="media/schema-comparison/ads-schema-compare.png" alt-text="Screenshot of Schema comparison interface in Azure Data Studio comparing a database against a project." lightbox="media/schema-comparison/ads-schema-compare.png":::
 
-5. By default all differences are included in the scope of the Update Target action. You can exclude differences that you don't want to synchronize. To do so, uncheck the **Action** column in the center of each row. Alternatively, right-click a row in the Schema pane, and select **Exclude**. The row is immediately grayed out. When it's time to update the target database, this row isn't considered for any pending changes.
+5. By default all differences are included in the scope of the Update Target action. You can exclude differences that you don't want to synchronize. To do so, uncheck the **Action** column in the center of each row. Alternatively, right-click a row in the Schema pane, and select **Exclude**. The row is immediately grayed out. When schema compare is used to update the target database, this row isn't considered for any pending changes.
 
    You can also right-click on a group row and select **Exclude All** or **Include All**, which is equivalent to unchecking or checking all differences in that group. When you group results by schema this is a useful way to include or exclude all changes to a specific schema.
 
@@ -164,6 +164,6 @@ To update the schema of the target, you have two options. You can update the tar
 
 ## Related content
 
-- [Compare a database and a project](../howto/compare-a-database-and-a-project.md)
-- [Tutorial: start from an existing database](../tutorials/start-from-an-existing-database.md)
+- [Compare a database and a project](../howto/compare-database-project.md)
+- [Tutorial: start from an existing database](../tutorials/start-from-existing-database.md)
 - [SqlServer.Dac.Compare namespace](/dotnet/api/microsoft.sqlserver.dac.compare)

docs/tools/sql-database-projects/concepts/sql-code-analysis/sql-code-analysis.md

@@ -14,7 +14,7 @@ zone_pivot_groups: sq1-sql-projects-tools
 
 [!INCLUDE [SQL Server Azure SQL Database Azure SQL Managed Instance](../../../../includes/applies-to-version/sql-asdb-asdbmi.md)]
 
-You can eliminate potential design and naming problems and avoid performance pitfalls by analyzing your database code. The concepts are very similar to performing static analysis to detect and correct defects in managed code. You configure which analysis rules you want to apply to your database code, analyze the code, and then correct or ignore the issues that you identify. Before you can analyze your database code, you must first import your database schema into a database project. For more information, see [Start from an existing database](../../tutorials/start-from-an-existing-database.md).
+You can eliminate potential design and naming problems and avoid performance pitfalls by analyzing your database code. The concepts are very similar to performing static analysis to detect and correct defects in managed code. You configure which analysis rules you want to apply to your database code, analyze the code, and then correct or ignore the issues that you identify. Before you can analyze your database code, you must first import your database schema into a database project. For more information, see [Start from an existing database](../../tutorials/start-from-existing-database.md).
 
 By performing static analysis with the [provided rules](#provided-rules), you can identify problems that fall into the following categories:
 
@@ -48,7 +48,7 @@ A SQL project file can contain two properties, `RunSqlCodeAnalysis` and `SqlCode
 ...
 ```
 
-The `SqlCodeAnalysisRules` element specifies the rules and their error/warning behavior. In the following example the rules Microsoft.Rules.Data.SR0006 and Microsoft.Rules.Data.SR0007 are disabled and the a detection for the rule Microsoft.Rules.Data.SR0008 will result in a build error.
+The `SqlCodeAnalysisRules` element specifies the rules and their error/warning behavior. In the following example the rules Microsoft.Rules.Data.SR0006 and Microsoft.Rules.Data.SR0007 are disabled and a detection for the rule Microsoft.Rules.Data.SR0008 will result in a build error.
 
 ```xml
 <?xml version="1.0" encoding="utf-8"?>

docs/tools/sql-database-projects/concepts/sql-projects-extensibility.md

@@ -39,6 +39,6 @@ Deployment contributors are reusable through parameterization and can be used in
 ## Related content
 
 - [Extending the Database Features](../../../ssdt/extending-the-database-features.md)
-- [Tutorial: Create and deploy a SQL project](../tutorials/creating-and-deploying-a-sql-project.md)
+- [Tutorial: Create and deploy a SQL project](../tutorials/create-deploy-sql-project.md)
 - [SqlPackage Publish parameters, properties, and SQLCMD variables](../../sqlpackage/sqlpackage-publish.md)
 - [Code analysis rules extensibility overview](code-analysis-extensibility.md)

docs/tools/sql-database-projects/concepts/sqlcmd-variables.md

@@ -105,5 +105,5 @@ SqlPackage /Action:Publish /SourceFile:AdventureWorks.dacpac /TargetConnectionSt
 ## Related content
 
 - [SqlPackage Publish parameters, properties, and SQLCMD variables](../../sqlpackage/sqlpackage-publish.md)
-- [Tutorial: Create and deploy a SQL project](../tutorials/creating-and-deploying-a-sql-project.md)
+- [Tutorial: Create and deploy a SQL project](../tutorials/create-deploy-sql-project.md)
 - [Database Project Settings](../../../ssdt/database-project-settings.md)

docs/tools/sql-database-projects/concepts/target-platform.md

@@ -85,5 +85,5 @@ When publishing a SQL project, the target platform of the project must match the
 ## Related content
 
 - [SqlPackage Publish parameters, properties, and SQLCMD variables](../../sqlpackage/sqlpackage-publish.md)
-- [Tutorial: Create and deploy a SQL project](../tutorials/creating-and-deploying-a-sql-project.md)
+- [Tutorial: Create and deploy a SQL project](../tutorials/create-deploy-sql-project.md)
 - [Database Project Settings](../../../ssdt/database-project-settings.md)

…sql-database-projects/getting-started.md …ols/sql-database-projects/get-started.mddocs/tools/sql-database-projects/getting-started.md renamed to docs/tools/sql-database-projects/get-started.md docs/tools/sql-database-projects/getting-started.md renamed to docs/tools/sql-database-projects/get-started.md

@@ -65,7 +65,7 @@ dotnet new install Microsoft.Build.Sql.Templates
 
 ## Create a new project
 
-We start our project by creating a new SQL database project before manually adding objects to it. There are other ways to create a project that enable immediately populating the project with objects from an existing database, such as using the [schema comparison tools](howto/compare-a-database-and-a-project.md).
+We start our project by creating a new SQL database project before manually adding objects to it. There are other ways to create a project that enable immediately populating the project with objects from an existing database, such as using the [schema comparison tools](howto/compare-database-project.md).
 
 ::: zone pivot="sq1-visual-studio"
 
@@ -247,6 +247,6 @@ sqlpackage /Action:Publish /SourceFile:bin/Debug/projectname.dacpac /TargetConne
 
 ## Related content
 
-- [Compare a database and a project](howto/compare-a-database-and-a-project.md)
-- [Convert an original SQL project to an SDK-style project](howto/convert-an-original-sql-project.md)
+- [Compare a database and a project](howto/compare-database-project.md)
+- [Convert an original SQL project to an SDK-style project](howto/convert-original-sql-project.md)
 - [Analyze T-SQL code to find defects](howto/analyze-t-sql-code-to-find-defects.md)

docs/tools/sql-database-projects/howto/analyze-t-sql-code-to-find-defects.md

@@ -20,7 +20,7 @@ For this initial assessment, you want to find all the potential problems in the
 
 ## Prerequisites
 
-Before you can analyze the code in a database project, you must already have a SQL project. For more information on using an existing database to create a project, see [Tutorial: start from an existing database](../tutorials/start-from-an-existing-database.md).
+Before you can analyze the code in a database project, you must already have a SQL project. For more information on using an existing database to create a project, see [Tutorial: start from an existing database](../tutorials/start-from-existing-database.md).
 
 ## Enable SQL code analysis on project build