A variety of documentation improvements and cleanup.

Author: rustprooflabs

docs/src/SUMMARY.md

@@ -20,7 +20,7 @@
     - [pgRouting 4](./routing-4.md)
 - [Processing Time](./performance.md)
 
-# Production usages
+# Production Use
 
 - [Postgres Permissions](./postgres-permissions.md)
 - [Using External Postgres Connection](./postgres-external.md)

docs/src/quick-start.md

@@ -235,11 +235,15 @@ From the perspective of database design, the `osm.unitable` option is the **wors
 This table violates all sorts of best practices established in this project
 by shoving all features into a single unstructured table.
 
-> This style included in PgOSM Flex is intended to be used for troubleshooting and quality control.  It is not intended to be used for real production workloads! This table is helpful for exploring the full data set when you don't really know what you are looking for, but you know **where** you are looking.
+The Unitable data is loaded with the `everything` layerset.
+Of course, you can create your own customized layerset including this style
+if needed.
 
-Unitable is loaded with the `everything` layerset.  Feel free to create your own
-customized layerset if needed.
 
+> The `osm.unitable` table is intended to be used for troubleshooting and
+> quality control.  It is not intended to be used for production workloads!
+> This table is most helpful for exploring the full data set when you don't
+> really know what you are looking for, but you know **where** you are looking.
 
 
 ```bash

docs/src/readme.md

@@ -1,4 +1,4 @@
-# PgOSM Flex
+# About PgOSM Flex
 
 PgOSM Flex ([GitHub](https://github.com/rustprooflabs/pgosm-flex))
 provides high quality OpenStreetMap datasets in PostGIS using the
@@ -33,7 +33,7 @@ A few decisions made in this project:
 * Defaults to same units as OpenStreetMap (e.g. km/hr, meters)
 * Data not included in a dedicated column is available from `osm.tags.tags` (`JSONB`)
 * Points, Lines, and Polygons are not mixed in a single table
-* Tracks latest Postgres, PostGIS, and osm2pgsql versions
+* Tracks latest Postgres, PostGIS, osm2pgsql, and pgRouting versions
 
 This project's approach is to do as much processing in the Lua styles
 passed along to osm2pgsql, with post-processing steps creating indexes,
@@ -72,6 +72,8 @@ package used to determine the best osm2pgsql command assumes fast SSDs.
 
 ## RustProof Labs project
 
-PgOSM Flex is a RustProof Labs project developed and maintained by Ryan Lambert.
+PgOSM Flex is a RustProof Labs project developed and maintained
+by Ryan Lambert and
+[contributors](https://github.com/rustprooflabs/pgosm-flex/graphs/contributors).
 See the [RustProof Labs blog](https://blog.rustprooflabs.com/category/pgosm-flex)
 for more resources and examples of using PgOSM Flex.

docs/src/routing-3.md

@@ -1,6 +1,21 @@
-# Routing with PgRouting 3
+# Routing with pgRouting 3
 
-> If you are using a pgRouting 4.0 or later see [Routing with pgRouting 4](./routing-4.md).
+If you are using a pgRouting 4.0 or later see [Routing with pgRouting 4](./routing-4.md).
+New development in PgOSM Flex will focus support on pgRouting 4.0 support.
+[PgOSM Flex 1.1.2](https://github.com/rustprooflabs/pgosm-flex/releases/tag/1.1.2)
+includes a simplified and higher performance implementation of the routing
+data preparation.
+
+
+> ⚠️ This page will remain in the PgOSM documentation through at least 2026 to ensure
+> continuity for a transition to pgRouting 4.0.
+> There will not be improvements made to these legacy instructions.
+
+Create the `pgRouting` extension.
+
+```sql
+CREATE EXTENSION IF NOT EXISTS pgrouting;
+```
 
 
 ## Clean the data

docs/src/routing-4.md

@@ -1,4 +1,4 @@
-# Routing with PgRouting 4
+# Routing with pgRouting 4
 
 > If you are using a pgRouting prior to 4.0 see [Routing with pgRouting 3](./routing-3.md).