Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: spelling fixes #2145

Merged
merged 1 commit into from
Apr 12, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/app/routes/docs/concepts/targets.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,9 @@ sidebar_position: 4
## What is a target?

When a target is discussed it is sometimes in reference to the platform, e.g. you create a client side react application
changes are it's targetted at the browser. However, if you write a server-side application then you're targetting node.
chances are it's targetted at the browser. However, if you write a server-side application then you're targetting node.
Whilst `react-spring` does support the targets `web` and `native` and _can_ be server-side rendered. This is not the type
of target we're referring too.
of target we're referring to.

A target in `react-spring` is a `react reconciler` a.k.a `react renderer`. That is, a custom renderer that can process different
JSX components, it's duty is to create / update and remove these elements from the browser. `react-dom` is a prime example of
Expand Down