diff --git a/tsa/howto/cache.mdwn b/tsa/howto/cache.mdwn
index eb74d4d6e24529867fecceb7dcaf7febab2df5db..136005a3d0c19219de175b3b070a7a0f4ee83c49 100644
--- a/tsa/howto/cache.mdwn
+++ b/tsa/howto/cache.mdwn
@@ -52,7 +52,7 @@ then hit `;` to enter the SQL query mode and issue this query:
 
 See also [[logging]] for more information about lnav.
 
-## Monitoring warnings
+## Pager playbook
 
 The only monitoring for this service is to ensure the proper number of
 nginx processes are running. If this gets triggered, the fix might be
diff --git a/tsa/howto/drbd.mdwn b/tsa/howto/drbd.mdwn
index 330840dda2a9c10f3e40b82899d11dff7c50d59e..68e3f1e1e449e9e251ec290ef2b5b8f76aca23af 100644
--- a/tsa/howto/drbd.mdwn
+++ b/tsa/howto/drbd.mdwn
@@ -65,7 +65,7 @@ Finding which host is associated with this device is easy: just call
 
 It's the host `gettor-01`.
 
-## Monitoring warnings
+## Pager playbook
 
 ### Resyncing disks
 
diff --git a/tsa/howto/fabric.mdwn b/tsa/howto/fabric.mdwn
index fa416db4bff34d84651ec5a05c944f458d7ab9b1..4f42c5cc921fc73e75deef7e2f152de84b7bc4b7 100644
--- a/tsa/howto/fabric.mdwn
+++ b/tsa/howto/fabric.mdwn
@@ -115,7 +115,7 @@ how to write new tasks.
         $ fab -H perdulce.torproject.org host.uptime
          18:06:56 up 24 days, 19:48,  1 user,  load average: 0.00, 0.00, 0.02
 
-## Monitoring warnings
+## Pager playbook
 
 N/A for now. Fabric is an ad-hoc tool and, as such, doesn't have
 monitoring that should trigger a response. It *could* however be used
diff --git a/tsa/howto/ganeti.mdwn b/tsa/howto/ganeti.mdwn
index 7f535b892273d44c25b66f714ff06f6f0c954ea7..41b1d1165028c8bb442e1ec55f201060017321ef 100644
--- a/tsa/howto/ganeti.mdwn
+++ b/tsa/howto/ganeti.mdwn
@@ -751,7 +751,7 @@ IP. You can still do so with:
 
     gnt-instance modify --net -1:add,ip=116.202.120.174,network=gnt-fsn test01.torproject.org
 
-## Monitoring warnings
+## Pager playbook
 
 ### I/O overload
 
diff --git a/tsa/howto/prometheus.mdwn b/tsa/howto/prometheus.mdwn
index 6e062a4d76adf147074449345bdb3da55223d15d..902d3785ee3b94eaaaf3bc884cad7255f1e81bec 100644
--- a/tsa/howto/prometheus.mdwn
+++ b/tsa/howto/prometheus.mdwn
@@ -29,7 +29,7 @@ dashboards for most purposes other than debugging.
 
 # How-to
 
-## Monitoring warnings
+## Pager playbook
 
 TBD.
 
diff --git a/tsa/howto/submission.mdwn b/tsa/howto/submission.mdwn
index c0d771459c8242966c37777746e242b090990310..c20f00b61b4eed1fe4562f7e7c32845e278b39d9 100644
--- a/tsa/howto/submission.mdwn
+++ b/tsa/howto/submission.mdwn
@@ -40,7 +40,7 @@ This document describes the implementation of a **MSA**, although the
 service will most likely also include a **MTA** functionality in that
 it will actually deliver emails to targets.
 
-## Monitoring warnings
+## Pager playbook
 ## Disaster recovery
 
 N/A. The server should be rebuildable from scratch using the Puppet
diff --git a/tsa/howto/template.mdwn b/tsa/howto/template.mdwn
index e6ec9697fa7e4e689ba127a272f0927bb1b21bdc..ce687ea86377fb6493c7c9c4d35010a5f4952c48 100644
--- a/tsa/howto/template.mdwn
+++ b/tsa/howto/template.mdwn
@@ -17,7 +17,7 @@
 
 <!-- more in-depth procedure that may require interpretation -->
 
-## Monitoring warnings
+## Pager playbook
 
 <!-- information about common errors from the monitoring system and -->
 <!-- how to deal with them. this should be easy to follow: think of -->
diff --git a/tsa/howto/tls.mdwn b/tsa/howto/tls.mdwn
index 8edcf277dff0ad093aea2184325adb48d44e5187..a6a283850e7555041d7349c74c0ec5a7f92c725d 100644
--- a/tsa/howto/tls.mdwn
+++ b/tsa/howto/tls.mdwn
@@ -127,7 +127,7 @@ Then run Puppet on all affected hosts, for example the static mirrors:
 
     cumin 'C:roles::static_mirror_web' 'puppet agent -t'
 
-## Monitoring warnings
+## Pager playbook
 
  * if you get email from Digicert, ask the Tor Browser team, they use
    it to sign code (see "Design" below for more information about