From 1de9939b08f4810b0b1c954ac5f4ff4f5482eb28 Mon Sep 17 00:00:00 2001 From: Jeff Posnick Date: Mon, 25 Sep 2017 12:12:03 -0400 Subject: [PATCH] Fixes gh-pages links in the README. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index bb02318..8a08aea 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ Service Worker Toolbox provides some simple helpers for use in creating your own service workers. Specifically, it provides common caching strategies for dynamic content, such as API calls, third-party resources, and large or infrequently used local resources that you don't want precached. -Service Worker Toolbox provides an [expressive approach](https://googlechrome.github.io/sw-toolbox/usage.html#express-style-routes) to using those strategies for runtime requests. If you're not sure what service workers are or what they are for, start with [the explainer doc](https://github.com/slightlyoff/ServiceWorker/blob/master/explainer.md). +Service Worker Toolbox provides an [expressive approach](https://googlechromelabs.github.io/sw-toolbox/usage.html#express-style-routes) to using those strategies for runtime requests. If you're not sure what service workers are or what they are for, start with [the explainer doc](https://github.com/slightlyoff/ServiceWorker/blob/master/explainer.md). ## What if I need precaching as well? @@ -48,7 +48,7 @@ importScripts('bower_components/sw-toolbox/sw-toolbox.js'); // Update path to m ### Use the toolbox -To understand how to use the toolbox read the [Usage](https://googlechrome.github.io/sw-toolbox/usage.html#main) and [API](https://googlechrome.github.io/sw-toolbox/api.html#main) documentation. +To understand how to use the toolbox read the [Usage](https://googlechromelabs.github.io/sw-toolbox/usage.html#main) and [API](https://googlechromelabs.github.io/sw-toolbox/api.html#main) documentation. ## Support