diff --git a/doc/manuals/chapters/config.adoc b/doc/manuals/chapters/config.adoc
index f264284..7c06392 100644
--- a/doc/manuals/chapters/config.adoc
+++ b/doc/manuals/chapters/config.adoc
@@ -75,7 +75,7 @@
 
 These kinds of resource are known:
 
-'nitb_iface'::
+'ip_address'::
 	List of IP addresses to run osmo-nitb instances on. The main unit
 	typically has a limited number of such IP addresses configured, which
 	the connected BTS models can see on their network.
@@ -138,7 +138,7 @@
 	currently always comp128v1)
 
 Side note: at first sight it might make sense to the reader to rather structure
-e.g. the 'nitb_iface' or 'arfcn' configuration as +
+e.g. the 'ip_address' or 'arfcn' configuration as +
 '"arfcn: GSM-1800: [512, 514, ...]"', +
 but the more verbose format is chosen to stay consistent with the general
 structure of resource configurations, which the resource allocation algorithm
diff --git a/doc/manuals/chapters/intro.adoc b/doc/manuals/chapters/intro.adoc
index 46c5ec6..8a09910 100644
--- a/doc/manuals/chapters/intro.adoc
+++ b/doc/manuals/chapters/intro.adoc
@@ -96,7 +96,7 @@
 
 	subgraph cluster_suite {
 		label = "Suite: sms";
-		requires [label="Requirements (suite.conf):\nmodem: times: 2\nbts\nnitb_iface\narfcn"]
+		requires [label="Requirements (suite.conf):\nmodem: times: 2\nbts\nip_address\narfcn"]
 		subgraph cluster_tests {
 			label = "Test Scripts (py)";
 			mo_mt_sms
@@ -202,7 +202,7 @@
 <<resources_conf>>.
 
 ----
-nitb_iface:
+ip_address:
 - addr: 10.42.42.1
 - addr: 10.42.42.2
 - addr: 10.42.42.3
@@ -268,7 +268,7 @@
 
 ----
 resources:
-  nitb_iface:
+  ip_address:
   - times: 1
   bts:
   - times: 1
@@ -291,7 +291,7 @@
   - type: osmo-bts-sysmo
 ----
 
-Which 'nitb_iface' or 'modem' is used in particular doesn't really matter, so
+Which 'ip_address' or 'modem' is used in particular doesn't really matter, so
 it can be left up to the osmo-gsm-tester to pick these automatically.
 
 Any number of such scenario configurations can be combined in the form