Skip to content

Commit bd46aad

Browse files
fix(docs): list capitalization consistency (#721)
1 parent 8b0e0f5 commit bd46aad

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

src/routes/solid-start/building-your-application/api-routes.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,11 @@ title: "API routes"
44

55
While Server Functions can be a good way to write server-side code for data needed by your UI, sometimes you need to expose API routes.
66
Some reasons for wanting API Routes include:
7-
- there are additional clients that want to share this logic.
8-
- exposing a GraphQL or tRPC endpoint.
9-
- exposing a public facing REST API.
10-
- writing webhooks or auth callback handlers for OAuth.
11-
- having URLs not serving HTML, but other kinds of documents like PDFs or images.
7+
- There are additional clients that want to share this logic.
8+
- Exposing a GraphQL or tRPC endpoint.
9+
- Exposing a public facing REST API.
10+
- Writing webhooks or auth callback handlers for OAuth.
11+
- Having URLs not serving HTML, but other kinds of documents like PDFs or images.
1212

1313
For these use cases, SolidStart provides a way to write these routes in a way that is easy to understand and maintain.
1414
API routes are just similar to other routes and follow the same filename conventions as [UI Routes](/solid-start/building-your-application/routing).

0 commit comments

Comments
 (0)