ilist.html in rmagick-2.3.0

- old
+ new

@@ -4,11 +4,11 @@
 <html xmlns="http://www.w3.org/1999/xhtml">
 <head>
   <meta name="generator" content=
   "HTML Tidy for Linux/x86 (vers 1 September 2005), see www.w3.org" />
 
-  <title>RMagick 2.2.2: class ImageList</title>
+  <title>RMagick 2.3.0: class ImageList</title>
   <meta http-equiv="Content-Type" content=
   "text/html; charset=us-ascii" />
   <meta name="GENERATOR" content="Quanta Plus" />
   <meta name="Copyright" content=
   "Copyright (C) 2005 by Timothy P. Hunter" />
@@ -18,11 +18,11 @@
 <script type="text/javascript" src="scripts/doc.js">
 </script>
 </head>
 
 <body>
-  <h6 id="header">RMagick 2.2.2 User's Guide and Reference</h6>
+  <h6 id="header">RMagick 2.3.0 User's Guide and Reference</h6>
 
   <div class="nav">
     &laquo;&nbsp;<a href="magick.html">Prev</a> | <a href=
     "index.html">Contents</a> | <a href=
     "imageattrs.html">Next</a>&nbsp;&raquo;
@@ -372,11 +372,11 @@
 
     <p>Adding anything other than a image to an imagelist has
     undefined results. Most of the time RMagick will raise an
     ArgumentError exception. For example, if you call
     <code>collect!</code> on an imagelist you should make sure that
-    the members of theimagelist remain images. If you need to
+    the members of the imagelist remain images. If you need to
     replace images in an imagelist with non-image objects, convert
     the imagelist to an array with the <code>to_a</code> method,
     then modify the array.</p>
 
     <p>The <code>assoc</code>, <code>flatten</code>,
@@ -561,11 +561,11 @@
 
   <div class="desc">
     <h4>Description</h4>
 
     <p>Same as <a href="#dup">dup</a>, but the frozen state of the
-    original is propogated to the copy.</p>
+    original is propagated to the copy.</p>
 
     <h4>Returns</h4>
 
     <p>A new imagelist</p>
 
@@ -758,11 +758,11 @@
     <p>This method constructs a new imagelist containing images
     that include only the changed pixels between each image and its
     successor. The resulting imagelist usually produces a much
     smaller file.</p>
 
-    <p>The <code>desconstruct</code> method starts by copying the
+    <p>The <code>deconstruct</code> method starts by copying the
     first image in the list to the output imagelist. Then, for each
     pair of images, <code>deconstruct</code> computes the smallest
     rectangle that encompasses all the changes between the first
     and second image and stores just the changed rectangle of the
     second image, along with the offset of the rectangle relative
@@ -1517,11 +1517,11 @@
 
       <dd><span class="imquote">Create a canvas the size of the
       first images virtual canvas using the current background
       color, and compose each image in turn onto that canvas.
       Images falling outside that canvas will be clipped. Final
-      image will have a zero virtual canvas offset. This is usally
+      image will have a zero virtual canvas offset. This is usually
       used as one of the final 'image layering' operations
       overlaying all the prepared image layers into a final image.
       For a single image this method can also be used to fillout a
       virtual canvas with real pixels, or to underlay a opaque
       color to remove transparency from an image.</span> This
@@ -1534,11 +1534,11 @@
       expanding the initial canvas size of the first image so as to
       hold all the image layers. However as a virtual canvas is
       'locked' to the origin, by definition, image layers with a
       negative offsets will still be clipped by the top and left
       edges. This method is commonly used to layout individual
-      image using various offset but without knowning the final
+      image using various offset but without knowing the final
       canvas size. The resulting image will, like FlattenLayer not
       have any virtual offset, so can be saved to any image file
       format.</span> This method corresponds to <a href=
       "#mosaic">mosaic</a>, above.</dd>
 
@@ -1590,11 +1590,11 @@
 
       <dt>RemoveDupsLayer</dt>
 
       <dd class="imquote">Remove (and merge time delays) of
       duplicate consecutive images, so as to simplify layer
-      overlays of coalesced animations. Usally this is a result of
+      overlays of coalesced animations. Usually this is a result of
       using a constant time delay across the whole animation, or
       after a larger animation was split into smaller
       sub-animations. The duplicate frames could also have been
       used as part of some frame optimization methods.</dd>
 
@@ -1603,10 +1603,10 @@
       <dd class="imquote">Remove any image with a zero time delay,
       unless ALL the images have a zero time delay (and is not a
       proper timed animation, a warning is then issued). In a GIF
       animation, such images are usually frames which provide
       partial intermediary updates between the frames that are
-      actually displayed to users. These frames are usally added
+      actually displayed to users. These frames are usually added
       for improved frame optimization in GIF animations.</dd>
     </dl>
 
     <p>Some of these values are not supported by older versions of
     ImageMagick. To see what values are available, enter the