acro

Author: VanMSFT

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

@@ -14,7 +14,7 @@ apitype: "Assembly"
 ---
 # prepareStatement Method (java.lang.String, int)
 
-Creates a [SQLServerPreparedStatement](./sqlserverpreparedstatement-class.md) object that has the capability to retrieve auto-generated keys.
+Creates a [SQLServerPreparedStatement](./sqlserverpreparedstatement-class.md) object that has the capability to retrieve autogenerated keys.
 
 ## Syntax
 
@@ -24,13 +24,13 @@ public java.sql.PreparedStatement prepareStatement(java.lang.String sql,
 ```
 
 #### Parameters
-*sql*
+`sql`
 
 A **String** containing a SQL statement.
 
-*autoGeneratedKeys*
+`autoGeneratedKeys`
 
-An **int** flag indicating whether auto-generated keys should be returned. One of `Statement.RETURN_GENERATED_KEYS` or `Statement.NO_GENERATED_KEYS`.
+An **int** flag indicating whether autogenerated keys should be returned. One of `Statement.RETURN_GENERATED_KEYS` or `Statement.NO_GENERATED_KEYS`.
 
 ## Return Value
 A PreparedStatement object.

docs/odbc/reference/develop-app/batches-of-sql-statements.md

@@ -14,10 +14,11 @@ helpviewer_keywords:
   - "batches [ODBC], about batches"
 ---
 # Batches of SQL Statements
-A batch of SQL statements is a group of two or more SQL statements or a single SQL statement that has the same effect as a group of two or more SQL statements. In some implementations, the entire batch statement is executed before any results are available. This is often more efficient than submitting statements separately, because network traffic can often be reduced and the data source can sometimes optimize execution of a batch of SQL statements. In other implementations, calling **SQLMoreResults** triggers the execution of the next statement in the batch. ODBC supports the following types of batches:  
-  
--   **Explicit Batches** An *explicit batch* is two or more SQL statements separated by semicolons (;). For example, the following batch of SQL statements opens a new sales order. This requires inserting rows into both the Orders and Lines tables. Note that there is no semicolon after the last statement.  
-  
+
+A batch of SQL statements is a group of two or more SQL statements or a single SQL statement that has the same effect as a group of two or more SQL statements. In some implementations, the entire batch statement is executed before any results are available. This is often more efficient than submitting statements separately, because network traffic can often be reduced and the data source can sometimes optimize execution of a batch of SQL statements. In other implementations, calling **SQLMoreResults** triggers the execution of the next statement in the batch. ODBC supports the following types of batches:
+
+-   **Explicit Batches** An *explicit batch* is two or more SQL statements separated by semicolons (;). For example, the following batch of SQL statements opens a new sales order. This requires inserting rows into both the Orders and Lines tables. Note that there's no semicolon after the last statement.
+
     ```  
     INSERT INTO Orders (OrderID, CustID, OpenDate, SalesPerson, Status)  
        VALUES (2002, 1001, {fn CURDATE()}, 'Garcia', 'OPEN');  
@@ -29,34 +30,32 @@ A batch of SQL statements is a group of two or more SQL statements or a single S
        VALUES (2002, 3, 566, 17);  
     INSERT INTO Lines (OrderID, Line, PartID, Quantity)  
        VALUES (2002, 4, 412, 500)  
-    ```  
-  
--   **Procedures** If a procedure contains more than one SQL statement, it is considered to be a batch of SQL statements. For example, the following SQL Server-specific statement creates a procedure that returns a result set containing information about a customer and a result set listing all the open sales orders for that customer:  
-  
+    ```
+
+-   **Procedures** If a procedure contains more than one SQL statement, it's considered to be a batch of SQL statements. For example, the following SQL Server-specific statement creates a procedure that returns a result set containing information about a customer and a result set listing all the open sales orders for that customer:
+
     ```  
     CREATE PROCEDURE GetCustInfo (@CustomerID INT) AS  
        SELECT * FROM Customers WHERE CustID = @CustomerID  
        SELECT OrderID FROM Orders  
           WHERE CustID = @CustomerID AND Status = 'OPEN'  
-    ```  
-  
-     The **CREATE PROCEDURE** statement itself is not a batch of SQL statements. However, the procedure it creates is a batch of SQL statements. No semicolons separate the two **SELECT** statements because the **CREATE PROCEDURE** statement is specific to SQL Server, and SQL Server does not require semicolons to separate multiple statements in a **CREATE PROCEDURE** statement.  
-  
--   **Arrays of Parameters** - Arrays of parameters can be used with a parameterized SQL statement as an effective way to perform bulk operations. For example, arrays of parameters can be used with the following **INSERT** statement to insert multiple rows into the Lines table while executing only a single SQL statement:  
-  
+    ```
+
+    The **CREATE PROCEDURE** statement itself isn't a batch of SQL statements. However, the procedure it creates is a batch of SQL statements. No semicolons separate the two **SELECT** statements because the **CREATE PROCEDURE** statement is specific to SQL Server, and SQL Server doesn't require semicolons to separate multiple statements in a **CREATE PROCEDURE** statement.
+
+-   **Arrays of Parameters** - Arrays of parameters can be used with a parameterized SQL statement as an effective way to perform bulk operations. For example, arrays of parameters can be used with the following **INSERT** statement to insert multiple rows into the Lines table while executing only a single SQL statement:
+
     ```  
     INSERT INTO Lines (OrderID, Line, PartID, Quantity)  
        VALUES (?, ?, ?, ?)  
-    ```  
-  
-     If a data source doesn't support arrays of parameters, the driver can emulate them by executing the SQL statement once for each set of parameters. For more information, see [Statement Parameters](../../../odbc/reference/develop-app/statement-parameters.md) and [Arrays of Parameter Values](../../../odbc/reference/develop-app/arrays-of-parameter-values.md), later in this article.  
-  
- The different types of batches can't be mixed in an interoperable manner. That is, how an application determines the result of executing an explicit batch that includes procedure calls, an explicit batch that uses arrays of parameters, and a procedure call that uses arrays of parameters is driver-specific.  
-  
+    ```
+
+    If a data source doesn't support arrays of parameters, the driver can emulate them by executing the SQL statement once for each set of parameters. For more information, see [Statement Parameters](../../../odbc/reference/develop-app/statement-parameters.md) and [Arrays of Parameter Values](../../../odbc/reference/develop-app/arrays-of-parameter-values.md), later in this article.
+
+The different types of batches can't be mixed in an interoperable manner. That is, how an application determines the result of executing an explicit batch that includes procedure calls, an explicit batch that uses arrays of parameters, and a procedure call that uses arrays of parameters is driver-specific.
+
 ## Related content
-  
--   [Result-Generating and Result-Free Statements](../../../odbc/reference/develop-app/result-generating-and-result-free-statements.md)  
-  
--   [Executing Batches](../../../odbc/reference/develop-app/executing-batches.md)  
-  
--   [Errors and Batches](../../../odbc/reference/develop-app/errors-and-batches.md)
+
+- [Result-Generating and Result-Free Statements](../../../odbc/reference/develop-app/result-generating-and-result-free-statements.md)
+- [Executing Batches](../../../odbc/reference/develop-app/executing-batches.md)
+- [Errors and Batches](../../../odbc/reference/develop-app/errors-and-batches.md)

docs/t-sql/statements/create-symmetric-key-transact-sql.md

@@ -91,7 +91,7 @@ Specifies a passphrase from which to derive the key.
 
 #### IDENTITY_VALUE = '*identity_phrase*'
 
-Specifies an identity phrase from which to generate a GUID for tagging data that is encrypted with a temporary key.
+Specifies an identity phrase from which to generate a GUID for tagging data that's encrypted with a temporary key.
 
 #### PROVIDER_KEY_NAME = '*key_name_in_provider*'
 
@@ -118,15 +118,15 @@ Specifies the name of the certificate that is used to encrypt the symmetric key.
 
 #### '*password*'
 
-Specifies a password from which to derive a TRIPLE_DES key with which to secure the symmetric key. `password` must meet the Windows password policy requirements of the computer that is running the instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. Always use strong passwords.
+Specifies a password from which to derive a TRIPLE_DES key with which to secure the symmetric key. `password` must meet the Windows password policy requirements of the computer that's running the instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. Always use strong passwords.
 
 #### *symmetric_key_name*
 
-Specifies a symmetric key, used to encrypt the key that is being created. The specified key must already exist in the database, and the key must be open.
+Specifies a symmetric key, used to encrypt the key that's being created. The specified key must already exist in the database, and the key must be open.
 
 #### *asym_key_name*
 
-Specifies an asymmetric key, used to encrypt the key that is being created. This asymmetric key must already exist in the database.
+Specifies an asymmetric key, used to encrypt the key that's being created. This asymmetric key must already exist in the database.
 
 #### \<algorithm>
 
@@ -156,7 +156,7 @@ The optional password can be used to encrypt the symmetric key before distributi
 
 Temporary keys are owned by the user that creates them. Temporary keys are only valid for the current session.
 
-`IDENTITY_VALUE` generates a GUID with which to tag data that is encrypted with the new symmetric key. This tagging can be used to match keys to encrypted data. The GUID generated by a specific phrase is always the same. After a phrase has been used to generate a GUID, the phrase can't be reused as long as there's at least one symmetric key in this database that is actively using the phrase. `IDENTITY_VALUE` is an optional clause; however, we recommend using it when you're storing data encrypted with a temporary key.
+`IDENTITY_VALUE` generates a GUID with which to tag data that's encrypted with the new symmetric key. This tagging can be used to match keys to encrypted data. The GUID generated by a specific phrase is always the same. After a phrase has been used to generate a GUID, the phrase can't be reused as long as there's at least one symmetric key in this database that is actively using the phrase. `IDENTITY_VALUE` is an optional clause; however, we recommend using it when you're storing data encrypted with a temporary key.
 
 There's no default encryption algorithm.