Fixes needed, teaching me the details of exact requirements, how much or little leeway there is.

Author: MightyPen

docs/big-data-cluster/hdfs-tiering-mount-adlsgen2.md

@@ -43,7 +43,7 @@ In order to use OAuth credentials to mount, you need to follow the below steps:
 1. In right navigation bar, select "App registrations" and create a new registration
 1. Create a "Web Application and follow the wizard. **Remember the name of the app you create here**. You will need to add this name to your ADLS account as an authorized user. Also note the Application client ID in the overview when you select the App.
 1. Once the web application is created, go to "Certificates&secrets" and create a **New client secret** and select a key duration. **Add** the secret.
-1.     Go back to the App Registrations page, and click on the "Endpoints" at the top. **Note down the "OAuth token endpoint (v2)** URL
+1. Go back to the App Registrations page, and click on the "Endpoints" at the top. **Note down the "OAuth token endpoint (v2)** URL
 1. You should now have the following things noted down for OAuth:
 
     - The "Application Client ID" of the Web Application

docs/database-engine/install-windows/install-sql-server-on-server-core.md

@@ -60,7 +60,7 @@ The Server Core installation option provides a minimal environment for running s
 ## Supported scenarios  
  The following table shows the supported scenario matrix for installing [!INCLUDE[ssCurrent](../../includes/ssnoversion-md.md)] on a Server Core.  
 
-|||  
+| Installation | Valid target |  
 |-|-|  
 |[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] editions|All [!INCLUDE[ssCurrent](../../includes/ssnoversion-md.md)] 64-bit editions |  
 |[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] language|All languages|  
@@ -124,41 +124,41 @@ The Server Core installation option provides a minimal environment for running s
     - Installing [!INCLUDE[ssDE](../../includes/ssde-md.md)]. 
     
     The following example shows how to install a new stand-alone instance that includes [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)][!INCLUDE[ssDE](../../includes/ssde-md.md)]:  
