updates based on feedback

Author: nevikashah

src/content/docs/workers/community/index.mdx

@@ -9,7 +9,7 @@ description: Set up a Deploy to Cloudflare button
 
 import { Tabs, TabItem } from "@astrojs/starlight/components";
 
-If you're building a Workers application and would like to share it with other developers, you can embed a Deploy to Cloudflare button in your README, blog post, or documentation to enable others to quickly bootstrap your application on their own Cloudflare account. Deploy to Cloudflare buttons eliminate the need for complex setup, allowing developers to get started with your public GitHub or GitLab repository in just a few clicks. 
+If you're building a Workers application and would like to share it with other developers, you can embed a Deploy to Cloudflare button in your README, blog post, or documentation to enable others to quickly deploy your application on their own Cloudflare account. Deploy to Cloudflare buttons eliminate the need for complex setup, allowing developers to get started with your public GitHub or GitLab repository in just a few clicks. 
 
 [![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/templates/tree/staging/saas-admin-template)
 
@@ -34,14 +34,14 @@ Deploy to Cloudflare buttons can be embedded anywhere developers might want to l
 </TabItem> 
 <TabItem label="HTML">
 ```html
-<a href="https://deploy.workers.cloudflare.com/?url=<your git repo URL>"><img src="https://deploy.workers.cloudflare.com/button" alt="Deploy to Cloudflare"/></a>
+<a href="https://deploy.workers.cloudflare.com/?url=<YOUR_REPO_URL>"><img src="https://deploy.workers.cloudflare.com/button" alt="Deploy to Cloudflare"/></a>
 ```
 
 </TabItem> 
 
 <TabItem label="URL">
 ```
-https://deploy.workers.cloudflare.com/?url=<your git repo link>
+https://deploy.workers.cloudflare.com/?url=<YOUR_REPO_URL>
 ```
 </TabItem> 
 </Tabs>
@@ -54,16 +54,14 @@ Once you have your snippet, you can paste this wherever you would like your butt
 
 ## Automatic Resource provisioning 
 If your Worker application requires Cloudflare resources, they will be automatically provisioned as part of the deployment. Currently, supported resources include:
-* **Storage**: KV namespaces, D1 databases, R2 buckets, Hyperdrive, and Vectorize databases
-* **Compute**: Durable Objects, Workers AI, Containers, and Queues
+* **Storage**: [KV namespaces](/kv/), [D1 databases](/d1/), [R2 buckets](/r2/), [Hyperdrive](/hyperdrive/), and [Vectorize databases](/vectorize/)
+* **Compute**: [Durable Objects](/durable-objects/), [Workers AI](/workers-ai/), and [Queues](/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 and 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 (for example, 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. 
 
-<insert screenshot of build and deploy command UI/>
-
 If no `deploy` script is specified, Cloudflare will preconfigure `npx wrangler deploy` by default. If no `build` script is specified, Cloudflare will leave this field blank. 
 
 **Running D1 Migrations**: If you would like to run migrations as part of your setup, you can specify this in your `package.json` by running your migrations as part of your `deploy` script. The migration command should reference the binding name rather than the database name to ensure migrations are successful when users specify a database name that is different from that of your source repository. The following is an example of how you can set up the scripts section of your `package.json`:
@@ -81,8 +79,8 @@ If no `deploy` script is specified, Cloudflare will preconfigure `npx wrangler d
 ## Limitations
 
 * **Monorepos**: Cloudflare does not fully support monorepos
-  * Unless your application is completely isolated within a subdirectory and has no dependencies outside of that subdirectory (for example, [a monorepo of example applications](https://github.com/cloudflare/templates)), the build will fail. 
-  * Additionally, if your monorepo contains multiple Workers applications, they will not be deployed together. You must configure a separate Deploy to Cloudflare button for each application. The user will manually create a distinct Workers application for each subdirectory.
-* **Pages applications**: Currently, Deploy to Cloudflare buttons only support Workers applications today.
+  * If your repository URL contains a subdirectory, your application must be fully isolated within that subdirectory, including any dependencies. Otherwise, the build will fail. Cloudflare treats this subdirectory as the root of the new repository created as part of the deploy process. 
+  * Additionally, if you have a monorepo that contains multiple Workers applications, they will not be deployed together. You must configure a separate Deploy to Cloudflare button for each application. The user will manually create a distinct Workers application for each subdirectory.
+* **Pages applications**: Deploy to Cloudflare buttons only support Workers applications.
 * **Non-GitHub/GitLab repositories**: Source repositories from anything other than github.com and gitlab.com are not supported. Self-hosted versions of GitHub and GitLab are also not supported. 
-* **Private repositories**: Repositories must be public in order for others to successfully use your Deploy to Cloudflare button. 
+* **Private repositories**: Repositories must be public in order for others to successfully use your Deploy to Cloudflare button.