update for Acrolinx

Author: cawrites

docs/odbc/microsoft/correlation-names.md

@@ -16,7 +16,7 @@ author: David-Engel
 ms.author: v-daenge
 ---
 # Correlation Names
-Correlation names are fully supported, including within the table list. For example, in the following string, E1 is the correlation name for the table named Emp:  
+Correlation names are fully supported, including within the list. For example, in the following string, E1 is the correlation name for the table named Emp:  
 
 ```  
 SELECT * FROM Emp E1   

docs/odbc/microsoft/create-index-for-paradox.md

@@ -64,7 +64,9 @@ CREATE INDEX PartNum
  ON SO_LINES (PartNum)  
 ```  
 
- Note that when two CREATE INDEX statements are performed, the first statement will always create a primary index with the same name as the table and the second statement will always create a non-unique index with the same name as the column. These indexes will be named this way even if different names are entered in the CREATE INDEX statements and even if the index is labeled UNIQUE in the second CREATE INDEX statement.  
+> [!NOTE]
+> When two CREATE INDEX statements are performed, the first statement will always create a primary index with the same name as the table and the second statement will always create a non-unique index with the same name as the column. 
+> Indexes will be named this way even if different names are entered in the CREATE INDEX statements. Even if the index is labeled UNIQUE in the second CREATE INDEX statement.  
   
-> [!NOTE]  
->  When you use the Paradox driver without implementing the Borland Database Engine, only read and append statements are allowed.
+> [!NOTE]
+> When you use the Paradox driver without implementing the Borland Database Engine, only read and append statements are allowed.

docs/odbc/microsoft/create-index-statement-limitations.md

@@ -24,6 +24,6 @@ The CREATE INDEX statement is not supported for the Microsoft Excel or Text driv
 
  When the dBASE driver is used, response time on large files can be improved by building an .mdx (or .ndx) index on the column (field) specified in the WHERE clauses of a SELECT statement. Existing .mdx indexes will automatically be applied for =, >, \<, >=, =<, and BETWEEN operators in a WHERE clause, and LIKE predicates, as well as in join predicates.  
 
- When the dBASE driver is used, the index created by a CREATE UNIQUE INDEX statement is actually non-unique, and duplicate values can be inserted into the indexed column. Only one record from a set with identical key values can be added to the index.  
+ When the dBASE driver is used, the index created by a CREATE UNIQUE INDEX statement is non-unique, and duplicate values can be inserted into the indexed column. Only one record from a set with identical key values can be added to the index.  
 
  When the Paradox driver is used, a unique index must be defined upon a contiguous subset of the columns in a table, including the first column. A table cannot be updated by the Paradox driver if a unique index is not defined on the table or when the Paradox driver is used without the implementation of the Borland Database Engine.