-  
-        ```console
-        ; SQL Server Configuration File  
-        [OPTIONS]  
-  
-        ; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.   
-  
-        ACTION="Install"  
-  
-        ; Specifies features to install, uninstall, or upgrade. The lists of features include SQLEngine, FullText, Replication, AS, IS, and Conn.   
-  
-        FEATURES=SQLENGINE  
-  
-        ; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the ssNoVersion Database Engine, and Analysis Services (AS).  
-  
-        INSTANCENAME="MSSQLSERVER"  
-  
-        ; Specify the Instance ID for the ssNoVersion features you have specified. ssNoVersion directory structure, registry structure, and service names will incorporate the instance ID of the ssNoVersion instance.   
-  
-        INSTANCEID="MSSQLSERVER"  
-  
-        ; Account for ssNoVersion service: Domain\User or system account.   
-  
-        SQLSVCACCOUNT="NT Service\MSSQLSERVER"  
-  
-        ; Windows account(s) to provision as ssNoVersion system administrators.   
-  
-        SQLSYSADMINACCOUNTS="\<DomainName\UserName>"  
-  
-        ; Accept the License agreement to continue with Installation  
-  
-        IAcceptSQLServerLicenseTerms="True"  
-  
-        ```  
-  
+
+    ```console
+    ; SQL Server Configuration File  
+    [OPTIONS]  
+    
+    ; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.   
+    
+    ACTION="Install"  
+    
+    ; Specifies features to install, uninstall, or upgrade. The lists of features include SQLEngine, FullText, Replication, AS, IS, and Conn.   
+    
+    FEATURES=SQLENGINE  
+    
+    ; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the ssNoVersion Database Engine, and Analysis Services (AS).  
+    
+    INSTANCENAME="MSSQLSERVER"  
+    
+    ; Specify the Instance ID for the ssNoVersion features you have specified. ssNoVersion directory structure, registry structure, and service names will incorporate the instance ID of the ssNoVersion instance.   
+    
+    INSTANCEID="MSSQLSERVER"  
+    
+    ; Account for ssNoVersion service: Domain\User or system account.   
+    
+    SQLSVCACCOUNT="NT Service\MSSQLSERVER"  
+    
+    ; Windows account(s) to provision as ssNoVersion system administrators.   
+    
+    SQLSYSADMINACCOUNTS="\<DomainName\UserName>"  
+    
+    ; Accept the License agreement to continue with Installation  
+    
+    IAcceptSQLServerLicenseTerms="True"  
+    
+    ```
+
     -   Installing connectivity components. The following example shows how to install the connectivity components:  
   
         ```console

docs/integration-services/connection-manager/hadoop-connection-manager.md

@@ -195,10 +195,10 @@ On the gateway computer:
 
 Run the following **Ksetup** commands to add a realm entry.
 
-    ```console
-    C:> Ksetup /addkdc REALM.COM <your_kdc_server_address>
-    C:> ksetup /addhosttorealmmap HDFS-service-FQDN REALM.COM
-    ```
+```console
+C:> Ksetup /addkdc REALM.COM <your_kdc_server_address>
+C:> ksetup /addhosttorealmmap HDFS-service-FQDN REALM.COM
+```
 
 ## See also  
  [Hadoop Hive Task](../../integration-services/control-flow/hadoop-hive-task.md)   

docs/integration-services/import-export-data/connect-to-a-mysql-data-source-sql-server-import-and-export-wizard.md

@@ -74,18 +74,18 @@ The user id and password to connect.
 ### Connection string format
 Here's the format of a typical connection string.
 
-    ```console
-    Driver={MySQL ODBC 5.3 Unicode Driver};Server=<server>;Database=<database>;UID=<user id>;PWD=<password>
-    ```
+```console
+Driver={MySQL ODBC 5.3 Unicode Driver};Server=<server>;Database=<database>;UID=<user id>;PWD=<password>
+```
 
 ### Enter the connection string
 Enter the connection string in the **ConnectionString** field, or enter the DSN name in the **Dsn** field, on the **Choose a Data Source** or **Choose a Destination** page. After you enter the connection string, the wizard parses the string and displays the individual properties and their values in the list.
 
 The following example uses this connection string.
 
-    ```console
-    Driver={MySQL ODBC 5.3 Unicode Driver};Server=127.0.0.1;Database=world;UID=root;PWD=********
-    ```
+```console
+Driver={MySQL ODBC 5.3 Unicode Driver};Server=127.0.0.1;Database=world;UID=root;PWD=********
+```
 
 Here's the screen that you see after entering the connection string.
 

docs/integration-services/import-export-data/connect-to-an-odbc-data-source-sql-server-import-and-export-wizard.md

@@ -87,9 +87,9 @@ If you want to provide your connection information with a connection string, the
 
 This example is going to use the following connection string, which connects to Microsoft SQL Server. The database example that is used is **WideWorldImporters** and we're connecting to the SQL Server on the local machine.
 
-    ```console
-    Driver={ODBC Driver 13 for SQL Server};server=localhost;database=WideWorldImporters;trusted_connection=Yes;
-    ```
+```console
+Driver={ODBC Driver 13 for SQL Server};server=localhost;database=WideWorldImporters;trusted_connection=Yes;
+```
 
 Enter the connection string in the **ConnectionString** field on the **Choose a Data Source** or **Choose a Destination** page. After you enter the connection string, the wizard parses the string and displays the individual properties and their values in the list.
 
@@ -149,9 +149,9 @@ To build and test the connection string for your ODBC driver on your own compute
 
     After you assemble the necessary values from the sample file DSN, you have the following connection string.
     
-        ```console
-        DRIVER=ODBC Driver 13 for SQL Server;SERVER=localhost;DATABASE=WideWorldImporters;Trusted_Connection=Yes
-        ```
+    ```console
+    DRIVER=ODBC Driver 13 for SQL Server;SERVER=localhost;DATABASE=WideWorldImporters;Trusted_Connection=Yes
+    ```
 
     You don't typically need all the settings in a DSN created by the ODBC Data Source Administrator to create a connection string that works.  
     -   You always have to specify the ODBC driver.

docs/integration-services/import-export-data/connect-to-an-oracle-data-source-sql-server-import-and-export-wizard.md

@@ -65,9 +65,9 @@ The user id and password to connect.
 ### Connection string format
 Here's the format of a typical connection string.
 
-    ```console
-    Driver={Microsoft ODBC for Oracle};Server=myServerAddress;Uid=myUsername;Pwd=myPassword;
-    ```
+```console
+Driver={Microsoft ODBC for Oracle};Server=myServerAddress;Uid=myUsername;Pwd=myPassword;
+```
 
 ### Enter the connection string
 Enter the connection string in the **ConnectionString** field, or enter the DSN name in the **Dsn** field, on the **Choose a Data Source** or **Choose a Destination** page. After you enter the connection string, the wizard parses the string and displays the individual properties and their values in the list.

docs/integration-services/packages/sql-server-agent-jobs-for-packages.md

@@ -116,23 +116,22 @@ ms.author: chugu
 6.  Select **Integration Services Package** for the job step type.  
 
 7.  In the **Run as** list, select **SQL Server Agent Service Account** or select a proxy account that has the credentials that the job step will use. For information about creating a proxy account, see [Create a SQL Server Agent Proxy](../../ssms/agent/create-a-sql-server-agent-proxy.md).  
-  
+
     Using a proxy account instead of the **SQL Server Agent Service Account** may resolve common issues that can occur when executing a package using the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent. For more information about these issues, see the [!INCLUDE[msCoName](../../includes/msconame-md.md)] Knowledge Base article, [An SSIS package does not run when you call the SSIS package from a SQL Server Agent job step](https://support.microsoft.com/kb/918760). 
 
     - When running job with a Proxy, one has to have the following security items in place for the job to successfuly run.
 
-    Credential Login used by the Proxy, the account running the SQL Server Agent and the account running the SQL Server Service     require the following permissions:
+        Credential Login used by the Proxy, the account running the SQL Server Agent and the account running the SQL Server Service     require the following permissions:
 
         - Local Security Policy Attribue: Replace a Process Level Token
         - Full control over %SYSTEMROOT%\Temp 
-        
-    Failure to put in the security items will result in the job failing and an error message similar to the following: The job failed.  A required privilege is not held by the client.
-     
-  
-    > **NOTE:** If the password changes for the credential that the proxy account uses, you need to update the credential password. Otherwise, the job step will fail.  
-  
-    For information about configuring the SQL Server Agent service account, see [Set the Service Startup Account for SQL Server Agent (SQL Server Configuration Manager)](https://msdn.microsoft.com/library/46ffe818-ebb5-43a0-840b-923f219a2472).  
-  
+
+        Failure to put in the security items will result in the job failing and an error message similar to the following: The job failed. A required privilege is not held by the client.
+
+        > **NOTE:** If the password changes for the credential that the proxy account uses, you need to update the credential password. Otherwise, the job step will fail.  
+
+        For information about configuring the SQL Server Agent service account, see [Set the Service Startup Account for SQL Server Agent (SQL Server Configuration Manager)](https://msdn.microsoft.com/library/46ffe818-ebb5-43a0-840b-923f219a2472).  
+
 8.  In the **Package Source** list box, click the source of the package and then configure the options for the job step.  
 
     **The following table describes the possible package sources.**