diff options
Diffstat (limited to 'doc/articles/image_package.html')
| -rw-r--r-- | doc/articles/image_package.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/articles/image_package.html b/doc/articles/image_package.html index ebe92a1ca..39a93ccda 100644 --- a/doc/articles/image_package.html +++ b/doc/articles/image_package.html @@ -130,7 +130,7 @@ much easier to type. A <code>Rectangle</code> is inclusive at the top-left and exclusive at the bottom-right. For a <code>Point p</code> and a <code>Rectangle r</code>, <code>p.In(r)</code> if and only if -<code>r.Min.X <= p.X && p.X < r.Max.X</code>, and similarly for <code>Y</code>. This is analagous to how +<code>r.Min.X <= p.X && p.X < r.Max.X</code>, and similarly for <code>Y</code>. This is analogous to how a slice <code>s[i0:i1]</code> is inclusive at the low end and exclusive at the high end. (Unlike arrays and slices, a <code>Rectangle</code> often has a non-zero origin.) @@ -236,7 +236,7 @@ more complicated, to access these struct type's <code>Pix</code> field directly. The slice-based <code>Image</code> implementations also provide a <code>SubImage</code> method, which returns an <code>Image</code> backed by the same array. Modifying the pixels of a sub-image will affect the pixels of the -original image, analagous to how modifying the contents of a sub-slice +original image, analogous to how modifying the contents of a sub-slice <code>s[i0:i1]</code> will affect the contents of the original slice <code>s</code>. </p> |