[SCOPED] Fix spacing (#34289)

Author: rwestMSFT

docs/analytics-platform-system/appliance-configuration.md

@@ -39,7 +39,7 @@ Provides checklists for the tasks required to configure Analytics Platform Syste
     1. Launch the **Configuration Manager** from the **Start** menu of the PDW Control node. The first screen of the Configuration Manager displays the appliance topology, which was created by your IHV. It is a list of the hardware nodes recognized by your SQL Server PDW software as part of your appliance. You should not need to change any settings on the Appliance Topology screen.  
 
 ## <a id="CMTasks"></a> Perform Configuration Manager Tasks
-The SQL Server PDW**Configuration Manager** (PDWCM) is an appliance administration tool that SQL Server PDW system administrators use to perform appliance-level operations and to change appliance-level settings. For example, use PDWCM to reset passwords, set the time zone, change IP addresses, configure SSL certificates, enable remote access through the firewall, start or stop the appliance, and set Instant File Initialization.  
+The SQL Server PDW **Configuration Manager** (PDWCM) is an appliance administration tool that SQL Server PDW system administrators use to perform appliance-level operations and to change appliance-level settings. For example, use PDWCM to reset passwords, set the time zone, change IP addresses, configure SSL certificates, enable remote access through the firewall, start or stop the appliance, and set Instant File Initialization.  
 
 Use **Configuration Manager** to perform the following configuration tasks.  
 

docs/analytics-platform-system/launch-the-configuration-manager.md

@@ -16,7 +16,7 @@ This topic provides instructions for launching the **Configuration Manager** for
 ## Before You Begin  
 
 ### Prerequisites  
-The Analytics Platform System**Configuration Manager** can only be run by the appliance domain administrator. To run this tool, you need the password for the appliance domain administrator. To create additional APS administrators, see [Create an APS Domain Administrator (APS)](create-an-aps-domain-administrator-aps.md).  
+The Analytics Platform System **Configuration Manager** can only be run by the appliance domain administrator. To run this tool, you need the password for the appliance domain administrator. To create additional APS administrators, see [Create an APS Domain Administrator (APS)](create-an-aps-domain-administrator-aps.md).  
 
 ## <a name="Accessing"></a>Launch the Configuration Manager Tool  
 To run the Configuration Manager, use Remote Desktop to connect to the PDW Control node (**_PDW_region_-CTL01**)node, and log in as _appliance_domain_**\Administrator**. When starting the **Configuration Manager** program, use the **Run as Administrator** option to ensure that your administrator credentials are used.  

docs/analytics-platform-system/load-with-ssis.md

@@ -236,7 +236,7 @@ Specify the data flow from source to destination.
 
 Run the package on your computer Integration Services.  
 
-1.  In the Integration Services**Solution Explorer** (right column), right-click `Package.dtsx` and select **Execute**.  
+1.  In the Integration Services **Solution Explorer** (right column), right-click `Package.dtsx` and select **Execute**.  
 
 2.  The package will run and the progress plus any errors will be shown on the **Progress** pane. Use a SQL client to confirm the load, or monitor the load via the SQL Server PDW Admin Console.  
 

docs/analytics-platform-system/password-reset.md

@@ -34,7 +34,7 @@ The **sa** login in SQL Server. **sa** is a member of the **sysadmin** fixed ser
 Both the domain administrator credentials and the system administrator credentials adhere to the password strength policies for each type of credential. When changing the domain administrator credentials, the new password is updated to the domain where needed throughout SQL Server PDW.  
 
 > [!IMPORTANT]  
-> SQL Server PDW does not support the dollar sign character (**$**) in the domain administrator or local administrator passwords. The characters **^ % &** are permitted in passwords, however PowerShell regards these as special characters. If any of these characters are used in passwords for the system administrator or SQL Server**sa** accounts (the **AdminPassword** and **PdwSAPassword** parameters during setup) then setup, including INSTALL, UPGRADE, REPLACENODE, and PATCHING, will fail. To ensure a successful upgrade when current passwords contain unsupported characters, change these passwords so that they do not contain such characters before running upgrade. After upgrade completes, you can set these passwords back to their original values. For more information about password requirements, see [ALTER LOGIN](../t-sql/statements/alter-login-transact-sql.md).  
+> SQL Server PDW does not support the dollar sign character (**$**) in the domain administrator or local administrator passwords. The characters **^ % &** are permitted in passwords, however PowerShell regards these as special characters. If any of these characters are used in passwords for the system administrator or SQL Server **sa** accounts (the **AdminPassword** and **PdwSAPassword** parameters during setup) then setup, including INSTALL, UPGRADE, REPLACENODE, and PATCHING, will fail. To ensure a successful upgrade when current passwords contain unsupported characters, change these passwords so that they do not contain such characters before running upgrade. After upgrade completes, you can set these passwords back to their original values. For more information about password requirements, see [ALTER LOGIN](../t-sql/statements/alter-login-transact-sql.md).  
   
 ## To reset a password  
 

docs/analytics-platform-system/pdw-certificate-provisioning.md

@@ -34,7 +34,7 @@ Although the connection through the self-signed certificate encrypts in-flight d
   
 The certification path must contain the fully qualified domain name that maps to the Control node Cluster IP Address (recommended) or the name that users type into their browser address bars to access the **Admin Console**.  
 
-Use the Analytics Platform System**Configuration Manager** to add or remove the trusted certificate. Directly using the Microsoft Windows HTTP Services Certificate Configuration Tool (**winHttpCertCfg.exe**) to manage the certificate is unsupported.  
+Use the Analytics Platform System **Configuration Manager** to add or remove the trusted certificate. Directly using the Microsoft Windows HTTP Services Certificate Configuration Tool (**winHttpCertCfg.exe**) to manage the certificate is unsupported.  
 
 ## Import or Remove the Certificate
 The following instructions show how to import or remove the appliance certificate.

docs/analytics-platform-system/tempdb-database.md

@@ -27,7 +27,7 @@ global temporary table
 pdwtempdb  
 **pdwtempdb** is the database that stores local temporary tables.  
 
-PDW does not implement temporary tables by using the SQL Server**tempdb** database. Instead, PDW stores them in a database called pdwtempdb. This database exists on each Compute node and is invisible to the user through the PDW interfaces. In the Admin Console, on the storage page, you will see these accounted for in a PDW system database called **tempdb-sql**.  
+PDW does not implement temporary tables by using the SQL Server **tempdb** database. Instead, PDW stores them in a database called pdwtempdb. This database exists on each Compute node and is invisible to the user through the PDW interfaces. In the Admin Console, on the storage page, you will see these accounted for in a PDW system database called **tempdb-sql**.  
 
 tempdb  
 **tempdb** is the SQL Server tempdb database. It uses minimal logging. SQL Server uses tempdb on the Compute nodes to store temporary tables that it needs in the course of performing SQL Server operations.  
@@ -46,15 +46,15 @@ SQL Server PDW drops tables from **tempdb** when:
 SQL Server PDW performs the same operations on temporary tables and permanent tables unless explicitly stated otherwise. For example, the data in local temporary tables, just like permanent tables, is either distributed or replicated across the Compute nodes.  
 
 ## <a name="LimitationsRestrictions"></a>Limitations and Restrictions  
-Limitations and restrictions on the SQL Server PDW**tempdb** database. You *cannot:*  
+Limitations and restrictions on the SQL Server PDW **tempdb** database. You *cannot:*  
 
 -   Create a global temporary table that begins with ##.  
 
 -   Perform a backup or restore of **tempdb**.  
 
 -   Modify permissions to **tempdb** with the **GRANT**, **DENY**, or **REVOKE** statements.  
 
--   Execute **DBCC SHRINKLOG** for **tempdb**tempdb.  
+-   Execute **DBCC SHRINKLOG** for the **tempdb** database.  
 
 -   Perform DDL operations on **tempdb**. There are a couple exceptions to this. For details, see the following list of limitations and restrictions on local temporary tables.  
 

docs/connect/ado-net/sql/sqlclient-support-high-availability-disaster-recovery.md

@@ -79,7 +79,7 @@ When `ApplicationIntent=ReadOnly`, the client requests a read workload when conn
 
 The `ApplicationIntent` keyword does not work with legacy, read-only databases.  
 
-A database can allow or disallow read workloads on the targeted Always On database. (This is done with the `ALLOW_CONNECTIONS` clause of the `PRIMARY_ROLE` and `SECONDARY_ROLE`Transact-SQL statements.)  
+A database can allow or disallow read workloads on the targeted Always On database. (This is done with the `ALLOW_CONNECTIONS` clause of the `PRIMARY_ROLE` and `SECONDARY_ROLE` Transact-SQL statements.)  
 
 The `ApplicationIntent` keyword is used to enable read-only routing.  
 

docs/connect/ado-net/sql/transaction-bulk-copy-operations.md

@@ -33,7 +33,7 @@ In the example, the source table and destination table each include an `Identity
 The bulk copy operation is executed with the <xref:Microsoft.Data.SqlClient.SqlBulkCopy.BatchSize%2A> property set to 10. When the operation comes across the invalid row, an exception is thrown. In this first example, the bulk copy operation is non-transacted. All batches that are copied up to the point of the error are committed. The batch containing the duplicate key is rolled back, and the bulk copy operation is halted before it processes any remaining batches.  
 
 > [!NOTE]
->  This sample will not run unless you have created the work tables as described in [Bulk copy example setup](bulk-copy-example-setup.md). This code is provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL`INSERT … SELECT` statement to copy the data.  
+>  This sample will not run unless you have created the work tables as described in [Bulk copy example setup](bulk-copy-example-setup.md). This code is provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL` INSERT ... SELECT` statement to copy the data.  
   
 [!code-csharp[DataWorks SqlBulkCopyOptions_Default#1](~/../sqlclient/doc/samples/SqlBulkCopyOptions_Default.cs#1)]
 
@@ -48,7 +48,7 @@ You can explicitly specify the <xref:Microsoft.Data.SqlClient.SqlBulkCopyOptions
 The following console application is similar to the previous example, with one exception: In this example, the bulk copy operation manages its own transactions. All batches that are copied up to the point of the error are committed. The batch containing the duplicate key is rolled back, and the bulk copy operation is halted before it processes any remaining batches. 
 
 > [!IMPORTANT]
->  This sample will not run unless you have created the work tables as described in [Bulk copy example setup](bulk-copy-example-setup.md). This code is provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL`INSERT … SELECT` statement to copy the data.  
+>  This sample will not run unless you have created the work tables as described in [Bulk copy example setup](bulk-copy-example-setup.md). This code is provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL `INSERT ... SELECT` statement to copy the data.  
   
 [!code-csharp[DataWorks SqlBulkCopyOptions_UseInternalTransaction#1](~/../sqlclient/doc/samples/SqlBulkCopyOptions_UseInternalTransaction.cs#1)]
 
@@ -60,7 +60,7 @@ If you need to roll back the entire bulk copy operation because an error occurs,
 The following console application is similar to the first (non-transacted) example, with one exception: in this example, the bulk copy operation is included in a larger, external transaction. When the primary key violation error occurs, the entire transaction is rolled back and no rows are added to the destination table.  
 
 > [!IMPORTANT]
->  This sample will not run unless you have created the work tables as described in [Bulk copy example setup](bulk-copy-example-setup.md). This code is provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL`INSERT … SELECT` statement to copy the data.  
+>  This sample will not run unless you have created the work tables as described in [Bulk copy example setup](bulk-copy-example-setup.md). This code is provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL` INSERT ... SELECT` statement to copy the data.  
   
 [!code-csharp[DataWorks SqlBulkCopy_ExternalTransaction#1](~/../sqlclient/doc/samples/SqlBulkCopy_ExternalTransaction.cs#1)]
 

docs/connect/jdbc/connecting-using-azure-active-directory-authentication.md

@@ -63,7 +63,7 @@ The following table lists required library dependencies for each authentication
 | `ActiveDirectoryPassword`<br/>`ActiveDirectoryIntegrated` | 6.2.2 - 6.4 | `Adal4j` 1.4.0 |
 | `ActiveDirectoryPassword`<br/>`ActiveDirectoryIntegrated` | 7.0 | `Adal4j` 1.6.0 |
 | `ActiveDirectoryPassword`<br/>`ActiveDirectoryIntegrated` | 7.2 | `Adal4j` 1.6.3<br/>`Client-Runtime-for-AutoRest` 1.6.5 |
-| `ActiveDirectoryPassword`<br/>`ActiveDirectoryIntegrated` | 7.4 - 8.2 | `Adal4j`l4j 1.6.4<br/>`Client-Runtime-for-AutoRest` 1.7.0 |
+| `ActiveDirectoryPassword`<br/>`ActiveDirectoryIntegrated` | 7.4 - 8.2 | `Adal4j` 1.6.4<br/>`Client-Runtime-for-AutoRest` 1.7.0 |
 | `ActiveDirectoryPassword`<br/>`ActiveDirectoryIntegrated` | 8.4 | `Adal4j` 1.6.5<br/>`Client-Runtime-for-AutoRest` 1.7.4 |
 | `ActiveDirectoryPassword`<br/>`ActiveDirectoryIntegrated`<br/>`ActiveDirectoryInteractive`<br/>`ActiveDirectoryServicePrincipal` | 9.2 | `msal4j` 1.7.1 |
 | `ActiveDirectoryPassword`<br/>`ActiveDirectoryIntegrated`<br/>`ActiveDirectoryInteractive`<br/>`ActiveDirectoryServicePrincipal` | 9.4 | `msal4j` 1.10.1 |

docs/connect/jdbc/reference/execute-method-java-lang-string-int.md

@@ -19,8 +19,8 @@ apitype: "Assembly"
 
 ```Java
 public final boolean execute(
-	java.lang.String sql,
-	int[] columnIndexes)
+    java.lang.String sql,
+    int[] columnIndexes)
 ```
 
 #### Parameters
@@ -30,7 +30,7 @@ A **String** that contains a SQL statement.
 
 *columnIndexes*
 
-An array of **int**s that indicates the column indexes of the auto-generated keys that should be made available.
+An array of **int** that indicates the column indexes of the auto-generated keys that should be made available.
 
 ## Return Value
 **true** if the first result is a result set. Otherwise, **false**.