warnings should be more prominent. Move extension warning up a bit. correct misspelling

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

diff --git a/doc/html/style.css b/doc/html/style.css
index 1c933da6276e15ba298129bee6026d6dfc0a68f1..76c4857d58cac2157423f40771cd181c5b9d1d03 100644 (file)
--- a/doc/html/style.css
+++ b/doc/html/style.css
@@ -30,6 +30,7 @@ pre, .literallayout { border-right-width: 0px; border-left-width: 0px; border-bo
 .note { border-left-width: 0px; border-bottom-width: 2px; border-right-width: 0px; border-top-width: 2px; width: 80%; border-color: #a2d545; border-style: solid; font-size: 11px; margin-bottom: 10px; margin-top: 10px; overflow: auto; padding: 10px; background: #e4f7dd; -moz-border-radius: 2px; -webkit-border-radius: 2px;}
 /* code { border-right-style: solid; border-right-color: #79791a; border-left-color: #79791b; border-left-style: solid; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px; border-top-width: 0px; padding-left: 3px; padding-bottom: 1px; padding-right: 3px; padding-top: 1px; font-family: "Courier New", Courier, Monaco, monospace; color: #fefff7; background: #9b9e96; -moz-border-radius: 2px; -webkit-border-radius: 2px;} */
 .programlisting {font-family: "Courier New", Courier, Monaco, monospace;}
+.warning { border-left-width: 0px; border-bottom-width: 2px; border-right-width: 0px; border-top-width: 2px; width: 80%; border-color: #a2d545; border-style: solid; font-size: 11px; margin-bottom: 10px; margin-top: 10px; overflow: auto; padding: 10px; background: #FFBF00; -moz-border-radius: 2px; -webkit-border-radius: 2px;}
 
 /* 4. Docbook Specifics
 ----------------------------------------------------- */

diff --git a/doc/installation.xml b/doc/installation.xml
index bf630dd58523521ac3f52adda372e5100a1b973d..cb6e878b3b12a3c29c3a2970a5bbd0e9f82314b0 100644 (file)
--- a/doc/installation.xml
+++ b/doc/installation.xml
@@ -605,16 +605,17 @@ in the <varname>extensions</varname> section of the database browser tree and wi
 <programlisting>CREATE EXTENSION postgis;
 CREATE EXTENSION postgis_topology;</programlisting>
 
+<warning><para>Extension tables <varname>spatial_ref_sys</varname>, <varname>layer</varname>, <varname>topology</varname> can not be explicitly backed up.  They can only 
+be backed up when the respective <varname>postgis</varname> or <varname>postgis_topology</varname> extension is backed up, which only seems to happen when you backup the whole database. 
+As of PostGIS 2.0.1, only srid records not packaged with PostGIS are backed up when the database is backed up so don't go around changing srids we package and expect your changes to be there. Put in a ticket if you find an issue.  The structures of extension tables are never backed up since they are created with <code>CREATE EXTENSION</code>
+and assumed to be the same for a given version of an extension. These behaviors are built into the current PostgreSQL extension model, so nothing we can do about it.</para></warning>
+
 <para>If you installed &last_release_version;, without using our wonderful extension system, you can change it to be extension based by first upgrading to the latest micro version running the upgrade scripts: <filename>postgis_upgrade_20_minor.sql</filename>,<filename>raster_upgrade_20_minor.sql</filename>,<filename>topology_upgrade_20_minor.sql</filename>.</para>
 <para>If you installed postgis without raster support, you'll need to install raster support first (using the full <filename>rtpostgis.sql</filename></para>
-<para>Then you can run teh below commands to package the functions in their respective extension.</para>
+<para>Then you can run the below commands to package the functions in their respective extension.</para>
 <programlisting>CREATE EXTENSION postgis FROM unpackaged;
 CREATE EXTENSION postgis_topology FROM unpackaged;</programlisting>
 
-<warning><para>Extension tables <varname>spatial_ref_sys</varname>, <varname>layer</varname>, <varname>topology</varname> can not be explicitly backed up.  They can only 
-be backed up when the respective <varname>postgis</varname> or <varname>postgis_topology</varname> extension is backed up, which only seems to happen when you backup the whole database. 
-As of PostGIS 2.0.1, only srid records not packaged with PostGIS are backed up when the database is backed up so don't go around changing srids we package and expect your changes to be there. Put in a ticket if you find an issue.  The structures of extension tables are never backed up since they are created with <code>CREATE EXTENSION</code>
-and assumed to be the same for a given version of an extension. These behaviors are built into the current PostgreSQL extension model, so nothing we can do about it.</para></warning>
        </sect2>