Apply suggestions from code review

Co-authored-by: Michael Schlottke-Lakemper <[email protected]>

Author: vchuravy

docs/src/configuration.md

@@ -110,8 +110,9 @@ You can use the argument `mpiexec` to provide the name (or full path) of the MPI
 `mpiexec`, but some clusters require using the scheduler launcher interface (e.g. `srun`
 on Slurm, `aprun` on PBS). If the MPI library has an uncommon name you can provide it in `library_names`.
 The MPI standard does not specify the exact application binary interface (ABI).
-In case ABI detection fails you can provide a manual choice,
-but also open an issue so that the auto-detection can be improved. `export_prefs=true` can be used to copy the preferences into the `Project.toml` instead of creating a
+In case ABI detection fails you can provide a manual choice (either `MPICH`, `MPItrampoline`, `OpenMPI`, or `MicrosoftMPI`),
+but also open an issue such that the automatic detection can be improved.
+`export_prefs=true` can be used to copy the preferences into the `Project.toml` instead of creating a
 `LocalPreferences.toml` file to hold them.
 
 #### Notes to HPC cluster adminstators
@@ -158,5 +159,5 @@ The test suite can also be modified by the following variables:
 - `JULIA_MPI_TEST_NPROCS`: How many ranks to use within the tests
 - `JULIA_MPI_TEST_ARRAYTYPE`: Set to `CuArray` to test the CUDA-aware interface with
   [`CUDA.CuArray](https://github.com/JuliaGPU/CUDA.jl) buffers.
-- `JULIA_MPI_TEST_BINARY`: Check that the correct MPI binary is used for the tests
-- `JULIA_MPI_TEST_ABI`: Check that the correct MPI ABI is used for the tests
+- `JULIA_MPI_TEST_BINARY`: Check that the specified MPI binary is used for the tests
+- `JULIA_MPI_TEST_ABI`: Check that the specified MPI ABI is used for the tests