Update README.md

README.md

@@ -2,15 +2,15 @@ A common way of defining the behavior of a process or thread in cases where
 performance is critical is in terms of a collection of n+1 files containing
 code in the C programming language: n "module" files with a ".c" suffix that
 contain the bodies of C functions and procedures, and one additional shared file
-with a ".h" suffix that contains definitions of global variables and types that
-are used by each of the module files. LDI, short for "logical data integration",
-is a collection of tools that make it possible to define this behavior in
-another way. First, the ".h" file is replaced with a relational database schema
-that abstracts all data relevant to the process or threads. This includes all
-local heap-memory data with the low level interface defined by the ".h" file.
-And second, each of the ".c" module files is replaced with a ".sql" version in
-which all data manipulation in the bodies of C functions and procedures is
-re-coded by using a variant of the static embedded SQL protocol.
+with a ".h" suffix that contains definitions of C global variables and types
+that are used by each of the module files. LDI, short for "logical data
+integration", is a collection of tools that make it possible to define this
+behavior in another way. First, the ".h" file is replaced with a relational
+database schema that abstracts all data relevant to the process or threads. This
+includes all local heap-memory data with the low level interface defined by the
+".h" file. And second, each of the ".c" module files is replaced with a ".sql"
+version in which all data manipulation in the bodies of C functions and
+procedures is re-coded by using a variant of the static embedded SQL protocol.
 
 Note that each of the tools comprising the LDI system define the behavior of
 such a process or thread, and are therefore also coded in this manner. Thus, the