Skip to content
This repository has been archived by the owner on Jan 23, 2021. It is now read-only.

Fix broken links in Getting Started guide #258

Merged
merged 1 commit into from
Mar 6, 2017
Merged

Fix broken links in Getting Started guide #258

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 GettingStarted.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,7 @@ located as subdirectories of an `app` directory, might look like:

Once you've chosen an appropriate caching strategy to use for your dynamic
content, you can tell `sw-precache` which
[strategies](https://github.com/GoogleChrome/sw-toolbox#built-in-handlers) to
[strategies](https://googlechrome.github.io/sw-toolbox/api.html#handlers) to
use for runtime requests that match specific URL patterns:

```js
Expand All @@ -146,7 +146,7 @@ use for runtime requests that match specific URL patterns:

If you use the `runtimeCaching` option, `sw-precache` will automatically include
the [`sw-toolbox` library](https://github.com/GoogleChrome/sw-toolbox) and the
corresponding [routing configuration](https://github.com/GoogleChrome/sw-toolbox#basic-routes)
corresponding [routing configuration](https://googlechrome.github.io/sw-toolbox/usage.html#basic-routes)
in the service worker file that it generates.

### Server-side Templating
Expand Down