diff --git a/content/guides/additional/app-workbook/flap.md b/content/guides/additional/app-workbook/flap.md
index 10b709d..f2cb687 100644
--- a/content/guides/additional/app-workbook/flap.md
+++ b/content/guides/additional/app-workbook/flap.md
@@ -1,12 +1,8 @@
 +++
-title = "%flap JS Client"
-weight = 60
+title = "Serving a JS Game"
+weight = 193
 +++
 
-#   `%flap` JS Client
-
-##  Introduction
-
 In this tutorial, we will take an off-the-shelf JavaScript game which runs in the browser and connect it to an Urbit back-end.  This page assumes that you have completed some version of Hoon School and App School, whether the [live courses](/courses) or the [written docs](/guides/core/hoon-school/A-intro).  Our goal is to show you one way of directly serving client code from an Urbit ship as server.
 
 _Flappy Bird_ is an "insanely irritating, difficult and frustrating game which combines a super-steep difficulty curve with bad, boring graphics and jerky movement" ([Huffington Post](https://web.archive.org/web/20140205084251/http://www.huffingtonpost.com/2014/02/03/flappy-bird-tips_n_4717406.html)).  We are going to implement `%flap`, a _Flappy Bird_ leaderboard using ~paldev’s `%pals` peer tracking agent.  The approach given in this tutorial will apply to any game which is primarily run in the browser and has some persistent state to retain across sessions or communicate between players at discrete intervals.  Direct player-v.-player games will require other techniques to implement.