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.

Sign up for GitHub

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

Jump to bottom

Fix tiny typo (1 letter) #38463

Merged
merged 2 commits into from
Aug 22, 2023
Merged

Fix tiny typo (1 letter) #38463

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cf17bb7
Fix tiny typo
holtzy Aug 18, 2023
519f48a
Merge pull request #1 from holtzy/holtzy-patch-1
holtzy Aug 18, 2023
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Fix tiny typo
  • Loading branch information
@holtzy
holtzy committed Aug 18, 2023
commit cf17bb7eba8e83e55344b9f30413fc5149b64dae
2 changes: 1 addition & 1 deletion docs/docs/reference/built-in-components/gatsby-script.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Gatsby includes a built-in `<Script>` component that aids in loading scripts per

It offers a convenient way to declare different [loading strategies](#strategies), and a default loading strategy that gives Gatsby users strong performance out of the box. It supports both [scripts with sources](#scripts-with-sources) and [inline scripts](#inline-scripts).

Whether you want to leave the heavy lifting of managing scripts to Gatsby or you want maxiumum flexibility and control, the Gatsby `<Script>` component is a great tool for the job.
Whether you want to leave the heavy lifting of managing scripts to Gatsby or you want maximum flexibility and control, the Gatsby `<Script>` component is a great tool for the job.

## Using Gatsby Script in your site

Expand Down