Update src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx

Co-authored-by: lrapoport-cf <[email protected]>

Author: penalosa

src/content/changelog/workers/2025-10-24-automatic-resource-provisioning.mdx

@@ -10,7 +10,7 @@ import { Render, TypeScriptExample, WranglerConfig } from "~/components";
 
 Previously, if you wanted to develop or deploy a worker with attached resources, you'd have to first manually create the desired resources. Now, if your Wrangler configuration file includes a KV namespace, D1 database, or R2 bucket that does not yet exist on your account, you can develop locally and deploy your application seamlessly, without having to run additional commands.
 
-This is still an experimental feature, but we're turning it on by default to make it easier for people to test it and try it out. You can disable the feature using the `--no-x-provision` flag. It currently works for KV, R2, and D1 bindings.
+Automatic provisioning is still experimental, but we're turning it on by default to make it easier to try out and test. It currently works for KV, R2, and D1 bindings. You can disable the feature using the `--no-x-provision` flag. 
 
 To use this feature, update to [email protected] and add bindings to your config file _without_ resource IDs e.g.: