Minor corrections including punctuation and missing words

docs/advanced-linux-installation/index.html

@@ -113,11 +113,11 @@ <h2><a class="anchor" id="configure"></a>Configure</h2>
 <dt class="col-md-4">CXXFLAGS</dt>
   <dd class="col-md-8">Compiler flags (e.g. <code>-g -O2</code>) to compile C++ code.</dd>
 <dt class="col-md-4">CPPFLAGS</dt>
-  <dd class="col-md-8">Include paths (.e.g. <code>-I/usr/local</code>) to look for header files.</dd>
+  <dd class="col-md-8">Include paths (e.g. <code>-I/usr/local</code>) to look for header files.</dd>
 <dt class="col-md-4">LDFLAGS</dt>
-  <dd class="col-md-8">Library paths (.e.g. <code>-L/usr/local</code>) to look for libraries systems that support the notion of a library run-path may require an additional argument in order to find shared libraries at run time. For example, the Solaris linker requires an argument of the form <var>-R/path</var>.  Some Linux systems will work with <code>-rpath /usr/local/lib</code>, while some other Linux systems who's gcc does not pass <code>-rpath</code> to the linker, require an argument of the form <code>-Wl,-rpath,/usr/local/lib</code>.</dd>
+  <dd class="col-md-8">Library paths (e.g. <code>-L/usr/local</code>) to look for libraries systems that support the notion of a library run-path may require an additional argument in order to find shared libraries at run time. For example, the Solaris linker requires an argument of the form <var>-R/path</var>.  Some Linux systems will work with <code>-rpath /usr/local/lib</code>, while some other Linux systems who's gcc does not pass <code>-rpath</code> to the linker, require an argument of the form <code>-Wl,-rpath,/usr/local/lib</code>.</dd>
 <dt class="col-md-4">LIBS</dt>
-  <dd class="col-md-8">Extra libraries (.e.g. <code>-l/usr/local/lib</code>) required to link.</dd>
+  <dd class="col-md-8">Extra libraries (e.g. <code>-l/usr/local/lib</code>) required to link.</dd>
 </dl>
 
 <p>Here is an example of setting configure variables from the command line:</p>
@@ -158,7 +158,7 @@ <h2><a class="anchor" id="configure"></a>Configure</h2>
     <td>--disable-installed</td>
     <td>disable building an installed ImageMagick (default enabled).
   <br/><br />
-  By default the ImageMagick build is configured to formally install into a directory tree.  This the most secure and reliable way to install ImageMagick.  Use this option to configure ImageMagick so that it doesn't use hard-coded paths and locates support files by computing an offset path from the executable (or from the location specified by the MAGICK_HOME environment variable. The uninstalled configuration is ideal for binary distributions which are expected to extract and run in any location.</td>
+  By default the ImageMagick build is configured to formally install into a directory tree.  This is the most secure and reliable way to install ImageMagick.  Use this option to configure ImageMagick so that it doesn't use hard-coded paths and locates support files by computing an offset path from the executable (or from the location specified by the MAGICK_HOME environment variable. The uninstalled configuration is ideal for binary distributions which are expected to extract and run in any location.</td>
   </tr>
   <tr>
     <td>--enable-ccmalloc</td>
@@ -253,7 +253,7 @@ <h2><a class="anchor" id="configure"></a>Configure</h2>
     <td>--with-frozenpaths</td>
     <td>enable frozen delegate paths.
   <br /><br />
-  Normally, external program names are substituted into the <code>delegates.xml</code> configuration file without full paths. Specify this option to enable saving full paths to programs using locations determined by configure. This useful for environments where programs are stored under multiple paths, and users may use different PATH settings than the person who builds ImageMagick.</td>
+  Normally, external program names are substituted into the <code>delegates.xml</code> configuration file without full paths. Specify this option to enable saving full paths to programs using locations determined by configure. This is useful for environments where programs are stored under multiple paths, and users may use different PATH settings than the person who builds ImageMagick.</td>
   </tr>
   <tr>
     <td>--without-magick-plus-plus</td>
@@ -390,7 +390,7 @@ <h2><a class="anchor" id="build"></a>Build</h2>
 <dt class="col-md-4">make clean</dt>
   <dd class="col-md-8"> Remove everything in the build directory created by <code>make</code>.</dd>
 <dt class="col-md-4">make distclean</dt>
-  <dd class="col-md-8">remove everything in the build directory created by <code>configure</code> and <code>make</code>.  This useful if you want to start over from scratch.</dd>
+  <dd class="col-md-8">remove everything in the build directory created by <code>configure</code> and <code>make</code>.  This is useful if you want to start over from scratch.</dd>
 <dt class="col-md-4">make uninstall</dt>
   <dd class="col-md-8">Remove all files from the system which are (or would be) installed by <code>sudo make install</code> using the current configuration.  Note that this target is imperfect for PerlMagick since Perl no longer supports an <var>uninstall</var> target.</dd>
 </dl>

docs/architecture/index.html

@@ -12,12 +12,12 @@ <h2><a class="anchor" id="overview"></a>Architecture Overview</h2>
 <p>An image typically consists of a rectangular region of pixels and metadata.  To convert, edit, or compose an image in an efficient manner, we need convenient access to any pixel anywhere within the region (and sometimes outside the region).  And in the case of an image sequence, we need access to any pixel of any region of any image in the sequence.  However, there are hundreds of image formats such JPEG, TIFF, PNG, GIF, etc., that makes it difficult to access pixels on demand.  Within these formats we find differences in:</p>
 
 <ul>
-  <li>colorspace (e.g sRGB, linear RGB, linear GRAY, CMYK, YUV, Lab, etc.)</li>
-  <li>bit depth (.e.g 1, 4, 8, 12, 16, etc.)</li>
+  <li>colorspace (e.g. sRGB, linear RGB, linear GRAY, CMYK, YUV, Lab, etc.)</li>
+  <li>bit depth (e.g. 1, 4, 8, 12, 16, etc.)</li>
   <li>storage format (e.g. unsigned, signed, float, double, etc.)</li>
   <li>compression (e.g. uncompressed, RLE, Zip, BZip, etc.)</li>
   <li>orientation (i.e. top-to-bottom, right-to-left, etc.),</li>
-  <li>layout (.e.g. raw, interspersed with opcodes, etc.)</li>
+  <li>layout (e.g. raw, interspersed with opcodes, etc.)</li>
 </ul>
 
 <p>In addition, some image pixels may require attenuation, some formats permit more than one frame, and some formats contain vector graphics that must first be rasterized (converted from vector to pixels).</p>

docs/command-line-options/index.html

@@ -1377,7 +1377,7 @@ <h2><a class="anchor" id="clahe"></a>-clahe <var>width</var>x<var>height</var>&#
   <h2><a class="anchor" id="clamp"></a>-clamp</h2>
 </div>
 
-<p class="lead">Set each pixel whose value is below zero to zero and any the pixel whose value is above the quantum range to the quantum range (e.g. 65535) otherwise the pixel value remains unchanged.</p>
+<p class="lead">Set each pixel whose value is below zero to zero and any pixel whose value is above the quantum range to the quantum range (e.g. 65535) otherwise the pixel value remains unchanged.</p>
 
 <div style="mx-auto my-3 text-center">
   <h2><a class="anchor" id="clip"></a>-clip</h2>
@@ -2195,7 +2195,7 @@ <h2><a class="anchor" id="define"></a>-define <var>key</var>{<var>=value</var>}<
 as "Artifacts". </p>
 
 <p>If <var>value</var> is missing for a definition, an empty-valued
-definition of a flag is created with that name. This used to control on/off
+definition of a flag is created with that name. This is used to control on/off
 options.  Use <a href="#define">+define key</a> to remove definitions
 previously created.  Use <a href="#define">+define "*"</a> to remove all
 existing definitions.</p>
@@ -5178,7 +5178,7 @@ <h2><a class="anchor" id="limit"></a>-limit <var>type value</var></h2>
 
 <p>The value for <code>file</code> is in number of files. The other limits are
 in bytes. Define arguments for the memory, map, area, and disk resource limits
-with SI prefixes (.e.g 100MB).</p>
+with SI prefixes (e.g. 100MB).</p>
 
 <p>By default the limits are 768 files, 3GB of image area, 1.5GiB memory, 3GiB
 memory map, and 18.45EB of disk.  These limits are adjusted relative to the
@@ -6320,7 +6320,7 @@ <h2><a class="anchor" id="read-mask"></a>-read-mask <var>filename</var></h2>
 
 <p class="lead">Prevent updates to image pixels specified by the mask.</p>
 
-<p>This the same as using a mask used for composite masking operations, with
+<p>This is the same as using a mask used for composite masking operations, with
 grayscale values causing blended updates of the image the mask is attached to.
 </p>
 
@@ -6408,7 +6408,7 @@ <h2><a class="anchor" id="render"></a>-render</h2>
 <p class="lead">Render vector operations.</p>
 
 <p>Use <a href="#render">+render</a> to turn off rendering vector operations.
