Fix spelling errors

diff --git a/src/cairo/a_chain_of_bugs.mdwn b/src/cairo/a_chain_of_bugs.mdwn
index 128674792efd7689cdded1bed024afd2f2de06a8..1991c0dba6f1758e5935901039b22d595e361a7c 100644 (file)
--- a/src/cairo/a_chain_of_bugs.mdwn
+++ b/src/cairo/a_chain_of_bugs.mdwn
@@ -19,7 +19,7 @@ Using Firefox3 with cairo 1.6.4 on a Fedora9 system, I did a "print to
 file" and obtained the following PDF output: [[bug.pdf]] (14,465
 bytes).
 
-This output is still quite accurate and farly usable. But we've
+This output is still quite accurate and fairly usable. But we've
 already seen problem #1. Note that the file size has increased by a
 factor of 100 compared to the original HTML. The PDF does have more
 content, (firefox adds a header and footer for example), but nothing
@@ -73,8 +73,8 @@ would have been larger than normal, but the final result would have
 looked great and printed just fine. And in that case, I probably would
 have never even received a bug report.
 
-But there's a third problme that is the most pernicious, because it
-results in the final result looking ust awful. When cairo inserts the
+But there's a third problem that is the most pernicious, because it
+results in the final result looking just awful. When cairo inserts the
 full-page fallback into the final PostScript file, it is inserting it
 at 300dpi, but it does that only after rendering it to an intermediate
 72dpi image, which is then scaled up. That's why the final PostScript
@@ -100,10 +100,12 @@ text that appears is much more sharp than in the previous PostScript
 file). However, the original HTML table is now entirely missing. So
 there's definitely something wrong with my patch.
 
-I'll continue to chase these bugs down, and continue my quest to get
-high-quality display and print output from cairo-using
-applications. It can be a difficult goal, but it's also a lot of fun
-and very rewarding.
-
-Please feel free to jump in and help if you're interested.
+I'll continue to chase these bugs down. The interesting thing about
+this chain is that it's only as strong as its weakest link. Fixing any
+of the individual problems here will make the end-to-end behavior be
+quite acceptable.
 
+And I'll continue my quest to get high-quality display and print
+output from cairo-using applications. It can be a challenging goal,
+but it's also a lot of fun and very rewarding. Please feel free to
+jump in and help if you're interested.