docs: Add introductory paragraph before first H2 heading

Moved intro content between H1 and H2 to resolve blocking validation issue. Restructured to have brief intro paragraph after H1, then 'Types of batches' H2 section with detailed explanation.

Author: VanMSFT

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

@@ -15,9 +15,11 @@ helpviewer_keywords:
 ---
 # Batches of SQL Statements
 
-## Overview
+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. Batching statements can improve performance by reducing network traffic and allowing the data source to optimize execution.
 
-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:
+## Types of batches
+
+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.