minor edits for clarity and typos

Author: drbruced12

lifecycle.rst

@@ -184,7 +184,7 @@ effective use of automation. This section introduces an approach to
 test automation, but we start by talking about the overall testing
 strategy.
 
-The best-practice for testing in the Cloud/DevOps environment is to
+The best practice for testing in the Cloud/DevOps environment is to
 adopt a *Shift Left* strategy, which introduces tests early in the
 development cycle, that is, on the left side of the pipeline shown in
 :numref:`Figure %s <fig-pipeline>`. To apply this principle, you first
@@ -311,16 +311,14 @@ switches).
 
    Example Testing Frameworks used in Aether.
 
-Some of the frameworks shown in :numref:`Figure %s
-<fig-tests>` were co-developed with the corresponding software
-component. This is true of TestVectors and TestON, which put
-customized workloads on Stratum (SwitchOS) and ONOS (NetworkOS),
-respectively. Both are open source, and hence available to pursue for
-insights into the challenges of building a testing framework. In
-contrast, NG40 is a proprietary framework for emulating 3GPP-compliant
-cellular network traffic, which due to the complexity and value in
-demonstrating adherence to the 3GPP standard, is a closed, commercial
-product.
+Some of the frameworks shown in :numref:`Figure %s <fig-tests>` were
+co-developed with the corresponding software component. This is true
+of TestVectors and TestON, which put customized workloads on Stratum
+(SwitchOS) and ONOS (NetworkOS), respectively. Both are open source,
+and hence available to be perused for insights into the challenges of
+building a testing framework. In contrast, NG40 is a
+close source, proprietary framework for emulating 3GPP-compliant
+cellular network traffic.
 
 Selenium and Robot are the most general of the five examples. Each is an
 open source project with an active developer community. Selenium is a
@@ -475,7 +473,7 @@ publish a new Docker image, triggered by a change to a ``VERSION``
 file stored in the code repo. (We'll see why in Section 4.5.)
 
 As an illustrative example, the following is from a Groovy script that
-defines the pipeline for testing the Aether API, which as we'll see in
+defines the pipeline for testing the Aether API, which, as we'll see in
 the next chapter, is auto-generated by the Runtime Control
 subsystem. We're interested in the general form of the pipeline, so
 omit most of the details, but it should be clear from the example what
@@ -518,8 +516,8 @@ patch set.
 
     *Aether uses Jenkins as our CI tool, but another popular option is
     GitHub Actions. This is a relatively new feature of GitHub (the
-    cloud service, not the software package) that nicely integrates
-    the code repo with a set of workflows that can be exectued every
+    cloud service, not to be confused with the software tool Git). GitHub Actions augment
+    the code repo with a set of workflows that can be executed every
     time a patch is submitted. In this setting, a workflow is roughly
     analogous to a Groovy pipeline.*
 
@@ -560,7 +558,7 @@ Config Repo, which includes both the set of Terraform Templates that
 specify the underlying infrastructure (we've been calling this the
 cloud platform) and the set of Helm Charts that specify the collection
 of microservices (sometimes called applications) that are to be
-deployed on that infrastructure. We already know about Terraform from
+deployed on that infrastructure. We discussed Terraform in
 Chapter 3: it's the agent that actually "acts on" the
 infrastructure-related forms. For its counterpart on the application
 side Aether uses an open source project called Fleet.
@@ -704,8 +702,8 @@ Our starting point is to adopt the widely-accepted practice of
 version number *MAJOR.MINOR.PATCH* (e.g., ``3.2.4``), where the
 *MAJOR* version increments whenever you make an incompatible API
 change, the *MINOR* version increments when you add functionality in a
-backward compatible way, and the *PATCH* corresponds to a backwards
-compatible bug fix.
+backward-compatible way, and the *PATCH* corresponds to a
+backward-compatible bug fix.
 
 .. _reading_semver:
 .. admonition:: Further Reading
@@ -731,7 +729,7 @@ the software lifecycle:
 
 * The commit that does correspond to a finalized patch is also tagged
   (in the repo) with the corresponding semantic version number. In
-  git, this tag is bound to a hash that unambiguously identifies the
+  Git, this tag is bound to a hash that unambiguously identifies the
   commit, making it the authoritative way of binding a version number
   to a particular instance of the source code.
 
@@ -797,7 +795,7 @@ chapter.
 4.6 Managing Secrets
 --------------------
 
-The discussion up this point has glossed over one important detail,
+The discussion up to this point has glossed over one important detail,
 which is how secrets are managed. These include, for example, the
 credentials Terraform needs to access remote services like GCP, as
 well as the keys used to secure communication among microservices
@@ -852,7 +850,7 @@ Controller to use its sealing key to help them unlock those secrets.
 
 While this approach is less general than the first (i.e., it is
 specific to protecting secrets within a Kubernetes cluster), it has
-the advantage of taking humans completely out-of-the-loop, with the
+the advantage of taking humans completely out of the loop, with the
 sealing key being programmatically generated at runtime. One
 complication, however, is that it is generally preferable for that
 secret to be written to persistent storage, to protect against having
@@ -898,7 +896,7 @@ with a particular set of use cases in mind, but it is later integrated
 with other software to build entirely new cloud apps that have their
 own set of abstractions and features, and correspondingly, their own
 collection of configuration state. This is true for Aether, where the
-SD-Core subsystem was originally implemented for use in global
+SD-Core subsystem, for example, was originally implemented for use in global
 cellular networks, but is being repurposed to support private 4G/5G in
 enterprises.