The tagline says "ODX writes the other twenty lines"

README.md

@@ -1,6 +1,6 @@
 # Open.Database.Extensions (ODX)
 
-![Open.Database.Extensions: You write the SQL. The library writes the other twenty lines.](https://raw.githubusercontent.com/Open-NET-Libraries/Open.Database.Extensions/master/docsite/images/hero-core.svg)
+![Open.Database.Extensions: You write the SQL. ODX writes the other twenty lines.](https://raw.githubusercontent.com/Open-NET-Libraries/Open.Database.Extensions/master/docsite/images/hero-core.svg)
 
 [![NuGet](https://img.shields.io/nuget/vpre/Open.Database.Extensions.Core.svg?style=flat)](https://www.nuget.org/packages/Open.Database.Extensions.Core/)
 [![Docs](https://github.com/Open-NET-Libraries/Open.Database.Extensions/actions/workflows/docs.yml/badge.svg)](https://github.com/Open-NET-Libraries/Open.Database.Extensions/actions/workflows/docs.yml)

Source/Channel/README.md

@@ -1,6 +1,6 @@
 # Open.Database.Extensions.Channel
 
-![Open.Database.Extensions.Channel: You write the SQL. The library writes the other twenty lines.](https://raw.githubusercontent.com/Open-NET-Libraries/Open.Database.Extensions/master/docsite/images/hero-channel.svg)
+![Open.Database.Extensions.Channel: You write the SQL. ODX writes the other twenty lines.](https://raw.githubusercontent.com/Open-NET-Libraries/Open.Database.Extensions/master/docsite/images/hero-channel.svg)
 
 Read query results straight into a `System.Threading.Channels` channel instead of a collection. `ToChannel<T>()` returns a `ChannelReader<T>` immediately; rows are produced in the background, and the channel completes when every row has been written (or completes with the exception if reading fails). **Use it when** another task consumes the rows while they are still being read. It includes [Open.Database.Extensions.Core](https://www.nuget.org/packages/Open.Database.Extensions.Core/), and rows are mapped the same way as `Map<T>()`.
 

Source/Core/README.md

@@ -1,6 +1,6 @@
 # Open.Database.Extensions.Core
 
-![Open.Database.Extensions.Core: You write the SQL. The library writes the other twenty lines.](https://raw.githubusercontent.com/Open-NET-Libraries/Open.Database.Extensions/master/docsite/images/hero-core.svg)
+![Open.Database.Extensions.Core: You write the SQL. ODX writes the other twenty lines.](https://raw.githubusercontent.com/Open-NET-Libraries/Open.Database.Extensions/master/docsite/images/hero-core.svg)
 
 Core is the foundation of Open.Database.Extensions: ADO.NET extension methods with best-practice defaults, expressive commands that open, run and dispose their own connection, and `Map<T>()` to turn rows into objects. It has no database dependency of its own. **Use it for any ADO.NET database;** most applications need only this package.
 

Source/Dataflow/README.md

@@ -1,6 +1,6 @@
 # Open.Database.Extensions.Dataflow
 
-![Open.Database.Extensions.Dataflow: You write the SQL. The library writes the other twenty lines.](https://raw.githubusercontent.com/Open-NET-Libraries/Open.Database.Extensions/master/docsite/images/hero-dataflow.svg)
+![Open.Database.Extensions.Dataflow: You write the SQL. ODX writes the other twenty lines.](https://raw.githubusercontent.com/Open-NET-Libraries/Open.Database.Extensions/master/docsite/images/hero-dataflow.svg)
 
 Read query results straight into a TPL Dataflow pipeline. `ToTargetBlock<T>()` posts each row to a block, and `AsSourceBlock<T>()` exposes the results as a source block. **Use it when** your processing is already built from dataflow blocks. It includes [Open.Database.Extensions.Core](https://www.nuget.org/packages/Open.Database.Extensions.Core/), and rows are mapped the same way as `Map<T>()`.
 

Source/MSSqlClient/README.md

@@ -1,6 +1,6 @@
 # Open.Database.Extensions.MSSqlClient
 
-![Open.Database.Extensions.MSSqlClient: You write the SQL. The library writes the other twenty lines.](https://raw.githubusercontent.com/Open-NET-Libraries/Open.Database.Extensions/master/docsite/images/hero-mssqlclient.svg)
+![Open.Database.Extensions.MSSqlClient: You write the SQL. ODX writes the other twenty lines.](https://raw.githubusercontent.com/Open-NET-Libraries/Open.Database.Extensions/master/docsite/images/hero-mssqlclient.svg)
 
 SQL Server for Open.Database.Extensions: `SqlConnectionFactory`, SQL-specific commands, and stored procedures on `Microsoft.Data.SqlClient`. **Use it when** your database is SQL Server. It includes [Open.Database.Extensions.Core](https://www.nuget.org/packages/Open.Database.Extensions.Core/) and the `Microsoft.Data.SqlClient` provider, so there is nothing else to install.
 

Source/SqlClient/README.md

@@ -1,6 +1,6 @@
 # Open.Database.Extensions.SqlClient
 
-![Open.Database.Extensions.SqlClient: You write the SQL. The library writes the other twenty lines.](https://raw.githubusercontent.com/Open-NET-Libraries/Open.Database.Extensions/master/docsite/images/hero-sqlclient.svg)
+![Open.Database.Extensions.SqlClient: You write the SQL. ODX writes the other twenty lines.](https://raw.githubusercontent.com/Open-NET-Libraries/Open.Database.Extensions/master/docsite/images/hero-sqlclient.svg)
 
 **This package is deprecated in favor of [Open.Database.Extensions.MSSqlClient](https://www.nuget.org/packages/Open.Database.Extensions.MSSqlClient/)**, which uses the actively maintained `Microsoft.Data.SqlClient` and has the same API. Use this package only if your project still needs the older `System.Data.SqlClient`; otherwise install MSSqlClient. It includes [Open.Database.Extensions.Core](https://www.nuget.org/packages/Open.Database.Extensions.Core/).
 

docsite/articles/channels-and-dataflow.md

@@ -11,7 +11,7 @@ They work on expressive commands, on `IDbCommand` and on readers, and map rows t
 
 ## Channels
 
-![Open.Database.Extensions.Channel: You write the SQL. The library writes the other twenty lines.](../images/hero-channel.svg)
+![Open.Database.Extensions.Channel: You write the SQL. ODX writes the other twenty lines.](../images/hero-channel.svg)
 
 `ToChannel<T>` returns a `ChannelReader<T>` immediately. The channel is completed when every row has been written, or completed with the exception if reading fails:
 
@@ -21,7 +21,7 @@ The overloads that take a `ChannelWriter` as the target return the number of row
 
 ## Dataflow
 
-![Open.Database.Extensions.Dataflow: You write the SQL. The library writes the other twenty lines.](../images/hero-dataflow.svg)
+![Open.Database.Extensions.Dataflow: You write the SQL. ODX writes the other twenty lines.](../images/hero-dataflow.svg)
 
 `ToTargetBlock<T>` posts each row to a block. The `complete` argument controls the target: with `true`, the block is completed after every row has been delivered and the reader has been released, or faulted with the exception if reading or mapping failed. With `false`, the block is left open and is never completed or faulted by the call. The number `ToTargetBlock<T>` returns counts the rows read and handed to the internal buffer; delivery to the target can still be in progress.
 

docsite/articles/getting-started.md

@@ -91,7 +91,7 @@ What is different:
 
 ## With SQL Server
 
-![Open.Database.Extensions.MSSqlClient: You write the SQL. The library writes the other twenty lines.](../images/hero-mssqlclient.svg)
+![Open.Database.Extensions.MSSqlClient: You write the SQL. ODX writes the other twenty lines.](../images/hero-mssqlclient.svg)
 
 `Open.Database.Extensions.MSSqlClient` provides `SqlConnectionFactory`. Everything above works the same way, and stored procedures are one call away: