Streamlined language

Cut out some extraneous wording

Author: cyndy-llnl

web/about.html

@@ -16,39 +16,37 @@ <h2>The motivation behind <span class="psij-font">PSI/J</span></h2>
                                     Project</a> which brings together a number of high level HPC tools developed
                                 by the members of ExaWorks. We noticed that most of these projects, as well as
                                 many of the community projects, implemented a software layer/library to interact
-                                with HPC schedulers in order to insulate the core functionality from the
-                                details of how things are specified for each scheduler. We also noticed that
-                                the respective libraries mostly covered schedulers running on resources that
-                                each team had access to. We figured that we could use our combined knowledge to
-                                design a single API/library for this goal, a library that would be tested on all
-                                resources that all ExaWorks teams have access to. We could then share this API
-                                and library so that all high level HPC tools could benefit from it.
+                                with HPC schedulers in order to insulate the core functionality from the detailed
+                                scheduler specifications. We also noticed that
+                                the respective libraries were limited to schedulers running on resources that
+                                each team had access to. We used our combined knowledge to
+                                design a single API/library for this goal, one that would be tested on all
+                                resources that all ExaWorks teams have access to. We then shared this API
+                                and library so that all high level HPC tools can benefit from it.
                             </p>
                         </v-card>
 
                         <v-card align="left" class="mb-6 vbox">
                             <h2>The complexity of testing HPC libraries</h2>
 
                             <p>
-                                A major factor contributing to the difficulties in maintaining HPC software
+                                A major difficulty in maintaining HPC software
                                 tools is that access to HPC resources is generally limited to a small number
-                                of clusters local to each team. Additionally, HPC resources tend to vary
-                                widely depending on the institution that maintains them. Consequently, the
-                                chances that software that is tested on resources that a HPC tool development
-                                team has access to will encounter problems on other HPC resources is fairly
-                                high. As mentioned above, a first step in addressing this problem is by
-                                pooling the teams' respective resources for testing purposes. However,
+                                of clusters local to each team. Additionally, HPC resources vary
+                                widely depending on the institution that maintains them. Consequently,
+                                software that is tested on resources that a HPC tool development
+                                team has access to is likely to encounter problems on other HPC resources. A first step in addressing this problem is by
+                                pooling teams' respective resources for testing purposes.
                                 <span class="psij-font">PSI/J</span> takes it a step further by exposing an
                                 infrastructure that allows any user <span class="psij-font">PSI/J</span> user
-                                to easily contribute test results to the <span class="psij-font">PSI/J</span>,
-                                and do so automatically. This is a mutually beneficial relationship: the
-                                <span class="psij-font">PSI/J</span> community at large gains a certain level
-                                of assurance that <span class="psij-font">PSI/J</span> functions correctly on
+                                to easily contribute test results to <span class="psij-font">PSI/J</span>,
+                                and do so automatically. This is mutually beneficial: the
+                                <span class="psij-font">PSI/J</span> community gains assurance that <span class="psij-font">PSI/J</span> functions correctly on
                                 a wide range of resources, while users contributing tests have a mechanism to
                                 ensure that the <span class="psij-font">PSI/J</span> team is aware of
                                 potential problems specific to their resources and can address them, thus
                                 ensuring that <span class="psij-font">PSI/J</span> continues to function
-                                correctly on specific resources.
+                                correctly on those resources.
                             </p>
                         </v-card>