Skip to content
This repository was archived by the owner on Apr 6, 2023. It is now read-only.

docs: update wording of client-side rendering explanation #5049

Merged
pi0 merged 2 commits into from
May 20, 2022
Merged

docs: update wording of client-side rendering explanation #5049

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
014b248
Update 3.rendering.md
aifodu May 18, 2022
56969d8
docs: tweak wording
danielroe May 19, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/content/2.guide/1.concepts/3.rendering.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ While this technique allows building complex and dynamic UIs with smooth page tr

### Examples

Client-side rendering is a good choice for heavily interactive **web applications** that don't need indexing or frequently use the same users. It can leverage browser caching to skip the download phase on subsequent visits, such as **SaaS, back-office applications, or Online Games**.
Client-side rendering is a good choice for heavily interactive **web applications** that don't need indexing or ones frequently used by the same users. It can leverage browser caching to skip the download phase on subsequent visits, such as **SaaS, back-office applications, or Online Games**.
Comment thread
danielroe marked this conversation as resolved.
Outdated

## Universal Rendering

Expand Down