From 739ce15bec12f3ea37f5e712bbd0a40a1aed11fc Mon Sep 17 00:00:00 2001
From: hwikle-lanl <154543628+hwikle-lanl@users.noreply.github.com>
Date: Mon, 23 Dec 2024 12:43:23 -0700
Subject: [PATCH] Edit variables page for grammar and clarity (#797)

---
 docs/tests/variables.rst | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/docs/tests/variables.rst b/docs/tests/variables.rst
index f444f5e42..adf1cfb6e 100644
--- a/docs/tests/variables.rst
+++ b/docs/tests/variables.rst
@@ -14,7 +14,7 @@ where those values come from.
 Variable Sets
 -------------
 
-Variables can come several different variable sets. Each set has a
+Variables can come from several different variable sets. Each set has a
 category name ('var', 'sys', 'pav', 'sched') that is used in the
 variable reference to remove ambiguity about the source of the variable,
 but is otherwise optional. This ordering of variable sets also
@@ -45,11 +45,10 @@ and mode configuration files.
 System Variables (sys)
 ^^^^^^^^^^^^^^^^^^^^^^
 
-System variables are provided via system plugins. These are designed to
-be easy to write, and provide a way for people working with Pavilion to
-provide extra information about the system or cluster that Pavilion is
-currently running on. The values may be
-:ref:`tests.variables.deferred`.
+System variables are provided via system plugins. These plugins are
+designed to be easy to write, and provide a way for people working with
+Pavilion to provide extra information about the system or cluster that
+Pavilion is currently running on. The values may be :ref:`tests.variables.deferred`.
 
 Use ``pav show sys_vars`` to list the system variables.