Merge pull request #19936 from David-Engel/minor

Minor edits

Author: PRMerger8

docs/connect/jdbc/azure-key-vault-sample-version-9.2.md

@@ -3,8 +3,6 @@ title: Azure Key Vault sample
 description: This JDBC code example demonstrates how to use Azure Key Vault as your key store provider when using Always Encrypted.
 ms.custom: ""
 ms.date: 07/30/2021
-
-
 ms.prod: sql
 ms.prod_service: connectivity
 ms.reviewer: v-daenge
@@ -246,4 +244,4 @@ public class AKV {
 
 [Azure Key vault sample version 7.0](azure-key-vault-sample-version-7.0.md)  
 [Azure Key vault sample version 6.2.2](azure-key-vault-sample-version-6.2.2.md)  
-[Azure Key vault sample version 6.0.0](azure-key-vault-sample-version-6.0.0.md) 
+[Azure Key vault sample version 6.0.0](azure-key-vault-sample-version-6.0.0.md)  

docs/connect/jdbc/setting-the-connection-properties.md

@@ -22,6 +22,7 @@ The connection string properties can be specified in various ways:
 - As name=value properties in the connection URL when you connect by using the DriverManager class.
 - As name=value properties in the *Properties* parameter of the Connect method in the DriverManager class.
 - As values in the appropriate setter method of the data source of the driver. For example:
+
     ```java
     datasource.setServerName(value)
     datasource.setDatabaseName(value)
@@ -30,6 +31,7 @@ The connection string properties can be specified in various ways:
 ## Remarks
 
 Property names are case-insensitive, and duplicate property names are resolved in the following order:
+
 1. API arguments (such as user and password)
 2. Property collection
 3. Last instance in the connection string