diff --git a/Makefile b/Makefile
index df79f1f..e7c03c9 100644
--- a/Makefile
+++ b/Makefile
@@ -1,3 +1,3 @@
-index.html: index.md style.css
+index.html: index.md head.html
 	./bin/gh-md-toc --insert index.md
 	./bin/mmark-linux-amd64 -head head.html -html index.md > index.html
\ No newline at end of file
diff --git a/index.html b/index.html
index 437faa6..de77890 100644
--- a/index.html
+++ b/index.html
@@ -83,6 +83,8 @@
 
 ## Table of Contents
  
+<!-- this TOC is only here for github or js-challenged browsers -->
+
 <!--ts-->
 * [Introduction](#introduction)
 * [Overview](#overview)
@@ -119,7 +121,7 @@
          * [Claim Sequence](#claim-sequence-1)
          * [Bid Position](#bid-position-1)
          * [ChannelName and ClaimName](#channelname-and-claimname)
-         * [Examples](#examples)
+         * [Examples {#url-resolution-examples}](#examples-url-resolution-examples)
       * [Design Notes](#design-notes)
    * [Transactions](#transactions)
       * [Operations and Opcodes](#operations-and-opcodes)
@@ -592,7 +594,7 @@ Char ::= #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]
 
 <p>Technically, if multiple claims for the same name exist inside the same channel, they are resolved via the same resolution rules applied entirely within the sub-scope of the channel. Pragmatically, it rarely makes sense for channels to use the same name twice and support for this functionality may be unreliable in current tooling.</p>
 
-<h5 id="examples">Examples</h5>
+<h5 id="url-resolution-examples">Examples</h5>
 
 <p>Suppose the following names were claimed in the following order:</p>
 
diff --git a/index.md b/index.md
index 22cf3b9..4c01c42 100644
--- a/index.md
+++ b/index.md
@@ -33,6 +33,8 @@ A> For more technical information about LBRY, visit [lbry.tech](https://lbry.tec
 
 ## Table of Contents
  
+<!-- this TOC is only here for github or js-challenged browsers -->
+
 <!--ts-->
 * [Introduction](#introduction)
 * [Overview](#overview)
@@ -69,7 +71,7 @@ A> For more technical information about LBRY, visit [lbry.tech](https://lbry.tec
          * [Claim Sequence](#claim-sequence-1)
          * [Bid Position](#bid-position-1)
          * [ChannelName and ClaimName](#channelname-and-claimname)
-         * [Examples](#examples)
+         * [Examples {#url-resolution-examples}](#examples-url-resolution-examples)
       * [Design Notes](#design-notes)
    * [Transactions](#transactions)
       * [Operations and Opcodes](#operations-and-opcodes)
@@ -546,7 +548,7 @@ If both a channel name and a claim name is present, resolution happens in two st
 
 Technically, if multiple claims for the same name exist inside the same channel, they are resolved via the same resolution rules applied entirely within the sub-scope of the channel. Pragmatically, it rarely makes sense for channels to use the same name twice and support for this functionality may be unreliable in current tooling.
 
-##### Examples
+##### Examples {#url-resolution-examples}
 
 Suppose the following names were claimed in the following order:
 
diff --git a/watch.sh b/watch.sh
index 16bc5e1..5350510 100755
--- a/watch.sh
+++ b/watch.sh
@@ -1,3 +1,3 @@
 #!/bin/bash
 
-./bin/reflex --decoration=none --start-service=true --inverse-regex='index\.html' -- sh -c "make"
+./bin/reflex --decoration=none --start-service=true --glob='*' --inverse-regex='index\.html' -- sh -c "make"