more typo fixing

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

diff --git a/doc/reference.xml b/doc/reference.xml
index 875ae4c097b554fe3049e41854e4cbbf58c72061..35b2ff38fcd6c73f37a13029f0bd5cc3e3719728 100644 (file)
--- a/doc/reference.xml
+++ b/doc/reference.xml
@@ -12074,11 +12074,10 @@ SELECT ST_Buffer(ST_GeomFromText('POINT(50 50)'), 20) As smallc,
                                </para>
                                <note><para>Geography: For geography this is really a thin wrapper around the geometry implementation. It first determines the best SRID that
                                        fits the bounding box of the geography object (favoring UTM and falling back on mercator in worst case scenario) and then buffers in that planar spatial ref and retransforms back to WGS84 geography.</para></note>
-                                                       <para><inlinegraphic fileref="images/warning.png" />
-                       For geography this may not behave as expected if object is sufficiently large that it falls between two UTM zones and crosses the dateline
-               </para>
+                       <para><inlinegraphic fileref="images/warning.png" />
+                       For geography this may not behave as expected if object is sufficiently large that it falls between two UTM zones or crosses the dateline</para>
                                <para>Availability: 1.5 - ST_Buffer was enhanced to support different endcaps and join types. These are useful for example to convert road linestrings
-                                       into polygon roads with flat or square edges instead of rounded edges. Thin wrapper for geography was added. - requires GEOS &gt;= 3.2 to take advantage of advanced functionality.
+                                       into polygon roads with flat or square edges instead of rounded edges. Thin wrapper for geography was added. - requires GEOS &gt;= 3.2 to take advantage of advanced geometry functionality.
                                </para>
                                <para>
 The optional third parameter (currently only applies to geometry) can either specify number of segments used to approximate a quarter circle (integer case, defaults to 8) or a list of blank-separated key=value pairs (string case) to tweak operations as follows: