Apply suggestions from code review

Co-authored-by: ToriLindsay <[email protected]>

Author: nevikashah

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

@@ -1,5 +1,5 @@
 ---
-title: Deploy to Cloudflare Button
+title: Deploy to Cloudflare button
 pcx_content_type: concept
 sidebar:
   order: 5
@@ -8,12 +8,12 @@ description: Set Up a Deploy to Cloudflare Button
 ---
 import { Tabs, TabItem } from "~/components"
 
-# Using a Deploy to Cloudflare Button
-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.
+# Using a Deploy to Cloudflare button
+If you are 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.
 
 <insert deploy button here that links to example/>
 
-## What are Deploy to Cloudflare Buttons?
+## What are Deploy to Cloudflare buttons?
 Deploy to Cloudflare buttons simplify the deployment of a Workers application by enabling Cloudflare to:
 * **Clone a Git repository**: Cloudflare clones your source repository into the user's GitHub/GitLab account where they can continue development after deploying.
 * **Configure a project**: Your users can customize key details such as repository name, Worker name, and required resource names in a single setup page with customizations reflected in the newly created Git repository.
@@ -46,21 +46,21 @@ If you have already deployed your application using Workers Builds, you can gene
 
 Once you have your snippet, you can paste this wherever you would like your button to be displayed.
 
-## Automatic Resource Provisioning
+## 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
-* **Compute**: Durable Objects, Workers AI, Containers and Queues
+* **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 (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.
+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 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 (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.
+## 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 set up, 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`:
+**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`:
 
 ```json
 {
@@ -74,6 +74,6 @@ If no `deploy` script is specified, Cloudflare will preconfigure `npx wrangler d
 
 ## Not currently supported
 * **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)). If your application relies on dependencies outside its subdirectory, 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**: Deploy to Cloudflare buttons only support Workers applications today.
-* **Non gitHub.com/gitLab.com 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.
+* **Pages applications**: Currently, 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.

src/content/docs/workers/get-started/dashboard.mdx

@@ -22,10 +22,16 @@ Follow this guide to create a Workers application using [the Cloudflare dashboar
 
 To get started with a new Workers application:
 
-1. Click [Create](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create) in the Workers & Pages section of the dashboard
-2. You can select from the gallery of existing templates or choose to connect to GitHub or GitLab, import an existing repository on your own account or let Cloudflare clone and bootstrap a public repository containing a Workers application. 
-3. Once you've connected to your chosen Git provider, configure your project and click `Deploy`. 
-4. Cloudflare will kick off a build and deployment. Once deployed, preview your Worker at its provided `workers.dev` subdomain. 
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. Go to **Workers & Pages**.
+3. Select **[Create](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create)** and then:
+* Select from the gallery of existing templates.
+* Create a new, blank Worker by selecting **Hello world**.
+* [Import an existing GitHub or GitLab repository](/workers/ci-cd/builds/git-integration/index), by selecting **Git account** under **Import a repository**.
+* Let Cloudflare clone and bootstrap a public repository containing a Workers application. 
+4. Review the provided code and select `Deploy`. 
+
+Cloudflare will kick off a build and deployment. Once deployed, you can preview your Worker at its provided `workers.dev` subdomain. 
 
 ## Development
 Applications started in the dashboard are set up with Git to help kickstart your development workflow. To continue developing on your repository, you can run: