Refs #36663, #36739 -- Added release note for running checks against all databases.

2 files changed, 10 insertions, 4 deletions

diff --git a/docs/ref/checks.txt b/docs/ref/checks.txt
index 966bca23b2..22ebfed2ca 100644
--- a/docs/ref/checks.txt
+++ b/docs/ref/checks.txt
@@ -79,10 +79,10 @@ Django's system checks are organized using the following tags:
 * ``compatibility``: Flags potential problems with version upgrades.
 * ``commands``: Checks custom management commands related configuration.
 * ``database``: Checks database-related configuration issues. Database checks
-  are not run by default because they do more than static code analysis as
-  regular checks do. They are only run by the :djadmin:`migrate` command or if
-  you specify configured database aliases using the ``--database`` option when
-  calling the :djadmin:`check` command.
+  are not run by default because they do more than only static code analysis as
+  most regular checks do. They are only run by the :djadmin:`migrate` command
+  or if you specify configured database aliases using the ``--database`` option
+  when calling the :djadmin:`check` command.
 * ``files``: Checks files related configuration.
 * ``models``: Checks of model, field, and manager definitions.
 * ``security``: Checks security related configuration.
diff --git a/docs/releases/6.1.txt b/docs/releases/6.1.txt
index 425419529b..f3338f8933 100644
--- a/docs/releases/6.1.txt
+++ b/docs/releases/6.1.txt
@@ -341,6 +341,12 @@ backends.
   instead of the JSON ``null`` primitive. This matches the behavior of a
   standalone :class:`~django.db.models.JSONField` when storing ``None`` values.
 
+System checks
+-------------
+
+* The :djadmin:`check` management command now supplies all ``databases`` if not
+  specified. Callers should be prepared for databases to be accessed.
+
 Dropped support for PostgreSQL 14
 ---------------------------------