fix formatting and word changes to tiger extension install section

git-svn-id: http://svn.osgeo.org/postgis/trunk@10981 b70326c6-7e19-0410-871a-916f4a2858ee

diff --git a/doc/installation.xml b/doc/installation.xml
index 36fbe6bdbe236f61eedc3f1b727925c601cbf19a..125a19b355287881dec4838ed8dd94a26f54d029 100644 (file)
--- a/doc/installation.xml
+++ b/doc/installation.xml
@@ -996,37 +996,37 @@ Failed: 0
                        <listitem><para>First get binaries for PostGIS 2.1.0 or compile and install as usual.  This should install the necessary extension files as well for tiger geocoder.</para></listitem>
                        <listitem><para>Connect to your database via psql or pgAdmin or some other tool and run the following SQL commands.  Note that if you are installing in a database that already has postgis, you don't need to do the first step.  If you have <varname>fuzzystrmatch</varname> extension already installed, you don't need to do the second step either.</para>
                        <para><programlisting>CREATE EXTENSION postgis;         
-       CREATE EXTENSION fuzzystrmatch;
-       CREATE EXTENSION postgis_tiger_geocoder;</programlisting></para></listitem>
+CREATE EXTENSION fuzzystrmatch;
+CREATE EXTENSION postgis_tiger_geocoder;</programlisting></para></listitem>
                        <listitem><para>To confirm your install is working correctly, run this sql in your database:</para>
                                <programlisting>SELECT na.address, na.streetname,na.streettypeabbrev, na.zip
        FROM normalize_address('1 Devonshire Place, Boston, MA 02109') AS na;</programlisting>
                                <para>Which should output</para>
                                <para><screen> address | streetname | streettypeabbrev |  zip
-       ---------+------------+------------------+-------
-                  1 | Devonshire | Pl               | 02109</screen></para>
+---------+------------+------------------+-------
+          1 | Devonshire | Pl               | 02109</screen></para>
                        </listitem>
-                       <listitem><para>Create a new profile in <varname>tiger.loader_platform</varname> with the paths of your executables and server. </para>  
-                               <para>So for example to create a profile called debbie that follows <code>sh</code> convention. I would do:</para>
+                       <listitem><para>Create a new record in <varname>tiger.loader_platform</varname> table with the paths of your executables and server. </para>  
+                               <para>So for example to create a profile called debbie that follows <code>sh</code> convention. You would do:</para>
                                <programlisting>INSERT INTO tiger.loader_platform(os, declare_sect, pgbin, wget, unzip_command, psql, path_sep, 
                   loader, environ_set_command, county_process_command)
-       SELECT 'debbie', declare_sect, pgbin, wget, unzip_command, psql, path_sep, 
-                  loader, environ_set_command, county_process_command
-         FROM tiger.loader_platform
-         WHERE os = 'sh';</programlisting>
-                               <para>And then edit the paths in the <emphasis>declare_sect</emphasis> to those that fit Debbie's pg path locations.</para>
+SELECT 'debbie', declare_sect, pgbin, wget, unzip_command, psql, path_sep, 
+          loader, environ_set_command, county_process_command
+  FROM tiger.loader_platform
+  WHERE os = 'sh';</programlisting>
+                               <para>And then edit the paths in the <emphasis>declare_sect</emphasis> column to those that fit Debbie's pg, unzip,shp2pgsql, psql, etc path locations.</para>
                        
                                <para>If you don't edit this  <varname>loader_platform</varname> table, it will just contain common case locations of items and you'll have to edit the generated script after the script is generated.</para>
                        </listitem>
                        <listitem><para>Then run the  <xref linkend="Loader_Generate_Nation_Script" /> and <xref linkend="Loader_Generate_Script" />  SQL functions make sure to use the name of your custom profile.  So for example to do the nation load using our new profile we would:</para>
-                                       <programlisting>SELECT Loader_Generate_Nation_Script('debbie')</programlisting>
+                                       <programlisting>SELECT Loader_Generate_Nation_Script('debbie');</programlisting>
                        </listitem>
                </orderedlist>
                <sect3 id="convert_tiger_geocoder_extension"><title>Converting a Tiger Geocoder Regular Install to Extension Model</title>
                        <para>If you installed the tiger geocoder without using the extension model, you can convert to the extension model as follows:</para>
                        <orderedlist>
                                <listitem><para>Follow instructions in <xref linkend="upgrade_tiger_geocoder" /> for the non-extension model upgrade.</para></listitem>
-                               <listitem><para>Connect to your data with psql or pgAdmin and run the following command:</para>
+                               <listitem><para>Connect to your database with psql or pgAdmin and run the following command:</para>
                                        <programlisting>CREATE EXTENSION postgis_tiger_geocoder FROM unpackaged;</programlisting>
                                </listitem>
                        </orderedlist>