From 0aa4599bd7e0d88beaa2197f9fa502930f4980ac Mon Sep 17 00:00:00 2001
From: JStewart28 <80227058+JStewart28@users.noreply.github.com>
Date: Thu, 26 Oct 2023 11:04:03 -0600
Subject: [PATCH] Added 'the' on line 19

---
 configs/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configs/README.md b/configs/README.md
index 7985956..727b729 100644
--- a/configs/README.md
+++ b/configs/README.md
@@ -16,7 +16,7 @@ The beatnik spack package should enforce its build requirements appropriately; w
 
 ### Current list of tested systems targets and suggested installation method
 
-We have tested beatnik installation on the following systems via either spack install with the provided spack install flags or a spack environment. An example run script is also provided for each of these systems in the appropriate subdirectory.
+We have tested the beatnik installation on the following systems via either spack install with the provided spack install flags or a spack environment. An example run script is also provided for each of these systems in the appropriate subdirectory.
   * University of New Mexico - UNM systems have a full global spack packages.yaml already set up, and so it is often possible to use `spack install` with the appropriate compiler and other flags to install beatnik on these systems. We recommend adding the provided `upstreams.yaml` file in the `unm` directory to the `.spack` directory in your home directory.
     * Hopper V100/A100 GPU cluster system - Build using the environment specification in `unm/hopper/spack.yaml`. It is sometimes possible to simply use `spack install beatnik +cuda cuda_arch=80 %gcc ^cuda@11` (or `cuda_arch=70` for the V100 nodes), but this may not always work depending on how spack chooses to concretize the spack installation.
     * General UNM (Wheeler/Hopper) CPU systems - `spack install beatnik` is generally sufficient.