Merge pull request #1252 from hiddewie/patch-1

Fix link for performance analysis for adding --multi-geometry and --hstore

Author: pnorman

docs/analysis.md

@@ -14,7 +14,7 @@ To start with, we'll download the data for the region as an [extract from Geofab
 
 `--multi-geometry` (`-G`) is necessary for most analysis as it prevents
 MULTIPOLYGONs from being split into multiple POLYGONs, a step that is
-normally used to [increase rendering speed](http://paulnorman.ca/blog/2014/03/osm2pgsql-multipolygons)
+normally used to [increase rendering speed](http://www.paulnorman.ca/blog/2014/03/osm2pgsql-multipolygons/)
 but increases the complexity of analysis SQL.
 
 Loading should take about 10 minutes, depending on computer speed. Once this

docs/usage.md

@@ -129,7 +129,7 @@ should give the same rows as no hstore, just with the additional hstore column.
 
 Hstore is used to give more flexibility in using additional tags without
 reimporting the database, at the cost of a
-[less speed and more space.](http://paulnorman.ca/blog/2014/03/osm2pgsql-and-hstore/)
+[less speed and more space.](http://www.paulnorman.ca/blog/2014/03/osm2pgsql-and-hstore/)
 
 ## Projection options
 
@@ -142,7 +142,7 @@ reimporting the database, at the cost of a
 
 * `--multi-geometry` skips an optimization for rendering where PostGIS
   MULTIPOLYGONs are split into multiple POLYGONs. `--multi-geometry` can be
-  used to [avoid some labeling issues at the cost of speed](http://paulnorman.ca/blog/2014/03/osm2pgsql-multipolygons/).
+  used to [avoid some labeling issues at the cost of speed](http://www.paulnorman.ca/blog/2014/03/osm2pgsql-multipolygons/).
   It is also typically required for [analysis](analysis.md).
 
 * `--keep-coastlines` disables a hard-coded rule that would otherwise