applied typos and spelling error fixes patch from Olly Betts

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@15779 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775

docs/gtk/install.txt

@@ -36,11 +36,13 @@ If you want to remove wxWindows on Unix you can do this:
 
 If you want to do some more serious cross-platform programming with wxWindows,
 such as for GTK and Motif, you can now build two complete libraries and use
-them concurretly. For this end, you have to create a directory for each build
+them concurrently. For this end, you have to create a directory for each build
 of wxWindows - you may also want to create different versions of wxWindows
 and test them concurrently. Most typically, this would be a version configured
-with --enable-debug_flag and one without. Note, that only one build can currently
-be installed, so you'd have to use local version of the library for that purpose.
+with --enable-debug_flag and one without. Note, that only one build can
+currently be installed, so you'd have to use local version of the library for
+that purpose.
+
 For building three versions (one GTK, one Motif and a debug version of the GTK
 source) you'd do this:
 
@@ -84,7 +86,7 @@ support definitely won't).
 
 You get errors during compilation: The reason is that you probably have a
 broken compiler, which includes a lot of old gcc versions. In particular, if
-you use gcc 2.8 you have to disable optimsation as the compiler will give up
+you use gcc 2.8 you have to disable optimisation as the compiler will give up
 with an internal compiler error.
 
 You get immediate segfault when starting any sample or application: This is
@@ -122,7 +124,7 @@ YOU USE AND WHAT ERROR WAS REPORTED. I know this has no effect, but I tried...
 -----------------------
 
 wxWindows/GTK requires the GTK+ library to be installed on your system. It has
-to be a stable version, preferebly version 1.2.10 (at least 1.2.3 is required,
+to be a stable version, preferably version 1.2.10 (at least 1.2.3 is required,
 1.2.7 is strongly recommended).
 
 You can get the newest version of the GTK+ from the GTK homepage at:
@@ -189,7 +191,7 @@ as described above.
 
 If you have pthreads library installed, but have a gtk version
 which does not yet support threading, you need to explicitly
-diable threading by using the option --disable-threads.
+disable threading by using the option --disable-threads.
 
 Note that configure assumes your flex will generate files named
 "lexyy.c", not "lex.yy.c". If you have a version which does
@@ -284,8 +286,9 @@ The following options handle the kind of library you want to build.
     --enable-no_deps        Enable compilation without creation of
                             dependency information.
 
-    --enable-permissive     Enable compilation without creation of
-                            giving erros as soon as you compile with
+    --enable-permissive     Enable compilation without checking for strict
+                            ANSI conformance.  Useful to prevent the build
+                            dying with errors as soon as you compile with
                             Solaris' ANSI-defying headers.
 
     --enable-mem_tracing    Add built-in memory tracing.
@@ -343,7 +346,7 @@ are
 
     --disable-clipboard     Disables Clipboard.
 
-    --disable-serial        Disables object instance serialiasation.
+    --disable-serial        Disables object instance serialisation.
 
     --disable-streams       Disables the wxStream classes.
 
@@ -377,9 +380,9 @@ make yourself some coffee, as it will take some time. On an old
 warning messages depending in your compiler.
 
 If you want to be more selective, you can change into a specific
-directiry and type "make" there.
+directory and type "make" there.
 
-Then you may install the library and it's header files under
+Then you may install the library and its header files under
 /usr/local/include/wx and /usr/local/lib respectively. You
 have to log in as root (i.e. run "su" and enter the root
 password) and type
@@ -420,7 +423,7 @@ clean:
 	rm -f *.o minimal
 
 This is certain to become the standard way unless we decide
-to sitch to tmake.
+to stick to tmake.
 
 2) The other way creates a project within the source code
 directories of wxWindows. For this endeavour, you'll need