From 53c9e71f4e56f6a1d1d54463bb678bebfcc2ab3d Mon Sep 17 00:00:00 2001
From: Thomas Pollet <thomaspollet@gmail.com>
Date: Thu, 28 Apr 2016 11:51:54 -0700
Subject: [PATCH] autocommit

---
 index.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index fee2b7f..af444bb 100755
--- a/index.html
+++ b/index.html
@@ -12,10 +12,10 @@ <h2 id="Introduction">Introduction</h2>
             <!--script src="js/tree.js"></script-->
 
             <iframe id="demo_frame" src="html/demo.html?json=/json/sys_kexec_file_load_callees-trace.json&depth=4&y=8&x=200" scrolling="no" onclick="javascript:alert(1);"></iframe>
-            More examples can be found <a href=#syscall_list>here</a></p>
             <p>
             When browsing large codebases, it is often unclear how a certain function can be reached. StackTrack tries to solve this problem for the linux kernel by generating call graphs. 
-            An example interactive graph showing the codepath for the sys_chdir system call can be found <a href="http://stacktrack.github.io/tree.html?json=sys_chdir.json&trace=chdir_trace.json">here</a>. The graphs are represented as expandable trees.
+            The graphs are represented as expandable trees.
+            More examples can be found <a href=#syscall_list>here</a></p>
             </p>
             <p>For the sake of brevity this page is lacking a lot of implementation details. Should you need more information regarding some of the details, please feel free to drop me an email.
             </p>