Fix test name

BUILDING.md

@@ -123,7 +123,7 @@ make all && make stable
 Pass `TEST=` to restrict which suite is run:
 
 ```bash
-make test-amd64 TEST=tests/01-vpp-ospf
+make test-amd64 TEST=tests/01-vpp-bird
 make test       TEST=tests/02-vpp-frr
 ```
 
@@ -141,28 +141,31 @@ xdg-open tests/out/tests-docker-log.html
 
 ```bash
 IMAGE=git.ipng.ch/ipng/vpp-containerlab:latest-amd64-test \
-  containerlab deploy -t tests/01-vpp-ospf/e2e-lab/vpp.clab.yml
+  containerlab deploy -t tests/01-vpp-bird/e2e-lab/vpp.clab.yml
 ```
 
 Then inspect live state:
 
 ```bash
-# OSPF neighbour state
-containerlab exec -t tests/01-vpp-ospf/e2e-lab/vpp.clab.yml \
+# Enter the VPP1 container:
+containerlab tools dc -t tests/01-vpp-bird/e2e-lab/vpp.clab.yml vpp1
+
+# OSPF neighbor state
+containerlab exec -t tests/01-vpp-bird/e2e-lab/vpp.clab.yml \
   --label clab-node-name=vpp1 --cmd "birdc show ospf neighbor"
 
 # Manual ping
-containerlab exec -t tests/01-vpp-ospf/e2e-lab/vpp.clab.yml \
+containerlab exec -t tests/01-vpp-bird/e2e-lab/vpp.clab.yml \
   --label clab-node-name=client1 --cmd "ping -c 5 10.82.98.82"
 
 # Tear down when done
-containerlab destroy -t tests/01-vpp-ospf/e2e-lab/vpp.clab.yml --cleanup
+containerlab destroy -t tests/01-vpp-bird/e2e-lab/vpp.clab.yml --cleanup
 ```
 
 **Common cause — OSPF convergence time:** 100% ping loss usually means routing is not up yet.
 Tune the `Sleep` duration in the relevant `.robot` file by deploying manually and watching
 `birdc show ospf neighbor` (or `vtysh -c "show ip ospf neighbor"` for FRR) until all
-neighbours reach state `Full`.
+neighbors reach state `Full`.
 
 **Increase robot verbosity:** add `--loglevel DEBUG` to the `robot` invocation in
 `tests/rf-run.sh` temporarily.