service/crm.md

@@ -150,7 +150,7 @@ See the [donate site docs for this](service/donate#rotating-api-tokens).
 
 If there's a major security breach on the service, the first thing to
 do is probably to shutdown the CiviCRM server completely. Halt the
-`crm-int-01` and `crm-ext-01` machines completely, and remove access
+`crm-int-01` and `donate-01` machines completely, and remove access
 to the underlying storage from the attacker.
 
 Then API keys secrets should probably be rotated, follow the [Rotating
@@ -299,10 +299,9 @@ of scope for TPA: sysadmins only installed the servers and setup basic
 services like a VPN (using [IPsec](howto/ipsec)) and an Apache, PHP, MySQL
 stack.
 
-The Puppet classes used on the CiviCRM server is
-`roles::civicrm_int_2018`. That naming convention reflects the fact
-that, before [donate-neo][], there used to be another role named
-`roles::civicrm_ext_2018` for the frontend, retired in
+The Puppet classes used on the CiviCRM server is `role::civicrm_int`. That
+naming convention reflects the fact that, before [donate-neo][], there used to
+be another role named `roles::civicrm_ext` for the frontend, retired in
 [tpo/tpa/team#41511](https://gitlab.torproject.org/tpo/tpa/team/-/issues/41511).
 
 [donate-neo]: service/donate