small pages fixes

Author: aninibread

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

@@ -23,6 +23,10 @@ Every time you open a new pull request on your GitHub repository, Cloudflare Pag
 
 ![GitHub Preview Urls](~/assets/images/pages/configuration/ghpreviewurls.png)
 
+:::note
+Commits/PRs created from forked repositories will not create a preview.
+:::
+
 ### Skipping a build via a commit message
 
 Without any configuration required, you can choose to skip a deployment on an adhoc basis. By adding the `[CI Skip]`, `[CI-Skip]`, `[Skip CI]`, `[Skip-CI]`, or `[CF-Pages-Skip]` flag as a prefix in your commit message, and Pages will omit that deployment. The prefixes are not case sensitive.
@@ -53,7 +57,7 @@ When authorizing Cloudflare Pages to access a GitHub account, you can specify ac
 
 :::caution[GitHub security consideration]
 
-A GitHub account should only point to one Cloudflare account, however, this is not enforced. If you are setting up Cloudflare with GitHub for your organization, Cloudflare recommends that you limit the scope of the application to only the repositories you intend to build with Pages at the time that you set up your project. You can modify these permissions as you build more applications.
+A GitHub account should only point to one Cloudflare account. If you are setting up Cloudflare with GitHub for your organization, Cloudflare recommends that you limit the scope of the application to only the repositories you intend to build with Pages. You can modify these permissions by going to the [Applications page](https://github.com/settings/installations) on GitHub, select **Switch settings context** to access your GitHub organization settings. Then, select **Cloudflare Workers & Pages** > For **Repository access**, select **Only select repositories** > select your repositories.
 
 :::
 

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

@@ -7,7 +7,7 @@ Cloudflare supports connecting Cloudflare Pages to your [GitHub](/pages/configur
 
 Using Git integration with Cloudflare also provides:
 
-- **Preview deployments for custom branches**, generating preview URLs for any branch in the repository without affecting your production deployment.
+- **Preview deployments for custom branches**, generating preview URLs for a commit to any branch in the repository without affecting your production deployment.
 - **Preview URLs in pull requests** (PRs) to the repository.
 - **Build and deployment status checks** within the Git repository.
 - **Skipping builds using a commit message**.
@@ -32,8 +32,8 @@ Cloudflare Pages supports the following Git providers:
 
 If you use [GitHub Enterprise Server](https://docs.github.com/en/[email protected]/admin/overview/about-github-enterprise-server), [Self-Managed GitLab](https://about.gitlab.com/pricing/), or another Git provider (e.g., Bitbucket), you can:
 
-- Start with a Direct Upload project and deploy using a CI/CD provider with [Wrangler CLI](/workers/wrangler/commands/#deploy)
-- Or, [disable automatic deployments](/pages/configuration/git-integration/#disable-automatic-deployments) in a Git-integrated project and use a CI/CD provider to deploy with [Wrangler CLI](/workers/wrangler/commands/#deploy).
+- Start with a Direct Upload project and deploy using a [CI/CD provider with Wrangler CLI](/pages/how-to/use-direct-upload-with-continuous-integration/).
+- Or, [disable automatic deployments](/pages/configuration/git-integration/#disable-automatic-deployments) in a Git-integrated project and use a [CI/CD provider with Wrangler CLI](/pages/how-to/use-direct-upload-with-continuous-integration/).
 
 ## Adding Git Integration
 

src/content/docs/pages/get-started/c3.mdx

@@ -10,7 +10,14 @@ description: Use C3 (`create-cloudflare` CLI) to set up and deploy new
   deployment.
 ---
 
-import { Render, TabItem, Tabs, Type, MetaInfo, PackageManagers } from "~/components";
+import {
+	Render,
+	TabItem,
+	Tabs,
+	Type,
+	MetaInfo,
+	PackageManagers,
+} from "~/components";
 
 Cloudflare provides a CLI command for creating new Workers and Pages projects — `npm create cloudflare`, powered by the [`create-cloudflare` package](https://www.npmjs.com/package/create-cloudflare).
 
@@ -229,7 +236,7 @@ Cloudflare collects anonymous usage data to improve `create-cloudflare` over tim
 You can opt-out if you do not wish to share any information.
 
 <PackageManagers
-  type="create"
+	type="create"
 	pkg="cloudflare@latest"
 	args="telemetry disable"
 />
@@ -243,15 +250,15 @@ export CREATE_CLOUDFLARE_TELEMETRY_DISABLED=1
 You can check the status of telemetry collection at any time.
 
 <PackageManagers
-  type="create"
-  pkg="cloudflare@latest"
-  args="telemetry status"
+	type="create"
+	pkg="cloudflare@latest"
+	args="telemetry status"
 />
 
 You can always re-enable telemetry collection.
 
 <PackageManagers
-  type="create"
-  pkg="cloudflare@latest"
-  args="telemetry enable"
+	type="create"
+	pkg="cloudflare@latest"
+	args="telemetry enable"
 />

src/content/docs/pages/get-started/direct-upload.mdx

@@ -10,9 +10,11 @@ description: Upload your prebuilt assets to Pages and deploy them via the
 
 import { Render } from "~/components";
 
-Direct Upload enables you to upload your prebuilt assets to Pages and deploy them to the Cloudflare global network. This guide will instruct you how to upload your assets using Wrangler or the drag and drop method.
+Direct Upload enables you to upload your prebuilt assets to Pages and deploy them to the Cloudflare global network. You should choose Direct Upload over Git integration if you want to [integrate your own build platform](/pages/how-to/use-direct-upload-with-continuous-integration/) or upload from your local computer.
 
-:::caution
+This guide will instruct you how to upload your assets using Wrangler or the drag and drop method.
+
+:::caution[You cannot switch to Git integration later]
 If you choose Direct Upload, you cannot switch to [Git integration](/pages/get-started/git-integration/) later. You will have to create a new project with Git integration to use automatic deployments.
 :::
 

src/content/docs/pages/get-started/git-integration.mdx

@@ -9,7 +9,7 @@ description: Connect your Git provider to Pages.
 
 import { Details, Render } from "~/components";
 
-In this guide, you will get started with Cloudflare Pages, and deploy your first website to the Pages platform through Git integration. The Git integration enables automatic builds and deployments every time you push a change to your connected GitHub or GitLab repository.
+In this guide, you will get started with Cloudflare Pages, and deploy your first website to the Pages platform through Git integration. The Git integration enables automatic builds and deployments every time you push a change to your connected [GitHub](/pages/configuration/git-integration/github-integration/) or [GitLab](/pages/configuration/git-integration/gitlab-integration/) repository.
 
 :::caution[You cannot switch to Direct Upload later]
 If you deploy using the Git integration, you cannot switch to [Direct Upload](/pages/get-started/direct-upload/) later. However, if you already use a Git-integrated project and do not want to trigger deployments every time you push a commit, you can [disable automatic deployments](/pages/configuration/git-integration/#disable-automatic-deployments) on all branches. Then, you can use Wrangler to deploy directly to your Pages projects and make changes to your Git repository without automatically triggering a build.

src/content/docs/pages/platform/known-issues.mdx

@@ -19,7 +19,7 @@ Here are some known bugs and issues with Cloudflare Pages:
 
 ## Git configuration
 
-- After you have selected a GitHub/GitLab repository for your Pages application, it cannot be changed. Delete your Pages project and create a new one pointing at a different repository if you need to update it.
+- If you deploy using the Git integration, you cannot switch to Direct Upload later. However, if you already use a Git-integrated project and do not want to trigger deployments every time you push a commit, you can [disable/pause automatic deployments](/pages/configuration/git-integration/#disable-automatic-deployments). Alternatively, you can delete your Pages project and create a new one pointing at a different repository if you need to update it.
 
 ## Build configuration
 

src/content/docs/workers/ci-cd/builds/git-integration/github-integration.mdx

@@ -44,7 +44,7 @@ To add Cloudflare Workers installation to an organization, your user account mus
 
 :::caution[GitHub security consideration]
 
-A GitHub account should only point to one Cloudflare account. If you are setting up Cloudflare with GitHub for your organization, Cloudflare recommends that you limit the scope of the application to only the repositories you intend to build with Workers at the time that you set up your project. You can modify these permissions as you build more applications.
+A GitHub account should only point to one Cloudflare account. If you are setting up Cloudflare with GitHub for your organization, Cloudflare recommends that you limit the scope of the application to only the repositories you intend to build with Pages. You can modify these permissions by going to the [Applications page](https://github.com/settings/installations) on GitHub, select **Switch settings context** to access your GitHub organization settings. Then, select **Cloudflare Workers & Pages** > For **Repository access**, select **Only select repositories** > select your repositories.
 
 :::
 

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

@@ -43,7 +43,7 @@ If a build succeeds, it is uploaded as a version. If the build is configured to
 
 :::
 
-## Disabling Builds
+## Disconnecting Builds
 
 To disable automatic builds and deployments from your Git repository, go to **Settings** > **Builds** and select **Disconnect** under **Git Repositories**. If you want to switch to a different repository for your Worker, you must first disable Builds, then reconnect to select the new repository.
 

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

@@ -6,10 +6,9 @@ sidebar:
 head:
   - tag: title
     content: Get started - Dashboard
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Follow this guide to create a Workers application using [the Cloudflare dashboard](https://dash.cloudflare.com).
 
@@ -38,6 +37,7 @@ To create a Workers application:
 
 To do more:
 
+- Push your project to a GitHub or GitLab respoitory then [connect to Builds](/workers/ci-cd/builds/#get-started) to enable automatic builds and deployments.
 - Review our [Examples](/workers/examples/) and [Tutorials](/workers/tutorials/) for inspiration.
 - Set up [bindings](/workers/runtime-apis/bindings/) to allow your Worker to interact with other resources and unlock new functionality.
 - Learn how to [test and debug](/workers/testing/) your Workers.

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

@@ -48,11 +48,11 @@ cd my-first-worker
 
 In your project directory, C3 will have generated the following:
 
-* `wrangler.toml`: Your [Wrangler](/workers/wrangler/configuration/#sample-wranglertoml-configuration) configuration file.
-* `index.js` (in `/src`): A minimal `'Hello World!'` Worker written in [ES module](/workers/reference/migrate-to-module-workers/) syntax.
-* `package.json`: A minimal Node dependencies configuration file.
-* `package-lock.json`: Refer to [`npm` documentation on `package-lock.json`](https://docs.npmjs.com/cli/v9/configuring-npm/package-lock-json).
-* `node_modules`: Refer to [`npm` documentation `node_modules`](https://docs.npmjs.com/cli/v7/configuring-npm/folders#node-modules).
+- `wrangler.toml`: Your [Wrangler](/workers/wrangler/configuration/#sample-wranglertoml-configuration) configuration file.
+- `index.js` (in `/src`): A minimal `'Hello World!'` Worker written in [ES module](/workers/reference/migrate-to-module-workers/) syntax.
+- `package.json`: A minimal Node dependencies configuration file.
+- `package-lock.json`: Refer to [`npm` documentation on `package-lock.json`](https://docs.npmjs.com/cli/v9/configuring-npm/package-lock-json).
+- `node_modules`: Refer to [`npm` documentation `node_modules`](https://docs.npmjs.com/cli/v7/configuring-npm/folders#node-modules).
 
 </Details>
 
@@ -191,14 +191,15 @@ Preview your Worker at `<YOUR_WORKER>.<YOUR_SUBDOMAIN>.workers.dev`.
 
 <Details header="Seeing 523 errors?">
 
-If you see [`523` errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-523-origin-is-unreachable) when pushing your  `*.workers.dev` subdomain for the first time, wait a minute or so and the errors will resolve themselves.
+If you see [`523` errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-523-origin-is-unreachable) when pushing your `*.workers.dev` subdomain for the first time, wait a minute or so and the errors will resolve themselves.
 
 </Details>
 
 ## Next steps
 
 To do more:
 
+- Push your project to a GitHub or GitLab respoitory then [connect to Builds](/workers/ci-cd/builds/#get-started) to enable automatic builds and deployments.
 - Visit the [Cloudflare dashboard](https://dash.cloudflare.com/) for simpler editing.
 - Review our [Examples](/workers/examples/) and [Tutorials](/workers/tutorials/) for inspiration.
 - Set up [bindings](/workers/runtime-apis/bindings/) to allow your Worker to interact with other resources and unlock new functionality.