[SCOPED] Update SQLCMD mode links

Author: rwestMSFT

docs/database-engine/availability-groups/windows/create-clustered-dtc-for-an-always-on-availability-group.md

@@ -18,7 +18,7 @@ This article walks you through a complete configuration of a clustered DTC resou
 
 The walkthrough creates a clustered DTC resource and the [!INCLUDE [ssnoversion-md](../../../includes/ssnoversion-md.md)] AGs to align with the requirements at [How to cluster the DTC service for an Always On availability group](cluster-dtc-for-sql-server-2016-availability-groups.md).
 
-The walkthrough uses PowerShell and Transact-SQL (T-SQL) scripts. Many of the T-SQL scripts require **SQLCMD Mode** to be enabled. For more information on **SQLCMD Mode**, see [Edit SQLCMD Scripts with Query Editor](../../../tools/sqlcmd/edit-sqlcmd-scripts-query-editor.md). The PowerShell module `FailoverClusters` must be imported. For more information about importing a PowerShell module, see [Importing a PowerShell Module](/powershell/scripting/developer/module/importing-a-powershell-module). This walkthrough is based on the following configuration options:
+The walkthrough uses PowerShell and Transact-SQL (T-SQL) scripts. Many of the T-SQL scripts require **SQLCMD Mode** to be enabled. For more information on **SQLCMD Mode**, see [Edit SQLCMD scripts with Query Editor](/ssms/scripting/sqlcmd-scripts-query-editor). The PowerShell module `FailoverClusters` must be imported. For more information about importing a PowerShell module, see [Importing a PowerShell Module](/powershell/scripting/developer/module/importing-a-powershell-module). This walkthrough is based on the following configuration options:
 
 - All requirements from [Prerequisites, restrictions, and recommendations for Always On availability groups](prereqs-restrictions-recommendations-always-on-availability.md) are met.
 - The domain is `contoso.lab`.

docs/relational-databases/replication/concepts/replication-system-stored-procedures-concepts.md

@@ -125,7 +125,7 @@ GO
 ### Creating a SQL Query File in SQL Server Management Studio  
  A replication [!INCLUDE[tsql](../../../includes/tsql-md.md)] script file can be created as a SQL Query file in a [!INCLUDE[ssManStudioFull](../../../includes/ssmanstudiofull-md.md)] project. After the script is written, a connection can be made to the database for this query file and the script can be executed. For more information about how to create [!INCLUDE[tsql](../../../includes/tsql-md.md)] scripts by using [!INCLUDE[ssManStudioFull](../../../includes/ssmanstudiofull-md.md)], see [Query and Text Editors (SQL Server Management Studio)](/ssms/f1-help/database-engine-query-editor-sql-server-management-studio).  
 
