Fix dropped word.

diff --git a/Doc/ext.tex b/Doc/ext.tex
index b32702ea628f757a2204f3faa0301c002537f519..d168aa671ddae61142dcf81cb4da5ba15f48fd3e 100644 (file)
--- a/Doc/ext.tex
+++ b/Doc/ext.tex
@@ -879,7 +879,7 @@ program terminates.  This is called a \dfn{memory leak}.  On the other
 hand, if a program calls \code{free()} for a block and then continues
 to use the block, it creates a conflict with re-use of the block
 through another \code{malloc()} call.  This is called \dfn{using freed
-memory} has the same bad consequences as referencing uninitialized
+memory}.  It has the same bad consequences as referencing uninitialized
 data --- core dumps, wrong results, mysterious crashes.
 
 Common causes of memory leaks are unusual paths through the code.  For

diff --git a/Doc/ext/ext.tex b/Doc/ext/ext.tex
index b32702ea628f757a2204f3faa0301c002537f519..d168aa671ddae61142dcf81cb4da5ba15f48fd3e 100644 (file)
--- a/Doc/ext/ext.tex
+++ b/Doc/ext/ext.tex
@@ -879,7 +879,7 @@ program terminates.  This is called a \dfn{memory leak}.  On the other
 hand, if a program calls \code{free()} for a block and then continues
 to use the block, it creates a conflict with re-use of the block
 through another \code{malloc()} call.  This is called \dfn{using freed
-memory} has the same bad consequences as referencing uninitialized
+memory}.  It has the same bad consequences as referencing uninitialized
 data --- core dumps, wrong results, mysterious crashes.
 
 Common causes of memory leaks are unusual paths through the code.  For