try to fix illegal abstract (with note (instead of para)) and listltiem with no para

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

diff --git a/doc/extras_tigergeocoder.xml b/doc/extras_tigergeocoder.xml
index 282fc6364663c79615ce0c58d8b4cf1f9df9fc4e..d2e8029e8dbb2b7136118c273f3bf970d854588c 100644 (file)
--- a/doc/extras_tigergeocoder.xml
+++ b/doc/extras_tigergeocoder.xml
@@ -12,10 +12,11 @@
             <para>All the geocode functions only reference the base tables, so there is no requirement that the data schema be called <varname>tiger_data</varname> or that data can't be further partitioned into other schemas -- e.g a different schema
             for each state, as long as all the tables inherit from the tables in the <varname>tiger</varname> schema.</para>
             
+       
             <para>For instructions on how enable the extension in your database and also to load data using it, refer to Refer to <xref linkend="install_tiger_geocoder_extension" />.</para>
             
         
-              <note><para>
+             <para> <note><para>
 If you are using tiger geocoder (tiger_2010),
 you can upgrade the scripts using the accompanying upgrade_geocoder.bat
 / .sh scripts in extras/tiger.  One major change between <varname>tiger_2010</varname> and <varname>tiger_2011+</varname> is that the county and <varname>county</varname> and <varname>state</varname> tables are no longer broken out by state.    If you have data from tiger_2010 and want replace with tiger_2015 refer to <xref linkend="upgrade_tiger_geocoder" />
@@ -24,6 +25,7 @@ you can upgrade the scripts using the accompanying upgrade_geocoder.bat
               <note>
               <para>New in PostGIS 2.2.0 release is support for Tiger 2015 data and inclusion of Address Standardizer as part of PostGIS.</para>
               <para>New in PostGIS 2.1.0 release is ability to install tiger geocoder with PostgreSQL extension model if you are running PostgreSQL 9.1+. Refer to <xref linkend="install_tiger_geocoder_extension" /> for details.</para></note>
+              </para>
              
               <para>The <xref linkend="Pagc_Normalize_Address" /> function as a drop in replacement for in-built <xref linkend="Normalize_Address" />. Refer to <xref linkend="installing_pagc_address_standardizer" /> for compile and installation instructions.</para> 
         
@@ -37,7 +39,7 @@ you can upgrade the scripts using the accompanying upgrade_geocoder.bat
             <para>It should be robust enough to function properly despite formatting and spelling errors.</para>
             <para>It should be extensible enough to be used with future data updates, or alternate data sources with a minimum of coding changes.</para>
             <para>
-        <note><para>The <varname>tiger</varname> schema must be added to the database search path for the functions to work properly.</para></note>
+                <note><para>The <varname>tiger</varname> schema must be added to the database search path for the functions to work properly.</para></note>
             </para>
         </abstract>
      </sect1info>

diff --git a/doc/installation.xml b/doc/installation.xml
index e596420b728dcc57d9542e88d01dd4e7d97f84bc..9b3880aab5d3cabf76f3b4bf9e8bcce0ee0a61d9 100644 (file)
--- a/doc/installation.xml
+++ b/doc/installation.xml
@@ -1564,10 +1564,10 @@ SELECT 'debbie', declare_sect, pgbin, wget, unzip_command, psql, path_sep,
                        
                                <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>Create a folder called <filename>gisdata</filename> on root of server or your local pc if you have a fast network connection to the server. This folder is
-where the tiger files will be downloaded to and processed.  If you are not happy with having the folder on the root of the server, or simply want to change to a different folder for staging, then edit the field <varname>staging_fold</varname> in the <varname>tiger.loader_variables</varname> table.</listitem>
-            <listitem>Create a folder called temp in the <filename>gisdata</filename> folder or whereever you designated the <varname>staging_fold</varname> to be.  This will be
-the folder where the loader extracts the downloaded tiger data.</listitem>
+                       <listitem><para>Create a folder called <filename>gisdata</filename> on root of server or your local pc if you have a fast network connection to the server. This folder is
+where the tiger files will be downloaded to and processed.  If you are not happy with having the folder on the root of the server, or simply want to change to a different folder for staging, then edit the field <varname>staging_fold</varname> in the <varname>tiger.loader_variables</varname> table.</para></listitem>
+            <listitem><para>Create a folder called temp in the <filename>gisdata</filename> folder or whereever you designated the <varname>staging_fold</varname> to be.  This will be
+the folder where the loader extracts the downloaded tiger data.</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 and copy the scripts to a .sh or .bat file.  So for example to do the nation load and one state using our new profile we would:</para>
                                        <programlisting>SELECT Loader_Generate_Nation_Script('debbie');</programlisting>
                                        <programlisting>SELECT Loader_Generate_Script(ARRAY['MA'], 'debbie');</programlisting>