From 75ccae10d617c5ceee9c3755540e81a2430fc108 Mon Sep 17 00:00:00 2001
From: Sigilante <57601680+sigilante@users.noreply.github.com>
Date: Mon, 24 Apr 2023 11:00:27 -0500
Subject: [PATCH] Rename w/o agent names

---
 content/guides/additional/app-workbook/ahoy.md | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/content/guides/additional/app-workbook/ahoy.md b/content/guides/additional/app-workbook/ahoy.md
index 5d625be..6230a3d 100644
--- a/content/guides/additional/app-workbook/ahoy.md
+++ b/content/guides/additional/app-workbook/ahoy.md
@@ -1,10 +1,8 @@
 +++
-title = "%ahoy Ship Monitoring"
-weight = 10
+title = "Ship Monitoring"
+weight = 194
 +++
 
-#   `%ahoy` Ship Monitoring
-
 The `%ahoy` desk by [~midden-fabler](https://urbit.org/ids/~midden-fabler) provides a number of agents to automatically monitor ship activity such as breaching and network uptime.  This tutorial examines the `%ahoy` agent specifically with some slight simplifications to demonstrate how an Urbit-native app can be constructed.  You will see how to render a front-end using Sail, employ the `++abet` nested core design pattern, construct CLI generators, and set wakeup timers using [Behn](https://developers.urbit.org/reference/glossary/behn).
 
 `%ahoy` presents a web UI at `/ahoy` rendered using [Sail](https://developers.urbit.org/guides/additional/sail) and [~paldev](https://urbit.org/ids/~paldev)'s Rudder library alongside command-line generators to add, delete, and modify ship watches.  Notifications are sent using `%hark-store` if a ship hasn't been contacted after a specified amount of time.