Copy-edits courtesy of a review from @omehegan

content/doc/book/pipeline/jenkinsfile.adoc

@@ -12,7 +12,7 @@ layout: section
 = The Jenkinsfile
 
 This section builds on the information covered in <<getting-started#, Getting Started>>,
-and introduces more useful steps, common patterns and demonstrates some
+and introduces more useful steps, common patterns, and demonstrates some
 non-trivial `Jenkinsfile` examples.
 
 Creating a `Jenkinsfile`, which is checked into source control
@@ -36,7 +36,7 @@ the Pipeline in a `Jenkinsfile` and check that in to source control.
 As discussed in the <<getting-started#defining-a-pipeline-in-scm, Getting Started>>
 section, a `Jenkinsfile` is a text file that contains the definition of a
 Jenkins Pipeline and is checked into source control. Consider the following
-Pipeline which implements a basic, three-stage, continuous delivery pipeline.
+Pipeline which implements a basic three-stage continuous delivery pipeline.
 
 [pipeline]
 ----
@@ -58,8 +58,8 @@ node { // <1>
 
 Not all Pipelines will have these same three stages, but this is a good
 continuous delivery starting point to define them for most projects. The
-following can be followed to create and execute a simple Pipeline in a
-local test installation of Jenkins.
+sections below will demonstrate the creation and execution of a simple Pipeline
+in a test installation of Jenkins.
 
 [NOTE]
 ====
@@ -139,9 +139,9 @@ Running automated tests is a crucial component of any successful continuous
 delivery process. As such, Jenkins has a number of test recording, reporting,
 and visualization facilities provided by a
 link:https://plugins.jenkins.io/?labels=report[number of plugins].
-At a fundamental level, when there are test failures,  it is useful to have
-record them reporting and visualization. The example below uses the `junit`
-step, provided by the
+At a fundamental level, when there are test failures, it is useful to have
+Jenkins record the failures for reporting and visualization in the web UI.  The
+example below uses the `junit` step, provided by the
 link:https://plugins.jenkins.io/junit[JUnit plugin].
 
 In the example below, if tests fail, the Pipeline is marked "unstable", as
@@ -174,7 +174,7 @@ pattern (`**/target/*.xml`).
 
 Deployment can imply a variety of steps, depending on the project or
 organization requirements, and may be anything from publishing built artifacts
-to an Artifactory server, or pushing code to a production system.
+to an Artifactory server, to pushing code to a production system.
 
 At this stage of the example Pipeline, both the "Build" and "Test" stages have
 successfully executed. In essense, the "Deploy" stage will only execute
@@ -211,13 +211,13 @@ more advanced Pipeline Script syntax in more detail.
 
 Pipeline Script is a domain-specific language
 footnoteref:[dsl, https://en.wikipedia.org/wiki/Domain-specific_language]
-based on Groovy, therefore much of
+based on Groovy, most
 link:http://groovy-lang.org/semantics.html[Groovy syntax]
-can be used without further consideration in Pipeline Script.
+can be in Pipeline Script without modification.
 
 === String Interpolation
 
-Groovy's "String" interpolation support can be confusing to many new-comers to
+Groovy's "String" interpolation support can be confusing to many newcomers to
 the language. While Groovy supports declaring a string with either single quotes, or
 double quotes, for example: