docs: minor grammar and formatting fixes

1 files changed, 13 insertions, 15 deletions

diff --git a/docs/INSTALL.txt b/docs/INSTALL.txt
index 978cf247..806b7d82 100644
--- a/docs/INSTALL.txt
+++ b/docs/INSTALL.txt
@@ -35,9 +35,9 @@ makes the search paths for you applications a little easier to setup.
  Building fpGUI using Lazarus
  ============================
 
-I use a Lazarus feature call Packages that compiles the required 
-units and keeps track of the compiled units and paths when creating 
-applications.  
+I use a Lazarus feature call Packages that compiles the required
+units and keeps track of the compiled units and paths when creating
+applications.
 
  * Start Lazarus
  * Select Components->Open Package File (*.lpk) and select the
@@ -138,9 +138,9 @@ a separate install - but included on the install DVD).
 An example workflow to work with any fpgui app is:
 a) launch X11 (Applications -> Utilities)
 b) start the X11 console xterm (Cmd+N or from the X11 menu)
-c) type the path to your fpgui application ( example: cd
-./Documents/fpgui/examples/apps   if you put fpgui in your Documents
-folder)
+c) change to the directory of the fpGUI application. For example:
+     cd ./Documents/fpgui/examples/apps
+   if you put fpgui in your Documents folder.
 d) type ./appname to start the application "appname"
 
  * Apparently starting fpGUI apps from an icon on the desktop requires that you
@@ -149,23 +149,21 @@ d) type ./appname to start the application "appname"
    from a X11 console, then it runs first time.
 
  * This issue is more about FPC then fpGUI specific, but it's handy to know. In
-   many standard Xcode + X11 installation, the linker could not find the X11
+   many standard Xcode + X11 installation, the linker can't find the X11
    libraries. So changing the fpc.cfg by adding
       -Fl/usr/X11/lib
    in the search library path solved the problem. Mac usually doesn't let you
-   choose the path during installation, so probably other Snow Leopard users
-   will have to double check the correct X11 library path.
+   choose the path during installation, so probably other OSX users will
+   have to double check the correct X11 library path.
 
- * Compiling from the command line, the compiler cannot create the 
+ * Compiling from the command line, the compiler cannot create the
    sub-directory "units" used by most demos inluded with fpGUI. So remember to
-   create such a directory if the compiler fails. When using Lazarus IDE to
-   compile fpGUI projects, the IDE normally creates the missing unit output 
-   path for you.
+   create such a directory if the compiler fails. The compiler output will
+   clearly state such a situation. When using Lazarus or Maximus IDE to compile
+   fpGUI projects, the IDE will creates the missing unit output path for you.
 
 
 
                 =================[  END  ]===================
 
 
-
-