Add Robert Haight as another solver

[cworth.org] / src / trender_bookmark.mdwn

diff --git a/src/trender_bookmark.mdwn b/src/trender_bookmark.mdwn
index 9a4f15ae9a8cf96f6382af399f0270cb10b49281..8bbac93e1f1b56b3e54904a07d6b83601f6d0fe1 100644 (file)
--- a/src/trender_bookmark.mdwn
+++ b/src/trender_bookmark.mdwn
@@ -1,8 +1,8 @@
-[[meta title="On-demand Trender"]]
+[[!meta title="On-demand Trender"]]

 
 

-[[tag performance]]
+[[!tag performance]]

 
 

-Vladimir Vukićević pointed me to an old [[blog
+Vladimir Vukićević pointed me to an old [blog

 entry](http://blog.vlad1.com/archives/2005/10/28/74/) where he
 provides a useful "bookmarklet" that I thought I'd share. It makes it
 easy to measure how long mozilla spends rendering any particular web
 entry](http://blog.vlad1.com/archives/2005/10/28/74/) where he
 provides a useful "bookmarklet" that I thought I'd share. It makes it
 easy to measure how long mozilla spends rendering any particular web


@@ -33,7 +33,7 @@ the "about:config" location in the toolbar and create a new Boolean
 entry, (right-click to find that), named
 `browser.dom.window.dump.enabled` and set it to `True`.
 
 entry, (right-click to find that), named
 `browser.dom.window.dump.enabled` and set it to `True`.
 

-At that point yous should be all setup. Just browse to a web page of
+At that point you should be all setup. Just browse to a web page of

 interest and click the "Time Render" bookmark to measure the rendering
 performance of Mozilla on that page.
 
 interest and click the "Time Render" bookmark to measure the rendering
 performance of Mozilla on that page.