address comments

Author: AldanTanneo

doc/catalog-format-spec.md

@@ -453,19 +453,19 @@ static, i.e. they cannot depend on the context.
     jobs = <number>
     ```
 
-    `<builtin>` is a builtin test runner name, currently only `'alire'`.
+    `<builtin>` is a built-in test runner name, currently only `'alire'`.
     `<command>` is an array of strings that will be run as an external command.
 
     When running `alr test`, Alire will first enter the given `directory`, a
-    subfolder of the crate root, and execute either the builtin test runner or
+    subfolder of the crate root, and execute either the built-in test runner or
     the given external command.
 
     The `jobs` parameter describes how many tests should be run in parallel. It
-    is only valid in the context of the builtin test runner for now.
+    is only valid in the context of the built-in test runner for now.
 
     The `[test]` section also accepts an array of test runners (with
-    `[[test]]`), although this is not recommended, as you lose the ability to
-    pass extra arguments to the test command with `alr test`.
+    `[[test]]`), although you lose the ability to pass extra arguments to the
+    test command with `alr test`.
 
  - `auto-gpr-with`: optional Boolean value that specifies if the project (gpr) files
    of a crate can be automatically depended upon ('withed') directly by the root

doc/getting-started.md

@@ -318,7 +318,7 @@ projects. It needs to be configured in a `[test]` section of the Alire manifest,
 by specifying either `runner = 'alire'` or a custom runner with
 `command = [...]`.
 Any arguments passed to the `alr test` command are passed as-is to the runner
-command (or the builtin runner, which uses them for test filtering).
+command (or the built-in runner, which uses them for test filtering).
 
 It is recommended to provide tests for a library in a `tests` or `testsuite`
 subfolder of the root crate; if your test suite is an Alire crate, it can then
@@ -334,7 +334,7 @@ mycrate = { path = '..' }
 
 ### Built-in runner
 
-The builtin Alire test runner provides a simple way to run `.adb` files as
+The built-in Alire test runner provides a simple way to run `.adb` files as
 separate tests. It requires setting up a subcrate, with a GPR file that defines
 its executables in a specific way: