Update src/content/docs/workers/deploy-buttons.mdx

Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>

Author: ToriLindsay

src/content/docs/workers/deploy-buttons.mdx

@@ -50,7 +50,7 @@ If your Worker application requires Cloudflare resources, they will be automatic
 * **Storage**: KV namespaces, D1 databases, R2 buckets, Hyperdrive and Vectorize
 * **Compute**: Durable Objects, Workers AI, Containers and Queues
 
-Cloudflare will read the Wrangler configuration file of your source repo to determine resource requirements for your application. During deployment, Cloudflare will provision any necessary resources and update the Wrangler configuration where applicable for newly created resources (e.g. database IDs, namespace IDs). To ensure successful deployment, please make sure your source repository includes default values for resource names, resource IDs and any other properties for each binding. 
+Cloudflare will read the Wrangler configuration file of your source repo to determine resource requirements for your application. During deployment, Cloudflare will provision any necessary resources and update the Wrangler configuration where applicable for newly created resources (for example, database IDs, namespace IDs). To ensure successful deployment, please make sure your source repository includes default values for resource names, resource IDs and any other properties for each binding.
 
 ## Best Practices 
 **Configuring Build/Deploy commands**: If you are using custom  `build` and `deploy` scripts in your package.json (e.g. if using a full stack framework or running D1 migrations), Cloudfare will automatically detect and pre-populate the build and deploy fields. Users can choose to modify or accept the custom commands during deployment configuration.