Think I got them all...

docs/peewee/database.rst

@@ -481,7 +481,7 @@ See :ref:`framework-integration` for framework-specific examples.
    Peewee uses thread local storage to manage connection state, so this
    pattern can be used with multi-threaded or gevent applications.
 
-   Peewee's :ref:`asyncio integration <asyncio>` stores connection state in
+   Peewee's :ref:`asyncio integration <pwasyncio>` stores connection state in
    task-local storage, so the same pattern applies.
 
 Context managers
@@ -559,7 +559,7 @@ the Peewee :class:`Database` object safe to use with multiple threads. Each
 thread will have it's own connection, and as a result any given thread will
 only have a single connection open at a given time.
 
-Peewee's :ref:`asyncio integration <asyncio>` stores connection state in
+Peewee's :ref:`asyncio integration <pwasyncio>` stores connection state in
 task-local storage, so the same applies to async applications.
 
 DB-API Connection object

docs/peewee/db_tools.rst

@@ -179,7 +179,7 @@ returns it to the pool rather than actually disconnecting.
 .. include:: pool-snippet.rst
 
 .. note::
-   Applications using Peewee's :ref:`asyncio integration <asyncio>` do not need to
+   Applications using Peewee's :ref:`asyncio integration <pwasyncio>` do not need to
    use a special pooled database - the Async databases use a connection pool by
    default.
 

docs/peewee/example.rst

@@ -246,7 +246,7 @@ Flask provides connection setup/teardown hooks via decorators:
    Peewee uses thread local storage to manage connection state, so this
    pattern can be used with multi-threaded or gevent WSGI servers.
 
-   Peewee's :ref:`asyncio integration <asyncio>` stores connection state in
+   Peewee's :ref:`asyncio integration <pwasyncio>` stores connection state in
    task-local storage, so the same pattern applies.
 
 Making Queries