Update the description of when SQLite might make sense as the configured database [ci skip] (rails#52639)

* Update the description of when SQLite might make sense as the configured database

* Update configuring.md

Co-authored-by: Rafael Mendonça França <[email protected]>

Author: fractaledmind

guides/source/configuring.md

@@ -3335,7 +3335,7 @@ Now the behavior is clear, that we are only using the connection information in
 
 #### Configuring an SQLite3 Database
 
-Rails comes with built-in support for [SQLite3](http://www.sqlite.org), which is a lightweight serverless database application. While a busy production environment may overload SQLite, it works well for development and testing. Rails defaults to using an SQLite database when creating a new project, but you can always change it later.
+Rails comes with built-in support for [SQLite3](http://www.sqlite.org), which is a lightweight serverless database application. While Rails better configures SQLite for production workloads, a busy production environment may overload SQLite. Rails defaults to using an SQLite database when creating a new project, but you can always change it later.
 
 Here's the section of the default configuration file (`config/database.yml`) with connection information for the development environment: