summary refs log tree commit diff
path: root/pamenlarge.html
diff options
context:
space:
mode:
authorgiraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8>2019-02-20 03:49:29 +0000
committergiraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8>2019-02-20 03:49:29 +0000
commitcc55fa0f8dcd81a5e2b99c1d41caad02460825a6 (patch)
tree2475cd853915ed6bb867c9339284bd6067ab9d94 /pamenlarge.html
parent598441aa09a2e3b2fa45abb8a758ff76c68f9c9e (diff)
downloadnetpbm-mirror-cc55fa0f8dcd81a5e2b99c1d41caad02460825a6.tar.gz
netpbm-mirror-cc55fa0f8dcd81a5e2b99c1d41caad02460825a6.tar.xz
netpbm-mirror-cc55fa0f8dcd81a5e2b99c1d41caad02460825a6.zip
miscellaneous update
git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@3550 9d0c8265-081b-0410-96cb-a4ca84ce46f8
Diffstat (limited to 'pamenlarge.html')
-rw-r--r--pamenlarge.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/pamenlarge.html b/pamenlarge.html
index 9b90121f..70b3ca11 100644
--- a/pamenlarge.html
+++ b/pamenlarge.html
@@ -41,7 +41,7 @@ then by 5 is faster than enlarging once by 15.  And because the algorithms
 are different for the different scale factors, some faster than others,
 the order matters too.  For example, the following examples all produce
 the same output -- an image 15 times bigger on edge than the input --
-but with at different spees, each being faster than the one before.
+but at different speeds, each being faster than the one before.
 
 <pre>
 <kbd>