Skip to content

Commit a247081

Browse files
Apply suggestions from code review
Co-authored-by: Daniel Walsh <[email protected]>
1 parent 91991af commit a247081

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

src/content/docs/d1/examples/d1-and-sveltekit.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ import { TabItem, Tabs } from "~/components"
1919

2020
To set up a new SvelteKit site on Cloudflare Pages that can query D1:
2121

22-
1. **Refer to [the Svelte guide](/pages/framework-guides/deploy-a-svelte-kit-site/) and Svelte's [Cloudflare adapter](https://kit.svelte.dev/docs/adapter-cloudflare)**.
22+
1. **Refer to [the SvelteKit guide](/pages/framework-guides/deploy-a-svelte-kit-site/) and Svelte's [Cloudflare adapter](https://kit.svelte.dev/docs/adapter-cloudflare)**.
2323
2. Install the Cloudflare adapter within your SvelteKit project: `npm i -D @sveltejs/adapter-cloudflare`.
2424
3. Bind a D1 database [to your Pages Function](/pages/functions/bindings/#d1-databases).
2525
4. Pass the `--d1 BINDING_NAME=DATABASE_ID` flag to `wrangler dev` when developing locally. `BINDING_NAME` should match what call in your code, and `DATABASE_ID` should match the `database_id` defined in your wrangler.toml: for example, `--d1 DB=xxxx-xxxx-xxxx-xxxx-xxxx`.

src/content/docs/pages/framework-guides/deploy-an-elderjs-site.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ title: Elder.js
55

66
import { PagesBuildPreset, Render } from "~/components";
77

8-
[Elder.js](https://elderguide.com/tech/elderjs/) is an SEO-focused framework for building static sites with [Svelte](/pages/framework-guides/deploy-a-svelte-kit-site/).
8+
[Elder.js](https://elderguide.com/tech/elderjs/) is an SEO-focused framework for building static sites with [SvelteKit](/pages/framework-guides/deploy-a-svelte-kit-site/).
99

1010
In this guide, you will create a new Elder.js application and deploy it using Cloudflare Pages.
1111

src/content/docs/pages/how-to/preview-with-cloudflare-tunnel.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ cloudflared version 2021.5.9 (built 2021-05-21-1541 UTC)
2323

2424
## Run a local service
2525

26-
The easiest way to get up and running with Cloudflare Tunnel is to have an application running locally, such as a [React](/pages/framework-guides/deploy-a-react-site/) or [Svelte](/pages/framework-guides/deploy-a-svelte-kit-site/) site. When you are developing an application with these frameworks, they will often make use of a `npm run develop` script, or something similar, which mounts the application and runs it on a `localhost` port. For example, the popular `vite` tool runs your in-development React application on port `5173`, making it accessible at the `http://localhost:5173` address.
26+
The easiest way to get up and running with Cloudflare Tunnel is to have an application running locally, such as a [React](/pages/framework-guides/deploy-a-react-site/) or [SvelteKit](/pages/framework-guides/deploy-a-svelte-kit-site/) site. When you are developing an application with these frameworks, they will often make use of a `npm run develop` script, or something similar, which mounts the application and runs it on a `localhost` port. For example, the popular `vite` tool runs your in-development React application on port `5173`, making it accessible at the `http://localhost:5173` address.
2727

2828
## Start a Cloudflare Tunnel
2929

0 commit comments

Comments
 (0)