Merge pull request #34293 from rwestMSFT/rw-0603-fix-spaces

[SCOPED] Fix spaces

Author: ttorble

docs/database-engine/availability-groups/windows/failover-and-failover-modes-always-on-availability-groups.md

@@ -94,13 +94,13 @@ In rare cases, one or more databases of an availability group might remain in a
  A failover that can be initiated by a database administrator when no secondary replica is SYNCHRONIZED with the primary replica or the primary replica isn't running and no secondary replica is failover ready. Forced failover risks possible data loss and is recommended strictly for disaster recovery. Forced failover is also known as forced manual failover because it can only be initiated manually. This is the only form of failover supported by in asynchronous-commit availability mode.  
 
  [!INCLUDE[ssFosAutoC](../../../includes/ssfosautoc-md.md)]  
- Within a given availability group, a pair of availability replicas (including the current primary replica) that are configured for synchronous-commit mode with automatic failover, if any. An [!INCLUDE[ssFosAuto](../../../includes/ssfosauto-md.md)]takes effect only if the secondary replica is currently SYNCHRONIZED with the primary replica.  
+ Within a given availability group, a pair of availability replicas (including the current primary replica) that are configured for synchronous-commit mode with automatic failover, if any. An [!INCLUDE[ssFosAuto](../../../includes/ssfosauto-md.md)] takes effect only if the secondary replica is currently SYNCHRONIZED with the primary replica.  
 
  [!INCLUDE[ssFosSyncC](../../../includes/ssfossyncc-md.md)]  
- Within a given availability group, a set of two or three availability replicas (including the current primary replica) that are configured for synchronous-commit mode, if any. A [!INCLUDE[ssFosSync](../../../includes/ssfossync-md.md)]takes effect only if the secondary replicas are configured for manual failover mode and at least one secondary replica is currently SYNCHRONIZED with the primary replica.  
+ Within a given availability group, a set of two or three availability replicas (including the current primary replica) that are configured for synchronous-commit mode, if any. A [!INCLUDE[ssFosSync](../../../includes/ssfossync-md.md)] takes effect only if the secondary replicas are configured for manual failover mode and at least one secondary replica is currently SYNCHRONIZED with the primary replica.  
 
  [!INCLUDE[ssFosEntireC](../../../includes/ssfosentirec-md.md)]  
- Within a given availability group, the set of all availability replicas whose operational state is currently ONLINE, regardless of availability mode and of failover mode. The [!INCLUDE[ssFosEntire](../../../includes/ssfosentire-md.md)]becomes relevant when no secondary replica is currently SYNCHRONIZED with the primary replica.  
+ Within a given availability group, the set of all availability replicas whose operational state is currently ONLINE, regardless of availability mode and of failover mode. The [!INCLUDE[ssFosEntire](../../../includes/ssfosentire-md.md)] becomes relevant when no secondary replica is currently SYNCHRONIZED with the primary replica.  
 
 ##  <a name="Overview"></a> Overview of Failover  
  The following table summarizes which forms of failover are supported under different availability and failover modes. For each pairing, the effective availability mode and failover mode are determined by the intersection of the modes of the primary replica plus the modes of one or more secondary replicas.  

docs/database-engine/configure-windows/agent-xps-server-configuration-option.md

@@ -20,7 +20,7 @@ Use the `Agent XPs` option to enable the [!INCLUDE [ssNoVersion](../../includes/
 When you use the [!INCLUDE [ssManStudioFull](../../includes/ssmanstudiofull-md.md)] tool to start the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Agent service, these extended stored procedures are enabled automatically. For more information, see [Surface area configuration](../../relational-databases/security/surface-area-configuration.md).
 
 > [!NOTE]  
-> [!INCLUDE [ssManStudio](../../includes/ssmanstudio-md.md)] Object Explorer doesn't display the contents of the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]Agent node unless these extended stored procedures are enabled regardless of the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Agent service state.
+> [!INCLUDE [ssManStudio](../../includes/ssmanstudio-md.md)] Object Explorer doesn't display the contents of the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Agent node unless these extended stored procedures are enabled regardless of the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Agent service state.
 
 The possible values are:
 

docs/database-engine/configure-windows/external-scripts-enabled-server-configuration-option.md

@@ -35,7 +35,7 @@ You must enable the external script enabled option before you can execute an ext
 
     Install the **Machine Learning Services** feature during [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] setup to enable the execution of external scripts. Be sure to select at least one language during initial setup: either R or Python, or both.
 
-+ For [!INCLUDE[sssql19-md](../../includes/sssql19-md.md)] and later[!INCLUDE[rsql-productnamenew-md](../../includes/rsql-productnamenew-md.md)] has support for all R, Python, Java and other third party languages.
++ For [!INCLUDE[sssql19-md](../../includes/sssql19-md.md)] and later [!INCLUDE[rsql-productnamenew-md](../../includes/rsql-productnamenew-md.md)] has support for all R, Python, Java and other third party languages.
 
 Install the Machine Learning Services and Language Extensions feature during [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] setup to enable the execution of external scripts for any supported language.
 

docs/database-engine/configure-windows/sql-server-browser-service-database-engine-and-ssas.md

@@ -15,7 +15,7 @@ helpviewer_keywords:
 ---
 # SQL Server Browser Service (Database Engine and SSAS)
  [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
-  The [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]Browser program runs as a Windows service. [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Browser listens for incoming requests for [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] resources and provides information about [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] instances installed on the computer. [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Browser contributes to the following actions:  
+  The [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Browser program runs as a Windows service. [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Browser listens for incoming requests for [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] resources and provides information about [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] instances installed on the computer. [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Browser contributes to the following actions:  
 
 -   Browsing a list of available servers  
 

docs/database-engine/database-mirroring/transport-security-database-mirroring-always-on-availability.md

@@ -72,7 +72,7 @@ helpviewer_keywords:
  If connecting endpoints specify both algorithms but in different orders, the endpoint accepting the connection wins.  
 
 > [!NOTE]  
->  The RC4 algorithm is only supported for backward compatibility. New material can only be encrypted using RC4 or RC4_128 when the database is in compatibility level 90 or 100. (Not recommended.) Use a newer algorithm such as one of the AES algorithms instead. In [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)]and higher versions,  material encrypted using RC4 or RC4_128 can be decrypted in any compatibility level.  
+>  The RC4 algorithm is only supported for backward compatibility. New material can only be encrypted using RC4 or RC4_128 when the database is in compatibility level 90 or 100. (Not recommended.) Use a newer algorithm such as one of the AES algorithms instead. In [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)] and higher versions,  material encrypted using RC4 or RC4_128 can be decrypted in any compatibility level.  
 >   
 >  Though considerably faster than AES, RC4 is a relatively weak algorithm, while AES is a relatively strong algorithm. Therefore, we recommend that you use the AES algorithm.  
   

docs/dmx/identifiers-dmx.md

@@ -70,7 +70,7 @@ SELECT * FROM [Targeted Mailing].CONTENT;
 
 -   When you use reserved words for object names or parts of object names.  
 
-     We recommend that you do not use reserved keywords as object names. Databases that you upgrade from earlier versions of [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] may contain identifiers that include words that were not reserved in the earlier version of [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] but that are reserved words for[!INCLUDE[ssnoversion](../includes/ssnoversion-md.md)] [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)]. You can use a delimited identifier to refer to such an object until you can change the object's name.  
+     We recommend that you do not use reserved keywords as object names. Databases that you upgrade from earlier versions of [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] may contain identifiers that include words that were not reserved in the earlier version of [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] but that are reserved words for [!INCLUDE[ssnoversion](../includes/ssnoversion-md.md)] [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)]. You can use a delimited identifier to refer to such an object until you can change the object's name.  
 
 -   When you use characters that are not listed as qualified identifiers.  
 

docs/includes/azdata-package-installation-remove-pip-install.md

@@ -8,7 +8,7 @@ ms.topic: include
 
 ### Python/Pip installation
 
-You can install [!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)]on Linux with yum, apt, or zypper, or on MacOS with Homebrew installation package managers. Before these package managers were available, installation required Python and pip.
+You can install [!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)] on Linux with yum, apt, or zypper, or on MacOS with Homebrew installation package managers. Before these package managers were available, installation required Python and pip.
 
 >[!IMPORTANT]
 >Before you proceed, you need to remove any installation of `azdata` that were installed to the global system Python. The new installers or native-packages add `azdata` to your path and it is impossible to know which one is first.

docs/integration-services/change-data-capture/change-data-capture-service-for-oracle-by-attunity-system-architecture.md

@@ -33,8 +33,8 @@ ms.topic: conceptual
 |Oracle CDC Service: This is a Windows service where the change data capture activity takes place.|Oracle CDC Instance: A sub-process of the Oracle CDC Service that handles change data capture activity for a single source Oracle database (there is one Oracle CDC instance per source Oracle database).|  
 ||Oracle Log Reader: Reads Oracle transaction logs using the Oracle Client.|  
 ||Oracle Client: The Oracle Instant Client used for communication with Oracle. This is a prerequisite that should be obtained from Oracle and installed before installing the Oracle CDC Service.|  
-||[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Change Writer: This writes committed changes made to the captured Oracle table to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]change tables. This component also maintains that capture state within the target [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] database.|  
-||[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]ODBC Client: The Microsoft Native Client for [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)]. This is a prerequisite component that should be obtained from Microsoft and installed before installing the Oracle CDC Service.|  
+||[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Change Writer: This writes committed changes made to the captured Oracle table to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] change tables. This component also maintains that capture state within the target [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] database.|  
+||[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] ODBC Client: The Microsoft Native Client for [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)]. This is a prerequisite component that should be obtained from Microsoft and installed before installing the Oracle CDC Service.|  
 |Oracle CDC Service Configuration: This is a Microsoft Management Console snap-in that creates the Windows service and sets up its configuration.|[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Client: The SQL ADO.NET client that ships with version 4 of the .NET framework.|  
 |Oracle Database: A source Oracle database from which changes to select tables are captured.|Log Miner: An Oracle component through which the Oracle transaction logs are read.|  
 ||Transaction Logs: The online and archived Oracle Redo Logs that are used by Oracle to ensure that the database can roll back transactions and recover from failures (in this case, the Oracle database must operate in archive-log mode).|  

docs/integration-services/connection-manager/data-sources.md

@@ -35,7 +35,7 @@ helpviewer_keywords:
 
  You use a data source object in a package by adding a connection manager that references the data source object to the package. You can add it to the package before you build the package control flow and data flows, or as a step in constructing the control flow or data flow.  
 
- A data source object represents a simple connection to a data source and provides access to the objects in the data store that it references. For example, a data source object that connects to the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]AdventureWorks Sample Database includes all 60 tables from the database.  
+ A data source object represents a simple connection to a data source and provides access to the objects in the data store that it references. For example, a data source object that connects to the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] AdventureWorks Sample Database includes all 60 tables from the database.  
 
  There is no dependency between a data source and the connection managers that reference it. If a data source is no longer part of the project, the packages continue to be valid, because information about the data source, such as its connection type and connection string, is included in the package definition.  
 

