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

Commit

Permalink
Fix broken links in Getting Started guide (#258)
Browse files Browse the repository at this point in the history
These were linking to sections of the sw-toolbox readme that were moved in
GoogleChromeLabs/sw-toolbox@37f6b21
  • Loading branch information
rmacklin authored and jeffposnick committed Mar 6, 2017
1 parent 8c6aff3 commit 69a4ebe
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions GettingStarted.md
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

0 comments on commit 69a4ebe

Please sign in to comment.