improve getting started section clarity

Author: AldanTanneo

doc/getting-started.md

@@ -335,22 +335,22 @@ mycrate = { path = '..' }
 ### Built-in runner
 
 The builtin Alire test runner provides a simple way to run `.adb` files as
-separate tests. It requires setting up a subcrate (let's name it `mycrate_test`
-in our example) with a GPR file that defines its executables in a specific way:
+separate tests. It requires setting up a subcrate, with a GPR file that defines
+its executables in a specific way:
 
 ```ada
-with "config/mycrate_tests_list_config.gpr"
+with "config/<cratename>_list_config.gpr"
 --  ...
-for Main use Mycrate_Tests_List_Config.Test_Files;
+for Main use <Cratename>_List_Config.Test_Files;
 ```
 
 This subcrate is automatically generated by `alr init` (unless one specifies
 `--no-test`), so you will not have to write all of this by hand.
 
 When running the `alr test` command, it will put every `.adb` file in `/src` in
-the generated `config/<cratename>_list_config.gpr` file, then build them all and
-run them in parallel in accordance with the `jobs` parameter (either from the
-manifest or the command line).
+the generated `config/<cratename>_list_config.gpr` file, then build them all 
+and run them in parallel in accordance with the `jobs` parameter (either from
+the manifest or the command line).
 
 Support code for the tests can be placed into another folder, like `/common`;
 only `.adb` files in `/src` are counted as tests. Each test must be a main