- To use a script that includes scripting variables, [!INCLUDE[ssManStudioFull](../../../includes/ssmanstudiofull-md.md)] must be running in **sqlcmd** mode. In **sqlcmd** mode, the Query Editor accepts additional syntax specific to **sqlcmd**, such as `:setvar`, which is used to a value for a variable. For more information about **sqlcmd** mode, see [Edit SQLCMD Scripts with Query Editor](../../../tools/sqlcmd/edit-sqlcmd-scripts-query-editor.md). In the following script, `:setvar` is used to provide a value for the `$(DistPubServer)` variable.  
+ To use a script that includes scripting variables, [!INCLUDE[ssManStudioFull](../../../includes/ssmanstudiofull-md.md)] must be running in SQLCMD mode. In SQLCMD mode, the Query Editor accepts additional syntax specific to **sqlcmd**, such as `:setvar`, which is used to a value for a variable. For more information about SQLCMD mode, see [Edit SQLCMD scripts with Query Editor](/ssms/scripting/sqlcmd-scripts-query-editor). In the following script, `:setvar` is used to provide a value for the `$(DistPubServer)` variable.  
 
 ```  
 :setvar DistPubServer N'MyPublisherAndDistributor';  

docs/tools/sqlcmd/sqlcmd-start-utility.md

@@ -18,7 +18,7 @@ monikerRange: ">=aps-pdw-2016 || =azuresqldb-current || =azure-sqldw-latest || >
 
 [!INCLUDE [SQL Server Azure SQL Database Azure SQL Managed Instance Azure Synapse Analytics PDW FabricSQLDB](../../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw-fabricsqldb.md)]
 
-The [sqlcmd utility](sqlcmd-utility.md) lets you enter Transact-SQL statements, system procedures, and script files at the command prompt, in [Edit SQLCMD Scripts with Query Editor](edit-sqlcmd-scripts-query-editor.md) in [About SQL Server Management Studio](/ssms/menu-help/about-sql-server-management-studio), and in a Windows script file or in [an operating system (Cmd.exe) job step](/ssms/agent/create-a-cmdexec-job-step) of a SQL Server Agent job.
+The [sqlcmd utility](sqlcmd-utility.md) lets you enter Transact-SQL statements, system procedures, and script files at the command prompt, in [SQLCMD mode](/ssms/scripting/sqlcmd-scripts-query-editor) in [SQL Server Management Studio](/ssms/sql-server-management-studio-ssms), and in a Windows script file or in [an operating system (Cmd.exe) job step](/ssms/agent/create-a-cmdexec-job-step) of a SQL Server Agent job.
 
 > [!NOTE]  
 > Windows Authentication is the default authentication mode for **sqlcmd**. To use SQL Server Authentication, you must specify a user name and password by using the `-U` and `-P` options.
@@ -51,7 +51,7 @@ By default, [!INCLUDE [ssExpress](../../includes/ssexpress-md.md)] installs as t
 
 ## Related content
 
-- [Edit SQLCMD Scripts with Query Editor](edit-sqlcmd-scripts-query-editor.md)
+- [Edit SQLCMD scripts with Query Editor](/ssms/scripting/sqlcmd-scripts-query-editor)
 - [Execute T-SQL from a script file with sqlcmd](sqlcmd-run-transact-sql-script-files.md)
 - [Use sqlcmd](sqlcmd-use-utility.md)
 - [SQL Server Utilities Statements - GO](../../t-sql/language-elements/sql-server-utilities-statements-go.md)

docs/tools/sqlcmd/sqlcmd-use-scripting-variables.md

@@ -356,6 +356,6 @@ These statements return the row.
 - [use the utility](sqlcmd-use-utility.md)
 - [Use sqlcmd with scripting variables](sqlcmd-use-scripting-variables.md)
 - [Connect to SQL Server with sqlcmd](sqlcmd-connect-database-engine.md)
-- [Edit SQLCMD Scripts with Query Editor](edit-sqlcmd-scripts-query-editor.md)
+- [Edit SQLCMD scripts with Query Editor](/ssms/scripting/sqlcmd-scripts-query-editor)
 - [Manage Job Steps](/ssms/agent/manage-job-steps)
 - [Create a CmdExec Job Step](/ssms/agent/create-a-cmdexec-job-step)

docs/tools/sqlcmd/sqlcmd-use-utility.md

@@ -31,7 +31,7 @@ monikerRange: ">=aps-pdw-2016 || =azuresqldb-current || =azure-sqldw-latest || >
 
 - Submit a **sqlcmd** job either by specifying a single T-SQL statement to execute, or by pointing the utility to a text file that contains T-SQL statements to execute. The output is directed to a text file, but can also be displayed at the command prompt.
 
-- [SQLCMD mode](edit-sqlcmd-scripts-query-editor.md) in SQL Server Management Studio (SSMS) Query Editor.
+- [SQLCMD mode](/ssms/scripting/sqlcmd-scripts-query-editor) in SQL Server Management Studio (SSMS).
 - SQL Server Management Objects (SMO).
 - SQL Server Agent CmdExec jobs.
 
@@ -560,6 +560,6 @@ If the provider specifies `ForceProtocolEncryption = True`, then encryption is e
 
 - [sqlcmd utility](sqlcmd-utility.md)
 - [Use sqlcmd with scripting variables](sqlcmd-use-scripting-variables.md)
-- [Edit SQLCMD Scripts with Query Editor](edit-sqlcmd-scripts-query-editor.md)
+- [Edit SQLCMD scripts with Query Editor](/ssms/scripting/sqlcmd-scripts-query-editor)
 - [Manage Job Steps](/ssms/agent/manage-job-steps)
 - [Create a CmdExec Job Step](/ssms/agent/create-a-cmdexec-job-step)

docs/tools/sqlcmd/sqlcmd-utility.md

@@ -1021,5 +1021,5 @@ Using `-V 16` in combination with checking the exit code and `DOS ERRORLEVEL` ca
 - [Execute T-SQL from a script file with sqlcmd](sqlcmd-run-transact-sql-script-files.md)
 - [Use sqlcmd](sqlcmd-use-utility.md)
 - [Connect to SQL Server with sqlcmd](sqlcmd-connect-database-engine.md)
-- [Edit SQLCMD Scripts with Query Editor](edit-sqlcmd-scripts-query-editor.md)
+- [Edit SQLCMD scripts with Query Editor](/ssms/scripting/sqlcmd-scripts-query-editor)
 - [Create a CmdExec Job Step](/ssms/agent/create-a-cmdexec-job-step)