-This useful when saving the result to vector formats such as MVG or SVG.</p>
+This is useful when saving the result to vector formats such as MVG or SVG.</p>
 
 <div style="mx-auto my-3 text-center">
 <h2><a class="anchor" id="repage"></a>-repage <var>geometry</var></h2>
@@ -6423,7 +6423,7 @@ <h2><a class="anchor" id="repage"></a>-repage <var>geometry</var></h2>
 <p>See <a href="/command-line-processing/#geometry">Image Geometry</a> for complete details about the <em class="arg">geometry</em> argument.</p>
 
 <p>If a <code>!</code> flag is given the offset given is added to the existing
-offset to move the image relative to its previous position. This useful for
+offset to move the image relative to its previous position. This is useful for
 animation sequences. </p>
 
 <p>A given a canvas size of zero such as '<code>0x0</code>' forces it to

docs/conjure/index.html

@@ -286,7 +286,7 @@ <h2><a class="anchor" id="msl"></a>Magick Scripting Language</h2>
   <tr>
     <td><strike>clamp</strike></td>
     <td>channel="Red, RGB, All, etc."</td>
-    <td>set each pixel whose value is below zero to zero and any the pixel whose value is above the quantum range to the quantum range (e.g. 65535) otherwise the pixel value remains unchanged.</td>
+    <td>set each pixel whose value is below zero to zero and any pixel whose value is above the quantum range to the quantum range (e.g. 65535) otherwise the pixel value remains unchanged.</td>
 
   </tr>
 

docs/convert/index.html

@@ -214,7 +214,7 @@ <h2><a class="anchor" id="options"></a>Option Summary</h2>
 
   <tr>
     <td><a href="/command-line-options/#clamp">-clamp</a></td>
-    <td>set each pixel whose value is below zero to zero and any the pixel whose value is above the quantum range to the quantum range (e.g. 65535) otherwise the pixel value remains unchanged.</td>
+    <td>set each pixel whose value is below zero to zero and any pixel whose value is above the quantum range to the quantum range (e.g. 65535) otherwise the pixel value remains unchanged.</td>
   </tr>
 
   <tr>

docs/defines/index.html

@@ -12,7 +12,7 @@
 beyond what is provided by normal means.  Defined settings are listed in <a href="/command-line-options/#verbose">-verbose</a> information ("<code>info:</code>" output format) as "Artifacts". </p>
 
 <p>If <var>value</var> is missing for a definition, an empty-valued
-definition of a flag is created with that name. This used to control on/off
+definition of a flag is created with that name. This is used to control on/off
 options.  Use <a href="/command-line-options/#define">-define keys</a> to remove definitions
 previously created.  Use <a href="/command-line-options/#define">+define "*"</a> to remove all existing definitions.</p>
 

docs/download/index.html

@@ -35,7 +35,7 @@ <h2><a class="anchor" id="linux"></a>Linux Binary Release</h2>
       {% include download-link.html variant="gcc-x86_64.AppImage" %}<br/>
       {% include download-link.html variant="clang-x86_64.AppImage" %}
     </td>
-    <td>Complete portable application on Linux, no installation required.  Just download and run.  This <a href="https://appimage.org/">AppImage</a> has an open security policy.  ImageMagick recommended practices <b>strongly</b> encourage you to configure a <a href="/security-policy/">security policy</a> that suits your local environment. Simply add a custom security policy in your local path, .e.g., <code>~/.config/ImageMagick/policy.xml</code> and verify with this command: <code>./magick -list policy</code>.</td>
+    <td>Complete portable application on Linux, no installation required.  Just download and run.  This <a href="https://appimage.org/">AppImage</a> has an open security policy.  ImageMagick recommended practices <b>strongly</b> encourage you to configure a <a href="/security-policy/">security policy</a> that suits your local environment. Simply add a custom security policy in your local path, e.g., <code>~/.config/ImageMagick/policy.xml</code> and verify with this command: <code>./magick -list policy</code>.</td>
   </tr>
 
   </tbody>

docs/exception/index.html

@@ -3,7 +3,7 @@
 ---
 <div>
 
-<p class="lead">ImageMagick returns a status of 0 whenever a command or algorithm successfully complete without complaint.  A warning code generally is typically just a notice that something unusual occurred but the command or algorithm still completed and most likely the results are still usable.  An error means the command or algorithm could not complete as expected and any results are unreliable.  A fatal error means the command or algorithm could not complete and the process exits prematurely and no results are returned.</p>
+<p class="lead">ImageMagick returns a status of 0 whenever a command or algorithm successfully completes without complaint.  A warning code generally is typically just a notice that something unusual occurred but the command or algorithm still completed and most likely the results are still usable.  An error means the command or algorithm could not complete as expected and any results are unreliable.  A fatal error means the command or algorithm could not complete and the process exits prematurely and no results are returned.</p>
 
 <div style="max-height:75svh; overflow-y:auto; overflow-x:hidden;">
 <table class="table table-sm table-hover table-striped caption-top">

docs/fx/index.html

@@ -111,7 +111,7 @@ <h4>The FX Expression Language</h4>
 
 <dl class="row">
   <dt class="col-md-4"> numbers:</dt>
-  	<dd class="col-md-8"> integer, floating point, scientific notation (+/- required, e.g. 3.81469e-06), International System number postfixes (.e.g KB, Mib, GB, etc.)</dd>
+  	<dd class="col-md-8"> integer, floating point, scientific notation (+/- required, e.g. 3.81469e-06), International System number postfixes (e.g. KB, Mib, GB, etc.)</dd>
   <dt class="col-md-4"> constants: </dt>
     <dd class="col-md-8"> E (Euler's number), Epsilon, Opaque, Phi (golden ratio), Pi, QuantumRange, QuantumScale, Transparent</dd>
   <dt class="col-md-4"> FX operators (in order of precedence): </dt>

docs/magick++/Exception.html

@@ -87,7 +87,7 @@ <h1 align="center">Magick::Exception Classes</h1>
 programs may use just one try/catch block.</p>
 <p>The <i>Exception</i> class is derived from the C++ standard
 exception class. This means that it contains a C++ string containing
-additional information about the error (e.g to display to the user).
+additional information about the error (e.g. to display to the user).
 Obtain access to this string via the what() method.&#160; For
 example: 
 </p>

docs/magick++/FormatCharacters.html

@@ -50,7 +50,7 @@ <h1 align="center">Special Format Characters</h1>
 <td width="51%">
 <p align="center">%m</p></td>
 <td width="49%">
-<p>magick (e.g GIF)</p></td></tr>
+<p>magick (e.g. GIF)</p></td></tr>
 <tr>
 <td width="51%">
 <p align="center">%p</p></td>

docs/magick-script/index.html

@@ -175,7 +175,7 @@ <h2><a class="anchor" id="options"></a>Option Summary</h2>
 
   <tr>
     <td><a href="/command-line-options/#clamp">-clamp</a></td>
-    <td>set each pixel whose value is below zero to zero and any the pixel whose value is above the quantum range to the quantum range (e.g. 65535) otherwise the pixel value remains unchanged.</td>
+    <td>set each pixel whose value is below zero to zero and any pixel whose value is above the quantum range to the quantum range (e.g. 65535) otherwise the pixel value remains unchanged.</td>
   </tr>
 
   <tr>

docs/magick/index.html

@@ -215,7 +215,7 @@ <h2><a class="anchor" id="options"></a>Option Summary</h2>
 
   <tr>
     <td><a href="/command-line-options/#clamp">-clamp</a></td>
-    <td>set each pixel whose value is below zero to zero and any the pixel whose value is above the quantum range to the quantum range (e.g. 65535) otherwise the pixel value remains unchanged.</td>
+    <td>set each pixel whose value is below zero to zero and any pixel whose value is above the quantum range to the quantum range (e.g. 65535) otherwise the pixel value remains unchanged.</td>
   </tr>
 
   <tr>

docs/mogrify/index.html

@@ -220,7 +220,7 @@ <h2><a class="anchor" id="options"></a>Option Summary</h2>
 
   <tr>
     <td><a href="/command-line-options/#clamp">-clamp</a></td>
-    <td>set each pixel whose value is below zero to zero and any the pixel whose value is above the quantum range to the quantum range (e.g. 65535) otherwise the pixel value remains unchanged.</td>
+    <td>set each pixel whose value is below zero to zero and any pixel whose value is above the quantum range to the quantum range (e.g. 65535) otherwise the pixel value remains unchanged.</td>
   </tr>
 
   <tr>

docs/perl-magick/index.html

@@ -454,7 +454,7 @@ <h2><a class="anchor" id="manipulate"></a>Manipulate an Image</h2>
   <tr>
     <td>Clamp</td>
     <td>channel=&gt;{Red, RGB, All, etc.}</td>
-    <td>set each pixel whose value is below zero to zero and any the pixel whose value is above the quantum range to the quantum range (e.g. 65535) otherwise the pixel value remains unchanged.</td>
+    <td>set each pixel whose value is below zero to zero and any pixel whose value is above the quantum range to the quantum range (e.g. 65535) otherwise the pixel value remains unchanged.</td>
   </tr>
 
   <tr>