From 2de07e5d52218489cc2250f297251f2728071408 Mon Sep 17 00:00:00 2001
From: Jonathan Shearman <jps@texterity.com.au>
Date: Sat, 19 Jan 2019 12:10:25 +1100
Subject: [PATCH] Google's JSON Style Guide URL has changed

changed to https://google.github.io/styleguide/jsoncstyleguide.xml
---
 pages/mydoc/mydoc_help_api.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/mydoc/mydoc_help_api.md b/pages/mydoc/mydoc_help_api.md
index b8acc95..47084b3 100644
--- a/pages/mydoc/mydoc_help_api.md
+++ b/pages/mydoc/mydoc_help_api.md
@@ -138,7 +138,7 @@ You can also view the same JSON file here: <a target="_blank" href="tooltips.jso
 
 You can add different fields depending on how you want the JSON to be structured. Here we just have to fields: `doc_id` and `body`. And the JSON is looking just in the tooltips collection that we created.
 
-{% include tip.html content="Check out [Google's style guide](https://google-styleguide.googlecode.com/svn/trunk/jsoncstyleguide.xml) for JSON. These best practices can help you keep your JSON file valid." %}
+{% include tip.html content="Check out [Google's style guide](https://google.github.io/styleguide/jsoncstyleguide.xml) for JSON. These best practices can help you keep your JSON file valid." %}
 
 Note that you can create different JSON files that specialize in different content. For example, suppose you have some getting started information. You could put that into a different JSON file. Using the same structure, you might add an `if` tag that checks whether the page has frontmatter that says `type: getting_started` or something. Or you could put the content into separate collection entirely (different from tooltips).