Compile fix (include order) for Unicode under Unix.

[wxWidgets.git] / docs / html / faqgen.htm

diff --git a/docs/html/faqgen.htm b/docs/html/faqgen.htm
index d945ff7ff8dd747ed1b147148ac0d4b9a5cd4ba0..43776e0578d1ed52468a0737679d1e7fa5010eb3 100644 (file)
--- a/docs/html/faqgen.htm
+++ b/docs/html/faqgen.htm
@@ -130,10 +130,10 @@ platform-independent code, such as the wxTreeCtrl and wxListCtrl classes.<P>
 No. This is a much-discussed topic that has (many times) ended with the conclusion that it is in
 wxWindows&#39; best interests to avoid use of templates. Not all compilers can handle
 templates adequately so it would dramatically reduce the number of compilers
 No. This is a much-discussed topic that has (many times) ended with the conclusion that it is in
 wxWindows&#39; best interests to avoid use of templates. Not all compilers can handle
 templates adequately so it would dramatically reduce the number of compilers

-and platforms that could be supported. It would also be undesirable to make
+and platforms that could be supported. It would also be undersirable to make

 wxWindows dependent on another large library that may have to be downloaded and installed.
 In addition, use of templates can lead to executable bloat, which is something
 wxWindows dependent on another large library that may have to be downloaded and installed.
 In addition, use of templates can lead to executable bloat, which is something

-wxWindows 2 is strenuously trying to avoid.<P>
+wxWindows 2 is strenously trying to avoid.<P>

 
 The standard C++ string class is not used, again because it is not available to all compilers,
 and it is not necessarily a very efficient implementation. Also, we retain more flexibility
 
 The standard C++ string class is not used, again because it is not available to all compilers,
 and it is not necessarily a very efficient implementation. Also, we retain more flexibility