Sync with latest script

1 files changed, 4 insertions, 4 deletions

diff --git a/doc/html/qcanvas.html b/doc/html/qcanvas.html
index 5c68676f0..fbfdbd12e 100644
--- a/doc/html/qcanvas.html
+++ b/doc/html/qcanvas.html
@@ -266,7 +266,7 @@ item is an item that is in motion; see setVelocity().)
 canvas item is called with paramater 0. Then all these canvas
 items are called again, with parameter 1. In phase 0, the canvas
 items should not change position, merely examine other items on
-the canvas for which special processing is retquired, such as
+the canvas for which special processing is required, such as
 collisions between items. In phase 1, all canvas items should
 change positions, ignoring any other items on the canvas. This
 two-phase approach allows for considerations of "fairness",
@@ -408,10 +408,10 @@ many objects on the canvas.
 <p> The canvas is divided into chunks which are rectangular areas <em>chunksze</em> wide by <em>chunksze</em> high. Use a chunk size which is about
 the average size of the canvas items. If you choose a chunk size
 which is too small it will increase the amount of calculation
-retquired when drawing since each change will affect many chunks.
+required when drawing since each change will affect many chunks.
 If you choose a chunk size which is too large the amount of
-drawing retquired will increase because for each change, a lot of
-drawing will be retquired since there will be many (unchanged)
+drawing required will increase because for each change, a lot of
+drawing will be required since there will be many (unchanged)
 canvas items which are in the same chunk as the changed canvas
 items.
 <p> Internally, a canvas uses a low-resolution "chunk matrix" to keep