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

Don't use "static" to describe what Gatsby does #18998

Merged
merged 2 commits into from
Oct 25, 2019
Merged
Changes from all commits
Commits
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
8 changes: 4 additions & 4 deletions www/src/components/homepage/homepage-features.js
Original file line number Diff line number Diff line change
Expand Up @@ -58,11 +58,11 @@ const HomepageFeatures = () => (
</FuturaParagraph>
</Card>
<Card>
<CardHeadline>Static Progressive Web Apps</CardHeadline>
<CardHeadline>Progressive Web Apps</CardHeadline>
<FuturaParagraph>
Gatsby.js is a static PWA (Progressive Web App) generator. You get code
and data splitting out-of-the-box. Gatsby loads only the critical HTML,
CSS, data, and JavaScript so your site loads as fast as possible. Once
Gatsby.js is a PWA (Progressive Web App) generator. You get code and
data splitting out-of-the-box. Gatsby loads only the critical HTML, CSS,
data, and JavaScript so your site loads as fast as possible. Once
loaded, Gatsby prefetches resources for other pages so clicking around
the site feels incredibly fast.
</FuturaParagraph>
Expand Down