Merge branch 'anni/wb-checkruns' of https://github.com/cloudflare/cloudflare-docs into anni/wb-checkruns

Author: aninibread

src/content/docs/pages/configuration/git-integration/index.mdx

@@ -70,7 +70,7 @@ If your git integration is experiencing issues, you may find the following banne
 
 #### `This repository is being used for a Cloudflare Pages project on a different Cloudflare account.`
 
-Using the same Github/Gitlab repository across separate Cloudflare accounts is disallowed. To use the repository for a Pages project in that Cloudflare account, you should delete any Pages projects using the repository in other Cloudflare accounts.
+Using the same GitHub/GitLab repository across separate Cloudflare accounts is disallowed. To use the repository for a Pages project in that Cloudflare account, you should delete any Pages projects using the repository in other Cloudflare accounts.
 
 ### Deployments
 

src/content/docs/workers/ci-cd/builds/advanced-setups.mdx

@@ -22,7 +22,7 @@ When a new commit is made to the monorepo, a new build and deploy will trigger f
 
 In the example `ecommerce-monorepo`, a Workers project should be created for `product-service`, `order-service`, and `notification-service`.
 
-A Git connection to `ecommerce-monorepo` should be added in all of the Workers projects. If you are using a monorepo tool (e.g. [Turborepo](https://turbo.build/)), you can configure a different deploy command for each Worker (e.g. `turbo deploy -F product-service`).
+A Git connection to `ecommerce-monorepo` should be added in all of the Workers projects. If you are using a monorepo tool, such as [Turborepo](https://turbo.build/), you can configure a different deploy command for each Worker, for example, `turbo deploy -F product-service`.
 
 Set the root directory of each Worker to where its wrangler.toml is located. For example, for `product-service`, the root directory should be `/workers/product-service/`. Optionally, you can add [build watch paths](/workers/ci-cd/builds/build-watch-paths/) to optimize your builds.
 

src/content/docs/workers/ci-cd/builds/index.mdx

@@ -39,7 +39,7 @@ If the build is successful, you can also view the build details by selecting **V
 
 :::note[Builds, Versions, Deployments]
 
-If a build succeeds, it is uploaded as a version. If the build is configured to deploy (e.g. with `wrangler deploy` set as the deploy command), the uploaded version will be automatically promoted to the Active Deployment.
+If a build succeeds, it is uploaded as a version. If the build is configured to deploy (for example, with `wrangler deploy` set as the deploy command), the uploaded version will be automatically promoted to the Active Deployment.
 
 :::