Description: Rm multistrap from doc
 multistrap project is dead.
Author: dod
--- a/lib/Config/Model/Tester.pm
+++ b/lib/Config/Model/Tester.pm
@@ -1018,7 +1018,7 @@
 
 =head2 Test specification with arbitrary file names
 
-In some models, like C<Multistrap>, the config file is chosen by the
+In some models, like late C<Multistrap>, the config file is chosen by the
 user. In this case, the file name must be specified for each tests
 case:
 
@@ -1030,8 +1030,6 @@
     }]
  };
 
-See the actual L<multistrap test|https://github.com/dod38fr/config-model/blob/master/t/model_tests.d/multistrap-test-conf.pl>.
-
 =head2 Backend argument
 
 Some application like systemd requires a backend argument specified by
@@ -1475,13 +1473,6 @@
 
 =item *
 
-L<multistrap-test-conf.pl|https://github.com/dod38fr/config-model/blob/master/t/model_tests.d/multistrap-test-conf.pl>
-and L<multistrap-examples|https://github.com/dod38fr/config-model/tree/master/t/model_tests.d/multistrap-examples>
-specify a test where the configuration file name is not imposed by the
-application. The file name must then be set in the test specification.
-
-=item *
-
 L<backend-shellvar-test-conf.pl|https://github.com/dod38fr/config-model/blob/master/t/model_tests.d/backend-shellvar-test-conf.pl>
 is a more complex example showing how to test a backend. The test is done creating a dummy model within the test specification.
 
