added comments to the makefile; added WX_CONFIG var to be able to use a different...

[wxWidgets.git] / wxPython / demo / viewer.py

diff --git a/wxPython/demo/viewer.py b/wxPython/demo/viewer.py
index ad438e10a00f300951beaa4b3f1c839b3634e5ff..befb03ece6d6b7294f40962dbe3f17eb51a8f683 100644 (file)
--- a/wxPython/demo/viewer.py
+++ b/wxPython/demo/viewer.py
@@ -35,9 +35,9 @@
         When using wxPython, the call to app.Mainloop() takes over
         the thread from which it is called.  This presents a
         problem for applications that want to use the standard
-        Python command line user interface, while occasionaly
+        Python command line user interface, while occasionally
         creating a GUI window for viewing an image, plot, etc.
-        One soultion is to mangage the GUI in a second thread.
+        One solution is to manage the GUI in a second thread.
 
         wxPython does not behave well if windows are created in
         a thread other than the one where wxPython was originally