summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorfvogel <fvogel@noemail.net>2016-06-26 20:18:50 (GMT)
committerfvogel <fvogel@noemail.net>2016-06-26 20:18:50 (GMT)
commit150bf52f974b59248fd6703060ec6f681c31286b (patch)
tree56f652797aba5625acefce90ed7d65515b0e8a89
parentd6109099e96dffabc87e94fdc29fead6cfeacbe7 (diff)
downloadtk-150bf52f974b59248fd6703060ec6f681c31286b.zip
tk-150bf52f974b59248fd6703060ec6f681c31286b.tar.gz
tk-150bf52f974b59248fd6703060ec6f681c31286b.tar.bz2
Fixed typos
FossilOrigin-Name: c94ac1406523730637f6699b18159af3e28c57ef
-rw-r--r--doc/FindPhoto.34
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/FindPhoto.3 b/doc/FindPhoto.3
index dea7e05..e4d83f0 100644
--- a/doc/FindPhoto.3
+++ b/doc/FindPhoto.3
@@ -191,8 +191,8 @@ Also, changes made by writing directly to \fIpixelPtr\fR will not be
immediately visible, but only after a call to
\fBTk_ImageChanged\fR or after an event that causes the interested
widgets to redraw themselves.
-For these reasons usually it is preferrable to make changes to
-a copy a of the image data and write it back with
+For these reasons usually it is preferable to make changes to
+a copy of the image data and write it back with
\fBTk_PhotoPutBlock\fR or \fBTk_PhotoPutZoomedBlock\fR.
.PP
\fBTk_PhotoGetImage\fR returns 1 for compatibility with the