docs/integration-services/install-windows/upgrade-integration-services.md

@@ -115,7 +115,7 @@ helpviewer_keywords:
   
 -   Identify the version of packages in the msdb.dbo.sysssispackages system table by checking the value in the packageformat column. The table has a packageformat column that identifies the version of each package. A value of 3 indicates a [!INCLUDE[ssISversion10](../../includes/ssisversion10-md.md)] package. Until you migrate packages to the new package format, the value in the packageformat column does not change.  
 
--   You cannot use the [!INCLUDE[sql2008-md](../../includes/sql2008-md.md)], [!INCLUDE[sql2008r2](../../includes/sql2008r2-md.md)], [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)], or [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] tools to design, run, or manage [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] packages. The [!INCLUDE[sql2008-md](../../includes/sql2008-md.md)], [!INCLUDE[sql2008r2](../../includes/sql2008r2-md.md)], [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)], or [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] tools include the respective versions of [!INCLUDE[ssBIDevStudioFull](../../includes/ssbidevstudiofull-md.md)], the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Import and Export Wizard, and the Package Execution Utility (dtexecui.exe). The upgrade process does not remove the [!INCLUDE[sql2008-md](../../includes/sql2008-md.md)], [!INCLUDE[sql2008r2](../../includes/sql2008r2-md.md)], [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)], or [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)]tools. However, you will not able to use these tools to continue to work with [!INCLUDE[ssISversion10](../../includes/ssisversion10-md.md)] or later packages on a server that has been upgraded.  
+-   You cannot use the [!INCLUDE[sql2008-md](../../includes/sql2008-md.md)], [!INCLUDE[sql2008r2](../../includes/sql2008r2-md.md)], [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)], or [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] tools to design, run, or manage [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] packages. The [!INCLUDE[sql2008-md](../../includes/sql2008-md.md)], [!INCLUDE[sql2008r2](../../includes/sql2008r2-md.md)], [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)], or [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] tools include the respective versions of [!INCLUDE[ssBIDevStudioFull](../../includes/ssbidevstudiofull-md.md)], the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Import and Export Wizard, and the Package Execution Utility (dtexecui.exe). The upgrade process does not remove the [!INCLUDE[sql2008-md](../../includes/sql2008-md.md)], [!INCLUDE[sql2008r2](../../includes/sql2008r2-md.md)], [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)], or [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] tools. However, you will not able to use these tools to continue to work with [!INCLUDE[ssISversion10](../../includes/ssisversion10-md.md)] or later packages on a server that has been upgraded.  
 
 -   By default, in an upgrade installation, [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] is configured to log events that are related to the running of packages to the Application event log. This setting might generate too many event log entries when you use the Data Collector feature of [!INCLUDE[ssSQL19](../../includes/sssql19-md.md)]. The events that are logged include EventID 12288, "Package started," and EventID 12289, "Package finished successfully." To stop logging these two events to the Application event log, open the registry for editing. Then in the registry, locate the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\130\SSIS node, and change the DWORD value of the LogPackageExecutionToEventLog setting from 1 to 0.