X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/f6bcfd974ef26faf6f91a62cac09827e09463fd1..72858fcf67bf670ea18fe48a6b039d61afa87131:/wxPython/demo/viewer.py

diff --git a/wxPython/demo/viewer.py b/wxPython/demo/viewer.py
index ad438e10a0..befb03ece6 100644
--- 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