summaryrefslogtreecommitdiff
path: root/lib/libcurses/doc
diff options
context:
space:
mode:
authorDavid Krause <david@cvs.openbsd.org>2003-03-10 04:02:51 +0000
committerDavid Krause <david@cvs.openbsd.org>2003-03-10 04:02:51 +0000
commit19fdb6d219cdc3ea1495722bc27d42562dcd78c5 (patch)
tree6dd51d99f33ec4a3a2dc9d7c44949743578c53c6 /lib/libcurses/doc
parentb9b34c1267966b63be8a38ff26f4774aa957eb7d (diff)
duplicate words and spelling fixes in comments
ok miod@
Diffstat (limited to 'lib/libcurses/doc')
-rw-r--r--lib/libcurses/doc/hackguide.html2
-rw-r--r--lib/libcurses/doc/ncurses-intro.html2
2 files changed, 2 insertions, 2 deletions
diff --git a/lib/libcurses/doc/hackguide.html b/lib/libcurses/doc/hackguide.html
index c52dd5b171f..4e1d237f3b7 100644
--- a/lib/libcurses/doc/hackguide.html
+++ b/lib/libcurses/doc/hackguide.html
@@ -558,7 +558,7 @@ Then <CODE>lib_doupdate.c</CODE> goes to work. Its job is to do line-by-line
transformations of <CODE>curscr</CODE> lines to <CODE>newscr</CODE> lines. Its main
tool is the routine <CODE>mvcur()</CODE> in <CODE>lib_mvcur.c</CODE>. This routine
does cursor-movement optimization, attempting to get from given screen
-location A to given location B in the fewest output characters posible. <P>
+location A to given location B in the fewest output characters possible. <P>
If you want to work on screen optimizations, you should use the fact
that (in the trace-enabled version of the library) enabling the
diff --git a/lib/libcurses/doc/ncurses-intro.html b/lib/libcurses/doc/ncurses-intro.html
index c16ecdd19bc..f6d505a50ad 100644
--- a/lib/libcurses/doc/ncurses-intro.html
+++ b/lib/libcurses/doc/ncurses-intro.html
@@ -978,7 +978,7 @@ on and refresh them, the changes made to the overlapping region under historic
To understand why this is a problem, remember that screen updates are
calculated between two representations of the <EM>entire</EM> display. The
-documentation says that when you refresh a window, it is first copied to to the
+documentation says that when you refresh a window, it is first copied to the
virtual screen, and then changes are calculated to update the physical screen
(and applied to the terminal). But "copied to" is not very specific, and
subtle differences in how copying works can produce different behaviors in the