docs: various updates and fixes from Reinier

git-svn-id: trunk@42502 -

README.txt

@@ -7,14 +7,14 @@ independent visual components like buttons, windows, checkbox, treeview and
 many, many more. The LCL is platform independent, so you can write an
 application once and then compile for various platforms without changing code.
 
-Free Pascal at www.freepascal.org is a fast object pascal compiler (and more),
+Free Pascal at www.freepascal.org is a fast Object Pascal compiler (and more),
-that runs on more than 20 platforms (linux, windows, BSD, OS/2, DOS, PowerPC,
+that runs on more than 20 platforms (Linux, Windows, BSD, OS/2, DOS, PowerPC,
 and many more).
 
-The LCL currently supports linux (gtk, gtk2 and qt4), all flavours of windows,
+The LCL currently supports Linux (gtk, gtk2 and qt4), all flavors of Windows
-even wince, Mac OS X (carbon, gtk, qt4), FreeBSD (gtk, gtk2).
+(even wince), Mac OS X (carbon, gtk, qt4), FreeBSD (gtk, gtk2).
-There is experimental support for Solaris and the native pascal backend fpgui
+There is experimental support for Solaris and the native Pascal backend fpgui
-which runs on windows, wince and linux.
+which runs on Windows, Wince and Linux.
 
 --------------------------------------------------------------------------------
 Compilation:
@@ -24,10 +24,10 @@ You don't need ./configure, just do
 
 (BSD users: gmake clean bigide)
 
-This will create the lazarus executable with a lot of packages.
+This will create the Lazarus executable with a lot of packages.
 Start it and enjoy.
 
-If the above gives an error you can try to build a minimal IDE with
+If the above gives an error, you can try to build a minimal IDE with
   []$ make clean all
 
 (BSD users: gmake clean all)
@@ -49,22 +49,23 @@ Documentation:
 
 The official site is www.lazarus.freepascal.org. There you can find the FAQ -
 the frequently asked questions.
-Documents about specific topics can be found at lazarus-ccr.sourceforge.net.
+Documents about specific topics can be found at 
-Examples, how to use the LCL can be found in the 'examples' directory.
+wiki.freepascal.org/Lazarus_Documentation.
+Examples on how to use the LCL can be found in the 'examples' directory.
 Help, documents and files about Free Pascal are at www.freepascal.org.
 
 
 --------------------------------------------------------------------------------
 Mailing list:
 
-There is a very active and helpful mailing list for lazarus, where the
+There is a very active and helpful mailing list for Lazarus, where the
 developers interact, share ideas, discuss problems, and of course answer
 questions.
 You can subscribe at
 http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
 
 --------------------------------------------------------------------------------
-How to help lazarus:
+How to help Lazarus:
 
 If you find bugs, don't hesitate to use the bug tracking tool at the website,
 or send an email to the list.

components/README.txt

@@ -22,8 +22,8 @@ customform
   Registering custom form descendants in the IDE.
 
 daemon
-  Package to create programs that run as daemon under linux or service under
+  Package to create programs that run as daemon under Linux or service under
-  windows.
+  Windows.
 
 datadict
   Support for data dictionaries for the IDE and applications.
@@ -41,7 +41,7 @@ filebrowser
   A file browser window for the IDE.
 
 fpcunit
-  template for a fpcunit gui test runner
+  Template for a fpcunit GUI test runner.
 
 fpweb
   Units that support web server and web client programming.
@@ -65,7 +65,7 @@ lazthread
    ?
 
 leakview
-  Extends the IDE with a graphical viewer for the heaptrc output.
+  Extends the IDE with a graphical viewer for heaptrc output.
 
 pochecker
   Validates translated PO files.
@@ -89,7 +89,7 @@ opengl
   An OpenGL control.
 
 paradox
-  Support for paradox databases.
+  Support for Paradox databases.
 	
 PascalScript
   Version of RemObjects Pascal Script adapted for use in the Lazarus IDE.
@@ -130,7 +130,7 @@ synedit
   The text editor control used by the IDE.
 
 synunihighlighter
-  An universal highlighter for synedit.
+  A universal highlighter for synedit.
 
 tachart
   A control for graphs and plots.

docs/BigIDE.txt

@@ -15,7 +15,7 @@ components/Makefile.fpc   package directories
 ide/lazarus.pp            package names
 
 
-Do not forget update the ide/Makefile and components/Makefile.
+Do not forget to update the ide/Makefile and components/Makefile.
 
 Compiling the bigide:
 

docs/CrossCompile.txt

@@ -1,4 +1,4 @@
-Hints to cross compile under linux/xxxBSD
+Hints to cross compile under Linux/xxxBSD
 =========================================
 
 
@@ -7,24 +7,26 @@ Thanks to Vincent Snijders for the hints.
 ================================================================================
 
 A.
-for fpc 2.0 and up. On linux and bsd to other platforms like windows.
+For FPC 2.0 and up. On Linux and BSD to other platforms.
+(Note: not necessary for cross-compiling to Windows as FPC has had an internal 
+linker for this platform).s
 
 Abstract:
-  The following describes how to setup the binutils, fpc and lazarus for
+  The following describes how to setup the binutils, FPC and Lazarus for
   crosscompiling to other targets. Once you have these cross files you can
   switch easily in the Lazarus IDE between any of the target platforms.
 
 IMPORTANT: The FPC units must have the same date/version for all platforms,
   because you will use only one compiler. That means:
-  Whenever you update your FPC, you must update all other cross fpc units too.
+  Whenever you update your FPC, you must update all other cross FPC units too.
-  The scripts will help you doing this.
+  The scripts will help you to do this.
 
  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 
 A.1
 
 Requirements:
-  An installed and working fpc. Preferrably the latest stable release.
+  An installed and working fpc. Preferably the latest stable release.
   A good internet connection or manually downloaded FPC sources and binutils.
 
 The following steps don't need the root user. They can be done as normal user.
@@ -77,13 +79,13 @@ TODO: write, where you can get the fpc 'install' directory sources.
 
 ================================================================================
 
-What the lazarus scripts do / Doing it by hand:
+What the Lazarus scripts do / Doing it by hand:
 
 
-1. Download the fpc sources
+1. Download the FPC sources
 
-  IMPORTANT: Your current FPC must be the same version/date as the fpc sources.
+  IMPORTANT: Your current FPC must be the same version/date as the FPC sources.
-  If your installed fpc is different, you can compile a new fpc from the
+  If your installed FPC is different, you can compile a new FPC from the
   sources.
 
 
@@ -127,7 +129,7 @@ What the lazarus scripts do / Doing it by hand:
 
 3. Cross build binutils
 
-  In the fpc source directory there is a script to build the binutils for all
+  In the FPC source directory there is a script to build the binutils for all
   cross platforms: install/cross/buildcrossbinutils
   Create a copy of the script:
 
@@ -151,7 +153,7 @@ What the lazarus scripts do / Doing it by hand:
   The script will automatically combine this to ~/download/binutils-2.14.tar.gz.
   The other variables define what target platforms you have. The default is to
   build quite a lot, so compilation will take some time (hours).
-  For cross compile to windows, you need only
+  For cross compile to Windows, you need only
 
   TARGETS_WIN="mingw32"
   
@@ -175,9 +177,9 @@ What the lazarus scripts do / Doing it by hand:
   without failed targets.
 
 
-4. Cross build fpc
+4. Cross build FPC
 
-  In the fpc source directory there is a script to build the fpc snapshot for
+  In the FPC source directory there is a script to build the FPC snapshot for
   all cross platforms: install/cross/buildcrosssnapshot
   Create a copy of the script:
 
@@ -204,7 +206,7 @@ What the lazarus scripts do / Doing it by hand:
 
   []$ sh buildcrosssnapshot.sh
 
-  This will create the fpc binaries under
+  This will create the FPC binaries under
   ~/freepascal/binutils/cross/destination/.
 
 

docs/DesignGuidelines.txt

@@ -1,12 +1,12 @@
-This is for lazarus developers:
+This is for Lazarus developers:
 
 Coding style:
 - Since one style is easier to read, Lazarus follows the Borland Coding style
-  guide lines. Of course, almost anyone will find some points there, that are
+  guidelines. Of course, almost anyone will find some points there, that are
-  arguable less readable than other styles. That's ok, just try to follow at
+  arguably less readable than other styles. That's OK, just try to follow at
   least 90%.
-- Try to avoid unit circles. This makes it easier to navigate and when unit is
+- Try to avoid unit circles. This makes it easier to navigate and allows to
-  growing allows to split it.
+  split the unit when it is growing.
 - Minimize the number of calls from Interfaces to LCL, when performing an
   action requested by the LCL. The interfaces only notify the LCL, never forces
   something. The LCL decides.
@@ -14,13 +14,13 @@ Coding style:
     Notifications for TControl decendants should be named CNxxx.
 - All code must work with all checks (range, io, overflow, stack) on. Beside
   that this helps debugging, some users put these checks into their fpc.cfg, so
-  they are applied to whole lazarus. Including packages and examples.
+  they are applied to whole Lazarus. Including packages and examples.
 
 
 New files:
 - Every file should start with a header containing the license and a few lines
   describing the content.
-- pascal sources should have lowercase filenames (.pas, .pp, .inc, .lfm, .lrs)
+- Pascal sources should have lowercase filenames (.pas, .pp, .inc, .lfm, .lrs)
 
 Include files:
 - should start with the {%MainUnit } directive

docs/ExtendingTheIDE.txt

@@ -1,7 +1,7 @@
 Extending the IDE (Overview)
 ============================
 
-The online pages are more uptodate and have more examples:
+The online pages are more up to date and have more examples:
 http://wiki.lazarus.freepascal.org/Extending_the_IDE
 
 

docs/ForDelphians.txt

@@ -1,6 +1,6 @@
-This text is for people knowing Delphi and it describes the differences.
+This text is for people who know Delphi; it describes differences with Delphi.
 
-The online document is more uptodate:
+The online document is more up to date:
 http://wiki.lazarus.freepascal.org/Lazarus_Documentation#Coming_from_Delphi
 
 
@@ -8,7 +8,7 @@ Delphi -> Lazarus
 =================
 
 Lazarus is an Rapid Application Development (RAD) tool like Delphi. That means
-it comes with a visual component library and an IDE. The lazarus component
+it comes with a visual component library and an IDE. The Lazarus component
 library (LCL) is very similar to Delphi's VCL. Most units, classes and
 properties have the same name and functionality. This makes porting easy. But
 Lazarus is *not* an 'open source Delphi clone'. So don't expect 100%
@@ -16,9 +16,9 @@ compatibility.
 
 The biggest differences:
 Lazarus is completely open source, is written platform independent and uses the
-mighty FreePascal compiler (FPC). FPC runs on more than 15 platforms. But not
+mighty FreePascal compiler (FPC). FPC runs on more than 15 platforms. However, 
-all packages and libs are ported, so Lazarus currently runs on Linux,
+not all packages and libs are ported, so Lazarus currently runs on Linux,
-Free/Open/NetBSD and the win32 port is under heavy development.
+Free/Open/NetBSD and win32.
 
 Lazarus is not complete, as is this text. We are always searching for new
 developers, packagers, porters, documentation writers, ... .

docs/INSTALL.txt

@@ -5,19 +5,19 @@ Lazarus provides two main parts:
 - LCL - the Lazarus Component Library
 - IDE - the RAD tool (editor, form designer, GUI for debugger and compiler, ...)
 
-What is required for lazarus:
+What is required for Lazarus:
-- FreePascal - the FreePascal Compiler plus packages plus fpc sources.
+- FreePascal - the FreePascal Compiler plus packages plus FPC sources.
-               IMPORTANT: try to get the same version of the compiler sources
+  IMPORTANT: try to get the same version of the compiler sources
-                          as the installed compiler.
+             as the installed compiler.
 - Under Linux/xxxBSD: gtk2 libaries - Most distributions already install them.
-     See www.gtk.org.
+  See www.gtk.org.
 
 
 The FAQ - Frequently Asked Question is available at www.lazarus.freepascal.org
   and some can be found in the file 'FAQ'.
 
 
-The following will describe how to get FreePascal and how to install lazarus
+The following will describe how to get FreePascal and how to install Lazarus
 properly:
 
 ================================================================================
@@ -27,47 +27,47 @@ properly:
 1.1 This is the short version. For more details, see the following sections.
 
   Lazarus is intended to be a development tool. Therefore it is designed, that
-  any normal user can easily install his local copy. This means, lazarus does
+  any normal user can easily install his local copy. This means Lazarus does
-  not need to be installed as root and it does not any symlinks or configuration
+  not need to be installed as root and it does not create any symlinks or 
-  entries. You can literally just unpack it into a directory of your choice and
+	configuration entries. You can literally just unpack it into a directory of 
-  compile it.
+	your choice and compile it.
 
 
 1.2 Under Linux/BSD:
 
-  Make sure, that you have installed X, gtk2 and gtk2-devel.
+  Make sure that you have installed X, gtk2 and gtk2-devel.
 
   Fedora:
     yum install gtk2 gtk2-devel
 
   Debian/Ubuntu:
-    apt-get install lazarus
+    apt-get install lazarus #will pull in required gtk dependencies
 
   Download and install FreePascal. Either the rpm, tgz or the daily snapshot.
-  You need at least fpc 2.4.2 (2.4.2 is the stable version of fpc, the 2.5.1 is
+  You need at least FPC 2.6.2 (2.6.2 is the stable version of FPC; uneven 
-  the development version).
+	versions like 2.7.1 are development versions).
 
-  To compile lazarus (LCL + IDE) go to your unpacked lazarus source and do:
+  To compile Lazarus (LCL + IDE) go to your unpacked Lazarus source and do:
   []$ make clean all
 
-  You don't need "./configure" and you don't need "make install". You now have
+  You don't need "./configure" and you don't need "make install". You now 
-  already a complete lazarus. You can start the IDE with "./lazarus".
+	already have a complete Lazarus. You can start the IDE with "./lazarus".
   The "make install" as root will just copy the files and set some nice symlinks
   and desktop entries.
 
 
 1.3 Under Mac OS X:
 
-  What you need: Apple Developer-tools
+  What you need: Apple Developer tools
-  The Developer-tools are included on the original OSX installation-CDs, or
+  The Developer tools are included on the original OSX installation CDs, or
-  download at ADC (free registration required)
+  can be downloaded at ADC (free registration required)
   http://developer.apple.com/.
 
   Download and install FreePascal. Either the dmg or the daily snapshot.
-  You need at least fpc 2.4.2 (2.4.2 is the stable version of fpc, the 2.5.1 is
+  You need at least FPC 2.6.2 (2.6.2 is the stable version of FPC; uneven 
-  the development version).
+	versions like 2.7.1 are development versions).
 
-  To compile lazarus (LCL + IDE) go to your unpacked lazarus source and do:
+  To compile Lazarus (LCL + IDE) go to your unpacked Lazarus source and do:
   []$ make clean all
 
   You don't need "./configure" and you don't need "make install". You now have
@@ -81,34 +81,34 @@ properly:
 --------------------------------------------------------------------------------
 2.1 Installing FreePascal under Linux:
 
-  Lazarus requires a fpc (FreePascal) version 2.4.2 (or newer) and it requires
+  Lazarus requires FPC (Free Pascal) version 2.6.2 (or newer) and it requires
-  both the compiled fpc libs (binaries) and the fpc sources. Most of the Linux
+  both the compiled FPC libs (binaries) and the FPC sources. Most of the Linux
-  distributions contain packages for FreePascal (look for fpc). Use your package
+  distributions contain packages for FreePascal (look for FPC). Use your package
   manager to install them.
 
-  The fpc binaries:
+  The FPC binaries:
-  At the lazarus downloads section (www.lazarus.freepascal.org
+  At the Lazarus downloads section (www.lazarus.freepascal.org
   or http://sourceforge.net/project/showfiles.php?group_id=89339) you can get
-  the rpm/deb of the freepascal compiler(compiler / linux) and its packages.
+  the rpm/deb of the Free Pascal compiler(compiler / linux) and its packages.
-  Or if you don't have a rpm system, you can download and install the tars from
+  Alternatively, if you don't have a rpm system, you can download and install 
-  the www.freepascal.org.
+	the tars from www.freepascal.org.
   If you want to compile the binaries for yourself see the BSD section.
 
-  The fpc sources:
+  The FPC sources:
-  The easiest way to get the freepascal sources is via svn. Of course you can
+  The easiest way to get the Free Pascal sources is via svn. Of course you can
   also download it as whole, see http://www.freepascal.org/develop.html
-  for the daily snapshot of the release tree (2.5.x).
+  for the daily snapshot of the release tree (2.7.x).
 
-  The fpc sources via svn:
+  The FPC sources via svn:
-  Create a directory, where you would like to put the sources. You don't need
+  Create a directory where you would like to put the sources. You don't need
-  to be root to do this. Any normal user can do this.
+  to be root to do this.
   First create a directory for fpc (e.g. /home/username/freepascal) then do
   the following:
 
   []$ bash
   []$ svn checkout http://svn.freepascal.org/svn/fpc/trunk fpc
 
-  This will create a directory fpc, which can be later used in the IDE.
+  This will create a directory fpc, which can later be used in the IDE.
 
   Hint:
   To download/update the latest changes you can simply do
@@ -121,16 +121,17 @@ properly:
 --------------------------------------------------------------------------------
 2.2 Installing FreePascal under Windows:
 
-  If you use the windows installer for lazarus, then you don't need to install 
+  If you use the Windows installer for lazarus, then you don't need to install 
-  FreePascal separately, because the installer already contains the necessary
+  Free Pascal separately, because the installer already contains the necessary
   files.
     
   See http://www.freepascal.org/down-win32.html. You can find a list of mirrors
-  at http://www.freepascal.org/sdown.html. Download for example fpc as one big
+  at http://www.freepascal.org/sdown.html. Download for example FPC as one big
-  file, unzip it and run the install.exe. Then extend your PATH variable to the
+  file, unzip it and run install.exe. Then extend your PATH variable to the
-  fpc directory. For example under win98: Edit autoexec.bat and add the line
+  FPC directory. For example under Windows 98: 
+	Edit autoexec.bat and add the line
   PATH=%PATH%;C:\pp\bin\bin\win32
-  Then restart win98.
+  Then restart Windows.
 
   ToDo: explain how to download fpc sources and build the compiler
 
@@ -142,12 +143,12 @@ properly:
  
  Effectively, you need:
 
- - a file with all sources, or two (fpc and lazarus)
+ - a file with all sources, or two (FPC and Lazarus)
-    (1) e.g. for fpc  ftp://ftp.freepascal.org/fpc/dist/Linux/separate/sources.tar
+    (1) e.g. for FPC ftp://ftp.freepascal.org/fpc/dist/Linux/separate/sources.tar
      preferably an export (no SVN/ dirs). The above file misses this
     (2) Lazarus source snapshot.
-  - _any_ starting compiler from the 2.4.2 branch) You can do a check by parsing
+  - _any_ starting compiler from the 2.6.2 branch) You can do a check by parsing
- 	  the output of 'fpc -v'  if it is 2.4.x or 2.5.x it is ok.
+ 	  the output of 'fpc -v'  if it is 2.6.2, it is ok.
   - dependant packages. (for FreeBSD that is gtk2, and
     GNU make, iconv and gettext)
 
@@ -193,16 +194,16 @@ properly:
 
 
 --------------------------------------------------------------------------------
-2.4 Installing FPC on Mac OS X
+2.4 Installing FPC on Mac OSX
 
   Read 1.3 first.
 
   Information:
   http://www.freepascal.org/fpcmac.html#TargetDarwin
 
-  Download the latest Mac OS X dmg package.
+  Download the latest Mac OSX dmg package.
-  Since fpc for Mac OS X is under heavy development, it s recommended to use
+  Since FPC for Mac OSX is under heavy development, it s recommended to use
-  the latest fpc from svn.
+  the latest FPC from svn.
 
   Open a terminal and type (without the []$)
   
@@ -233,48 +234,48 @@ properly:
 3. Installing Lazarus
 
 --------------------------------------------------------------------------------
-3.1 Installing Lazarus under Linux/BSD/MacOSX:
+3.1 Installing Lazarus under Linux/BSD/Mac OSX:
 
-  Because the whole lazarus stuff is installed into one directory, uninstall
+  Because the whole Lazarus stuff is installed into one directory, uninstall
-  is very easy and you don't need to be root to install lazarus.
+  is very easy and you don't need to be root to install Lazarus.
   You can get tgz/zip files from the downloads section or you can download it
   directly via svn.
   
   Hint: Most Linux distributions contain a Lazarus package. Go to your package
         manager and install it.
 
-  Downloading lazarus svn: svn provides an easy way to update your sources by
+  Downloading Lazarus svn: svn provides an easy way to update your sources by
   only downloading the changes. This is the recommended way and saves you a lot
-  of time. A connection to the internet is needed for this:
+  of time. A connection to the internet is needed for this.
   You don't to be root. Lazarus does not need any special permissions, neither
   during installation nor at runtime.
-  First create a directory for lazarus (e.g. /home/username/freepascal) then do
+  First create a directory for Lazarus (e.g. /home/username/freepascal) then do
   the following:
   
-  connect to the svn server (note: lazarus and freepascal use the same server)
+  connect to the svn server (note: Lazarus and Free Pascal use the same server)
   
   []$ svn checkout http://svn.freepascal.org/svn/lazarus/trunk lazarus
 
-  compile lazarus:
+  compile Lazarus:
 
   []$ cd lazarus
   []$ make          (gmake on BSD)
 
-  If fpc is installed correct, the compilation should work without problems. If
+  If FPC is installed correctly, the compilation should work without problems.
-  not, see FAQ.
+	If not, see the FAQ.
-  Start lazarus
+  Start Lazarus:
 
   []$ ./lazarus
 
-  The IDE should start. If you started lazarus in a terminal, you can see some
+  The IDE should start. If you started Lazarus in a terminal, you can see some
   notes about missing settings. This is normal at first start.
-  The IDE automatically tries to find out where the freepascal compiler and its
+  The IDE automatically tries to find out where the Free Pascal compiler and its
   sources are installed by searching in the most common directories.
   Check the paths:
     Use the IDE menu to go to
       Environment -> Environment Options -> Files
 
-    The 'FPC Source directory' should point to your fpc source directory. This
+    The 'FPC Source directory' should point to your FPC source directory. This
     directory normally ends with /fpc/ or /fpcsrc/ (e.g. /usr/share/fpcsrc or
     /home/username/freepascal/fpc) and
     contains directories like 'compiler', 'docs', 'fcl', 'rtl' and 'packages'.
@@ -283,13 +284,14 @@ properly:
 
 
   Hint:
-  To update lazarus you can use
+  To update Lazarus you can use
 
   []$ cd /home/username/freepascal/lazarus
   []$ svn up
   []$ make clean all   (gmake on BSD)
   
-  This will rebuild lazarus and create a minimal IDE with only the basic packages.
+  This will rebuild Lazarus and create a minimal IDE with only the basic 
+	packages.
   
   []$ make idepkg
 
@@ -298,32 +300,26 @@ properly:
 3.1 Installing Lazarus under Windows:
 
   Just download and install the .exe file. You can get the files from:
-  http://sourceforge.net/project/showfiles.php?group_id=89339 (stable release) or
+  http://sourceforge.net/project/showfiles.php?group_id=89339 (stable release)
+	or
   http://snapshots.lazarus.shikami.org/lazarus/ (snapshots)
 
 
-  Thx to Joe for this Step-by-step description:
+  Thanks to Joe for this Step-by-step description:
 
-  You have to download the lazarus source:
+  You have to download the Lazarus source:
   ftp://ftp.freepascal.org/pub/fpc/source/lazarus.zip
 
   Then unzip it to c:\lazarus for example.
-  You have to install at least fpc 2.4.2. It compiles to me and lazarus.exe
+  You have to install at least FPC 2.6.2, e.g. in
-  works. The path to my fpc is: c:\pp\bin\win32. In this directory you
+	c:\pp\bin\win32. 
-  can find a lot of exe (make, grep, ppc386, and so on).
+	In this directory you can find a lot of exes (make, grep, ppc386, and so on).
 
   Open a command line. Start->Run...>command or choose MS-DOS icon.
   Type:
   cd c:\lazarus
-  set path=c:\pp\bin\win32;c:\lazarus  //of course change the first to
+	rem of course adjust to your path:
-                                       //the path of yours
+  set path=c:\pp\bin\win32;c:\lazarus  
   make
 
-  If you are lucky then you can type: lazarus.exe
+  If you are lucky then you can type: lazarus.exe  
-
-  If you extracted lazarus to another drive, eg.: d:\lazarus. It can happen
-  that you need the gnu utility to make it. If you have it, you can take its
-  path to set path=...;<gmakepath> but it is simpler not to choose drive d:\
-
-  That's all.
-

docs/acknowledgements.txt

@@ -1,4 +1,4 @@
-#Lazarus is using following third party libraries and tools
+#Lazarus uses the following third party libraries and tools
 
 
 #Component libraries:

examples/mssql/README.txt

@@ -3,6 +3,8 @@ Example program for the MS SQL Server and Sybase connectors in Lazarus.
 
 These connectors require the FreeTDS shared library (dblib.dll/.so/.dylib), which at least on Windows requires libiconv2.dll for UTF8 support.
 These can be downloaded via www.freetds.org and are provided by a lot of Linux distributions.
+As a courtesy, FreePascal has a downloadable version for Windows at:
+ftp://ftp.freepascal.org/fpc/contrib/windows/
 
 The program will ask you for a database type (Sybase or MS SQL Server), username, password, server etc. and then connect.
 Then it will query the server for database server information and show the results in a dbgrid.