From d4befbfdc1e1b385d5933cd41f35e1e4349151bb Mon Sep 17 00:00:00 2001
From: Josh Soref <jsoref@users.noreply.github.com>
Date: Wed, 15 Aug 2018 15:38:54 -0400
Subject: [PATCH] minor spelling/grammar/word choice improvements

---
 .../security/s2m/AdminWhitelistRule/index.jelly      | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/core/src/main/resources/jenkins/security/s2m/AdminWhitelistRule/index.jelly b/core/src/main/resources/jenkins/security/s2m/AdminWhitelistRule/index.jelly
index 738fe7cf02..a657ea84b4 100644
--- a/core/src/main/resources/jenkins/security/s2m/AdminWhitelistRule/index.jelly
+++ b/core/src/main/resources/jenkins/security/s2m/AdminWhitelistRule/index.jelly
@@ -32,8 +32,8 @@ THE SOFTWARE.
       Jenkins master is now more strict about what commands its agents can send to the master.
       Unfortunately, this prevents some plugins from functioning correctly, as those plugins do not
       specify which commands are open for agents to execute and which ones are not.
-      While plugin developers work on updating this,
-      as an administrator, you can mark commands as OK for agents to execute (aka "whitelisting".)
+      While plugin developers work on improving this,
+      as an administrator, you can mark commands as OK for agents to execute (aka "whitelisting").
     </p>
     <div class="warning" style="margin:1em">
       Please see <a href="https://jenkins.io/redirect/security-144">the discussion of this feature</a> to
@@ -43,14 +43,14 @@ THE SOFTWARE.
       <div class="warning" style="margin:1em">
         The agent &#8594; master access control subsystem is currently disabled.
         This is unsafe if you have agents from other less trusted people.
-        You can put it back on from <a href="${rootURL}/configureSecurity">Global Security Configuration UI</a>
+        You can turn it back on from <a href="${rootURL}/configureSecurity">Global Security Configuration UI</a>.
       </div>
     </j:if>
 
     <form method="post" action="submit">
       <h2>Currently Whitelisted Commands</h2>
       <p>
-        The following commands are currently whitelisted for agents to execute them on the master.
+        The following commands are currently whitelisted for agents to execute on the master.
         Type in any fully-qualified class names to white list them:
       </p>
       <textarea id="whitelist" name="whitelist" style="width:100%; height:5em">${it.whitelisted.read()}</textarea>
@@ -61,7 +61,7 @@ THE SOFTWARE.
         <h2>Currently Rejected Commands</h2>
         <p>
           Agents have attempted to use the following functionalities but the plugins that implement them
-          did not specify whether they are usable from agents or not. Check ones you want to whitelist:
+          did not specify whether or not they should be usable from agents. Check ones you want to whitelist:
         </p>
         <ul style="list-style:none">
           <j:forEach var="r" items="${rejectedList}">
@@ -86,7 +86,7 @@ THE SOFTWARE.
 
       <h2>File Access Rules</h2>
       <p>
-        The following rules control which part of <tt>$JENKINS_HOME</tt> can be access from agents:
+        The following rules control which part of <tt>$JENKINS_HOME</tt> can be accessed from agents:
       </p>
       <textarea id="filePathRules" name="filePathRules" style="width:100%; height:5em">${it.filePathRules.read()}</textarea>
       <p>