--- a/doc/interpreter/dynamic.txi
+++ b/doc/interpreter/dynamic.txi
@@ -1211,14 +1211,14 @@
 @cindex mex
 
 Octave includes an interface to allow legacy mex-files to be compiled
-and used with Octave. This interface can also be used to share code
-between Octave and @sc{Matlab} users. However, as mex-files expose the
-@sc{Matlab}'s internal API, and the internal structure of Octave is
+and used with Octave.  This interface can also be used to share code
+between Octave and @sc{matlab} users.  However, as mex-files expose the
+@sc{matlab}'s internal API, and the internal structure of Octave is
 different, a mex-file can never have the same performance in Octave as
-the equivalent oct-file. In particular to support the manner in which
+the equivalent oct-file.  In particular to support the manner in which
 mex-files access the variables passed to mex functions, there are a
 significant number of additional copies of memory when calling or
-returning from a mex function. For this reason, new code should be
+returning from a mex function.  For this reason, new code should be
 written using the oct-file interface discussed above if possible.
 
 @menu
@@ -1236,17 +1236,17 @@
 @subsection Getting Started with Mex-Files
 
 The basic command to build a mex-file is either @code{mkoctfile --mex}
-or @code{mex}. The first can either be used from within Octave or from
-the command line. However, to avoid issues with @sc{Matlab}'s own @code{mex}
+or @code{mex}.  The first can either be used from within Octave or from
+the command line.  However, to avoid issues with @sc{matlab}'s own @code{mex}
 command, the use of the command @code{mex} is limited to within Octave.
 
 @DOCSTRING(mex)
 
 @DOCSTRING(mexext)
 
-One important difference with the use of @code{mex} between @sc{Matlab} and
+One important difference with the use of @code{mex} between @sc{matlab} and
 Octave is that the header file "matrix.h" is implicitly included through
-the inclusion of "mex.h". This is to avoid a conflict with the Octave
+the inclusion of "mex.h".  This is to avoid a conflict with the Octave
 file "Matrix.h" with operating systems and compilers that don't
 distinguish between filenames in upper and lower case
 
@@ -1669,8 +1669,8 @@
 @section Standalone Programs
 
 The libraries Octave itself uses, can be utilized in standalone
-applications. These applications then have access, for example, to the
-array and matrix classes as well as to all the Octave algorithms. The
+applications.  These applications then have access, for example, to the
+array and matrix classes as well as to all the Octave algorithms.  The
 following C++ program, uses class Matrix from @file{liboctave.a} or
 @file{liboctave.so}.