Merge pull request #12841 from g-pan/H22506-HPCC-R

HPCC-22506 Replace instances of HPCC with HPCC Systems(r)

Reviewed-by: Gavin Halliday <ghalliday@hpccsystems.com>

docs/EN_US/ConfiguringHPCC/ConfiguringHPCC.xml

@@ -3,7 +3,7 @@
 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
 <book xml:base="../">
   <bookinfo>
-    <title>Configuring the HPCC System</title>
+    <title>Configuring the HPCC Systems® Platform</title>
 
     <mediaobject>
       <imageobject>
@@ -65,7 +65,7 @@
     <title>Using Configuration Manager</title>
 
     <para>Configuration Manager is the utility with which we configure the
-    HPCC platform. The HPCC platform's configuration is stored in an XML file
+    HPCC Systems platform. The HPCC Systems platform's configuration is stored in an XML file
     named <emphasis role="bold">environment.xml</emphasis>. When you install a
     package, a default single-node environment.xml is generated. After that,
     you can use the Configuration Manager to modify it and add nodes and
@@ -81,16 +81,16 @@
     View, it is a good idea to start with a wizard generated configuration and
     use Advanced View to finish it.</para>
 
-    <para>This document will guide you through configuring an HPCC environment
+    <para>This document will guide you through configuring an HPCC Systems environment
     using the Configuration Manager.</para>
 
     <sect1 id="configuring-a-multi-node-system">
       <title>Running the Configuration Manager</title>
 
-      <para>This document will guide you through configuring an HPCC
+      <para>This document will guide you through configuring an HPCC Systems
       environment using the Configuration Manager.</para>
 
-      <para>The HPCC package should already be installed on ALL nodes.</para>
+      <para>The HPCC Systems package should already be installed on ALL nodes.</para>
 
       <para>You can use any tool or shell script you choose.</para>
 
@@ -123,7 +123,7 @@
         </listitem>
       </orderedlist>
 
-      <para>There are different ways to configure your HPCC system. You can
+      <para>There are different ways to configure your HPCC Systems platform. You can
       use the <emphasis role="bold">Generate environment wizard</emphasis> and
       use that environment or experienced users can then use the <emphasis
       role="bold">Advanced View</emphasis> for more specific customization.
@@ -159,8 +159,8 @@
           <listitem>
             <para>Press the Next button.</para>
 
-            <para>Next you will need to define the IP addresses that your HPCC
-            system will be using.</para>
+            <para>Next you will need to define the IP addresses that your HPCC Systems
+            platform will be using.</para>
           </listitem>
 
           <listitem>
@@ -284,7 +284,7 @@
               <row>
                 <entry><inlinegraphic fileref="images/OSSgr3.png" /></entry>
 
-                <entry>Keep in mind, that your HPCC configuration may be
+                <entry>Keep in mind, that your HPCC Systems configuration may be
                 different depending on your needs. For example, you may not
                 need a Roxie or you may need several smaller Roxie clusters.
                 In addition, in a production [Thor] system, you would ensure
@@ -304,9 +304,9 @@
             <listitem>
               <?dbfo keep-together="always"?>
 
-              <para>Stop the HPCC system.</para>
+              <para>Stop the HPCC Systems platform.</para>
 
-              <para>If it is running stop the HPCC system (on every node),
+              <para>If it is running stop the HPCC Systems platform (on every node),
               using a command such as this:</para>
 
               <xi:include href="Installing_and_RunningTheHPCCPlatform/Inst-Mods/SysDStop.xml"
@@ -320,7 +320,7 @@
                   <listitem>
                     <para>You may have a multi-node system and a custom script
                     such as the one illustrated in Appendix of the <emphasis
-                    role="bluebold">Installing and Running the HPCC
+                    role="bluebold">Installing and Running the HPCC Systems
                     Platform</emphasis> document to start and stop your
                     system. If that is the case please use the appropriate
                     command for stopping your system on every node.</para>
@@ -339,7 +339,7 @@
                         <entry><inlinegraphic
                         fileref="images/caution.png" /></entry>
 
-                        <entry>Be sure HPCC is stopped before attempting to
+                        <entry>Be sure the HPCC Systems platform is stopped before attempting to
                         copy the environment.xml file.</entry>
                       </row>
                     </tbody>
@@ -395,13 +395,13 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
               <para>You may want to use a script to push out the XML file to
               all nodes. See the <emphasis>Example Scripts</emphasis> section
               in the Appendix of the <emphasis role="bluebold">Installing and
-              Running the HPCC Platform</emphasis> document. You can use the
+              Running the HPCC Systems Platform</emphasis> document. You can use the
               scripts as a model to create your own script to copy the
               environment.xml file out to all your nodes.</para>
             </listitem>
 
             <listitem>
-              <para>Restart the HPCC platform on all nodes.</para>
+              <para>Restart the HPCC Systems platform on all nodes.</para>
             </listitem>
           </orderedlist>
         </sect3>
@@ -432,7 +432,7 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
         </listitem>
 
         <listitem>
-          <para>If it is running, stop the HPCC system using this command on
+          <para>If it is running, stop the HPCC Systems platform using this command on
           every node:</para>
 
           <xi:include href="Installing_and_RunningTheHPCCPlatform/Inst-Mods/SysDStop.xml"
@@ -448,7 +448,7 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
                 to use a script to perform this step. See the
                 <emphasis>Example Scripts</emphasis> section in the Appendix
                 of the <emphasis role="bluebold">Installing and Running the
-                HPCC Platform</emphasis> document.</para>
+                HPCC Systems Platform</emphasis> document.</para>
               </listitem>
             </varlistentry>
           </variablelist>
@@ -466,7 +466,7 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
                     <entry><inlinegraphic
                     fileref="images/OSSgr3.png" /></entry>
 
-                    <entry>You can use this command to confirm HPCC processes
+                    <entry>You can use this command to confirm HPCC Systems processes
                     are stopped: <para><programlisting>sudo systemctl status hpccsystems-platform.target</programlisting></para></entry>
                   </row>
                 </tbody>
@@ -698,7 +698,7 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
       <title>Software Section</title>
 
       <para>Use the software components section to configure software
-      components of the HPCC platform. Most software components are actual
+      components of the HPCC Systems platform. Most software components are actual
       running processes; however, some are just definitions used by the
       system. These definitions are used by the configuration
       generator.</para>
@@ -967,7 +967,7 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
                     <entry>keyspace</entry>
 
                     <entry>The name of the Cassandra keyspace to use for the
-                    HPCC data store. The default is
+                    HPCC Systems data store. The default is
                     <emphasis>hpcc</emphasis>.</entry>
                   </row>
 
@@ -1232,7 +1232,7 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
         <title>Drop Zone</title>
 
         <para>A Drop Zone (or landing zone) is a location where files can be
-        transferred to or from your HPCC system. The drop zone is a logical
+        transferred to or from your HPCC Systems installation. The drop zone is a logical
         combination of a path and one or more servers.</para>
 
         <para>Multiple drop zones allow you to configure different top level
@@ -1842,9 +1842,9 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
             integration</emphasis>
           </para>
 
-          <para>HPCC provides a mechanism to integrate ELK (ElasticSearch,
+          <para>HPCC Systems provides a mechanism to integrate ELK (ElasticSearch,
           Logstash, and Kibana) based visualizations into ECL Watch. This
-          feature can be configured and enabled through the HPCC Configuration
+          feature can be configured and enabled through the HPCC Systems Configuration
           manager.</para>
 
           <para>To configure the ELK Log Visualization component, click and
@@ -2010,7 +2010,7 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
         LDAPServer Installation in ConfigManager. For a complete description
         of how to add LDAP Authentication see <emphasis>Using LDAP
         Authentication</emphasis> section in the <emphasis
-        role="bluebold">Installing and Running The HPCC Platform</emphasis>
+        role="bluebold">Installing and Running The HPCC Systems Platform</emphasis>
         document.</para>
 
         <para>
@@ -2031,7 +2031,7 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
           added the LDAP computers in the Hardware section. For a complete
           description of how to add LDAP Authentication see <emphasis>Using
           LDAP Authentication</emphasis> section in the <emphasis
-          role="bluebold">Installing and Running The HPCC Platform</emphasis>
+          role="bluebold">Installing and Running The HPCC Systems Platform</emphasis>
           document.</para>
 
           <orderedlist>
@@ -2053,12 +2053,12 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
         </sect3>
 
         <sect3>
-          <title>The HPCC Administrator's account</title>
+          <title>The HPCC Systems Administrator's account</title>
 
-          <para>You can set up an HPCC Administrator's account with limited
-          administrative rights. The HPCC Administrator does not have to be an
-          LDAP Administrator's account. This allows the HPCC Administrator to
-          be able to set up users, groups, and set permissions in HPCC without
+          <para>You can set up an HPCC Systems Administrator's account with limited
+          administrative rights. The HPCC Systems Administrator does not have to be an
+          LDAP Administrator's account. This allows the HPCC Systems Administrator to
+          be able to set up users, groups, and set permissions in HPCC Systems without
           having rights to perform other LDAP administrative functions. To use
           this feature: <orderedlist>
               <listitem>
@@ -2067,14 +2067,14 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
               </listitem>
 
               <listitem>
-                <para>In the HPCC configuration manager navigate to this (LDAP
-                Server Process) page and enter the HPCC Administrator group
+                <para>In the HPCC Systems configuration manager navigate to this (LDAP
+                Server Process) page and enter the HPCC Systems Administrator group
                 name as the value in the <emphasis
                 role="bold">adminGroupName</emphasis> field.</para>
               </listitem>
 
               <listitem>
-                <para>Add (HPCC Administrator) users to this new group.</para>
+                <para>Add (HPCC Systems Administrator) users to this new group.</para>
               </listitem>
 
               <listitem>
@@ -2897,7 +2897,7 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
             </listitem>
 
             <listitem>
-              <para>Restart the HPCC system</para>
+              <para>Restart the HPCC Systems platform</para>
 
               <para>You might prefer to script this process, especially if you
               have many nodes. See the Example Scripts section in the Appendix

docs/EN_US/DynamicESDL/DynamicESDL_Includer.xml

@@ -106,7 +106,7 @@
 
       <itemizedlist>
         <listitem>
-          <para>Access to an HPCC Cluster (version 7.0 or later). This can be
+          <para>Access to an HPCC Systems Cluster (version 7.0 or later). This can be
           one running in a Virtual Machine.</para>
         </listitem>
       </itemizedlist>
@@ -134,7 +134,7 @@
 
       <para><emphasis role="bold">dESDL and LDAP Security</emphasis></para>
 
-      <para>If your HPCC platform is configured to use LDAP security, you must
+      <para>If your HPCC Systems platform is configured to use LDAP security, you must
       ensure any user who will be publishing ESDL Definitions has Access to
       <emphasis role="bold">ESDL configuration service</emphasis> set to
       <emphasis role="bold">Allow Full</emphasis>, as shown below.</para>

docs/EN_US/ECLLanguageReference/ECLR_mods/BltInFunc-PIPE.xml

@@ -40,7 +40,7 @@
 
             <entry>The name of a program to execute, which must take any input
             data through stdin and produce its output through stdout. This
-            program must have already been deployed on the HPCC cluster in the
+            program must have already been deployed on the HPCC Systems cluster in the
             Thor instance directory (such as: /var/lib/HPCCSystems/mythor/) but that can be
             overridden by the externalProgDir environment setting for the Thor
             cluster). </entry>

docs/EN_US/ECLLanguageReference/ECLR_mods/Templ-OVERVIEW.xml

@@ -6,7 +6,7 @@
       <primary>Template Language</primary>
     </indexterm> Overview</title>
 
-  <para>ECL was created to be the programming language for all of our HPCC
+  <para>ECL was created to be the programming language for all of our HPCC Systems 
   technology. Therefore, it must be able to meet all the demands of a complete
   business solution: from data ingest, through querying and processing, and
   all the way to fulfillment and customer output.</para>

docs/EN_US/ECLPlayground/ECLPlay-Mods/ECL_Playground.xml

@@ -29,14 +29,14 @@
 
       <para>ECL Playground is a tool hosted on an ESP server. A page runs in
       your browser, allowing you to access and execute self-contained ECL code
-      on your HPCC system without the use of any other tools. The ECL
+      on your HPCC Systems platform without the use of any other tools. The ECL
       Playground then shows you the results and the graph in your browser. The
       view is very similar to what the ECL IDE displays.</para>
 
       <sect2 id="ECLPlayground_AccessingThePlayground">
         <title>Accessing ECL Playground</title>
 
-        <para>ECL Playground is installed with the HPCC platform. You can
+        <para>ECL Playground is installed with the HPCC Systems platform. You can
         access it through the ECL Watch page.</para>
 
         <para><orderedlist>

docs/EN_US/ECLProgrammersGuide/PRG_Mods/CodeSign.xml

@@ -135,7 +135,7 @@
     unchanged.</para>
 
     <para>We have signed the SERVICE definitions provided by the ECL standard
-    plugins and included the public key in the HPCC platform installation.
+    plugins and included the public key in the HPCC Systems platform installation.
     Code that tries to use service definitions that are signed will continue
     to work as before but, code that tries to call arbitrary library functions
     using user-supplied SERVICE definitions will give compile errors, if the

docs/EN_US/ECLProgrammersGuide/PRG_Mods/PrG_Automated_ECL.xml

@@ -161,7 +161,7 @@ B        3
 
     <para>How you create this text file is up to you. To fully automate the
     process you may want to write a daemon application that watches a
-    directory (such as your HPCC environment's landing zone) to detect new
+    directory (such as your HPCC Systems environment's landing zone) to detect new
     files dropped in (by whatever means) and generate the appropriate ECL code
     file to process that new file in some standard fashion (typically using
     MACRO calls), then execute it from ECLplus command line as described

docs/EN_US/ECLProgrammersGuide/PRG_Mods/PrG_Roxie_Overview.xml

@@ -16,17 +16,17 @@
           <row>
             <entry><emphasis role="bold">Thor</emphasis></entry>
 
-            <entry>An HPCC cluster specifically designed to perform massive
+            <entry>An HPCC Systems cluster specifically designed to perform massive
             data manipulation (ETL) processes. This is a back-office data
             preparation tool and not meant for end-user production-level
-            queries. See the HPCC operational manuals for complete
+            queries. See the HPCC Systems operational manuals for complete
             documentation.</entry>
           </row>
 
           <row>
             <entry><emphasis role="bold">Roxie</emphasis></entry>
 
-            <entry>An HPCC cluster specifically designed to service standard
+            <entry>An HPCC Systems cluster specifically designed to service standard
             queries, providing a throughput rate of a thousand-plus responses
             per second (actual response rate for any given query is, of
             course, dependent on its complexity). This is a production-level
@@ -40,7 +40,7 @@
             <entry>An R&amp;D platform designed for iterative, interactive
             development and testing of Roxie queries. This is not a separate
             cluster, but a "piggyback" implementation of ECL Agent and Thor.
-            See the HPCC operational manuals for complete
+            See the HPCC Systems operational manuals for complete
             documentation.</entry>
           </row>
         </tbody>

docs/EN_US/ECLProgrammersGuide/PRG_Mods/PrG_Roxie_Overview2.xml

@@ -49,21 +49,21 @@
             <entry>Thor</entry>
 
             <entry>The commonly used name for an instance of the Data Refinery
-            component of the HPCC platform.</entry>
+            component of the HPCC Systems platform.</entry>
           </row>
 
           <row>
             <entry>Roxie</entry>
 
             <entry>The commonly used name for an instance of the Rapid Data
-            Delivery Engine component of the HPCC platform.</entry>
+            Delivery Engine component of the HPCC Systems platform.</entry>
           </row>
 
           <row>
             <entry>hThor</entry>
 
             <entry>The commonly used name for an instance of the Data Delivery
-            Engine component of the HPCC platform.</entry>
+            Engine component of the HPCC Systems platform.</entry>
           </row>
         </tbody>
       </tgroup>

docs/EN_US/ECLProgrammersGuide/PRG_Mods/PrG_Workwith_Blobs.xml

@@ -11,18 +11,18 @@
   <para>There are essentially three issues around working with BLOB
   data:</para>
 
-  <para>1) How to get the data into the HPCC (spraying).</para>
+  <para>1) How to get the data into the HPCC Systems cluster(spraying).</para>
 
-  <para>2) How to work with the data, once it is in the HPCC.</para>
+  <para>2) How to work with the data, once it is in the HPCC Systems cluster.</para>
 
-  <para>3) How to get the data back out of the HPCC (despraying).</para>
+  <para>3) How to get the data back out of the HPCC Systems cluster (despraying).</para>
 
   <sect2 id="Spraying_BLOB_Data">
     <title>Spraying BLOB Data</title>
 
     <para>In the HPCCClientTools.PDF there is a chapter devoted to the
     DFUplus.exe program. This is a command line tool with specific options
-    that allow you to spray and despray files into BLOBs in the HPCC. In all
+    that allow you to spray and despray files into BLOBs in the HPCC Systems cluster. In all
     the examples below, we'll assume you have a DFUPLUS.INI file in the same
     folder as the executable containing the standard content described in that
     section of the PDF.</para>
@@ -49,7 +49,7 @@
   <sect2 id="Working_with_BLOB_Data">
     <title>Working with BLOB Data</title>
 
-    <para>Once you've sprayed the data into the HPCC you must define the
+    <para>Once you've sprayed the data into the HPCC Systems cluster you must define the
     RECORD structure and DATASET. The following RECORD structure defines the
     result of the spray above:</para>
 
@@ -93,7 +93,7 @@ BUILDINDEX(imageKey);</programlisting>
     <title>Despraying BLOB Data</title>
 
     <para>The DFUplus.exe program also allows you to despray BLOB files from
-    the HPCC, splitting them back into the separate files they originated
+    the HPCC Systems platform, splitting them back into the separate files they originated
     from. The key to making a despray operation write BLOBs to separate files
     is the use of the <emphasis>splitprefix=Filename,Filesize</emphasis>
     option. For example, the following command line desprays all the BLOB data

docs/EN_US/ECLScheduler/ECLSched-Mods/ECLSchedAdmin.xml

@@ -27,7 +27,7 @@
       <para>The <emphasis role="bold">scheduleadmin</emphasis> is the command
       line interface to the ECL Scheduler. The scheduleadmin is located by
       default in <emphasis role="bold">/opt/HPCCSystems/bin/ </emphasis>on
-      your HPCC system.</para>
+      your HPCC Systems platform.</para>
 
       <para><emphasis role="bold">scheduleadmin
       </emphasis><emphasis>daliserver</emphasis>

docs/EN_US/ECLScheduler/ECLSched-Mods/ECLSchedComp.xml

@@ -37,8 +37,8 @@
       
 
       <para>The ECL Scheduler installs when
-      you install the HPCC platform. It
-      starts and stops using hpcc-init, just as all other HPCC
+      you install the HPCC Systems platform. It
+      starts and stops using hpcc-init, just as all other HPCC Systems platform
       components.</para>
     </sect1>
 

docs/EN_US/ECLScheduler/ECLScheduler.xml

@@ -67,7 +67,7 @@
       <title>Introduction</title>
 
       <para>The ECL Scheduler is a component process installed with the HPCC
-      system platform. It typically starts with the platform.</para>
+      Systems platform. It typically starts with the platform.</para>
 
       <para>An interface to the scheduler is available through ECL Watch. The
       ECL Scheduler interface allows you to see a list of scheduled workunits.

docs/EN_US/ECLWatch/ECLWa_mods/ECLWatchSrc.xml

@@ -75,18 +75,18 @@
 
     <para>This document depicts details about the newly redesigned ECL Watch.
     The new design is more practical and offers many new features and
-    functionality. The new ECL Watch is bundled with the 4.x HPCC Platform
+    functionality. The new ECL Watch is bundled with the 4.x HPCC Systems platform
     software.</para>
 
     <sect1 id="ECLWatch4x">
       <title>ECL Watch 4.x</title>
 
-      <para>ECL Watch provides an interface to the HPCC system and allows you
+      <para>ECL Watch provides an interface to the HPCC Systems platform and allows you
       to view information and interrogate nodes to confirm all expected
       processes are running. This provides a simple view into the system and a
       means to perform Work Unit and data files maintenance.***</para>
 
-      <para>Using ECL watch assumes your HPCC system is up and running, able
+      <para>Using ECL watch assumes your HPCC Systems platform is up and running, able
       to process jobs, and workunits. You would use the ECL Watch interface to
       both check the status of your jobs, and perform operations on those
       jobs.***</para>
@@ -1319,7 +1319,7 @@
             <listitem>
               <para>Press the <emphasis role="bold">Remote Copy</emphasis>
               button to open the dialog where you can copy files from a
-              foreign HPCC Platform. You will need premission to access the
+              foreign HPCC Systems platform. You will need premission to access the
               foreign Dali server.</para>
             </listitem>
 
@@ -1983,7 +1983,7 @@
       <title>Operations</title>
 
       <para>The Operations page provides access to several system
-      administrator tasks you can perform on your HPCC system. To access the
+      administrator tasks you can perform on your HPCC Systems platform. To access the
       Operations page click the Operations link from the Navigation pane in
       ECL Watch.</para>
 

docs/EN_US/ECLWatch/ECLWa_mods/SessFaq.xml

@@ -4,7 +4,7 @@
 <sect1 id="session-management" role="nobrk">
   <title>Session Management</title>
 
-  <para>The 7.0 release of HPCC Platform introduces the new ESP Session
+  <para>The 7.0 release of HPCC Systems platform introduces the new ESP Session
   Management security feature. This functions like many banking applications,
   where after a configurable period of inactivity you are warned with a "You
   are about to be locked out" pop-up. If no action further is taken, the
@@ -154,7 +154,7 @@
       </listitem>
 
       <listitem>
-        <para><emphasis role="strong">Q</emphasis>: Will HPCC command line
+        <para><emphasis role="strong">Q</emphasis>: Will HPCC Systems command line
         utilities be affected?</para>
 
         <para><emphasis role="strong">A</emphasis>: Possibly. If you have
@@ -216,7 +216,7 @@
         require SSL/TLS and HTTPS?</para>
 
         <para><emphasis role="strong">A</emphasis>: These secure protocols are
-        already available for your HPCC Administrator to configure. Though not
+        already available for your HPCC Systems Administrator to configure. Though not
         required for session management, hopefully they are currently
         enabled.</para>
       </listitem>
@@ -236,7 +236,7 @@
         Session Management changes?</para>
 
         <para><emphasis role="strong">A</emphasis>: You can configure your
-        system to use Session Management as part of HPCC Version 7.0.</para>
+        system to use Session Management as part of HPCC Systems Version 7.0.</para>
       </listitem>
     </orderedlist>
   </sect2>

docs/EN_US/ECLWatch/TheECLWatchMan.xml

@@ -67,9 +67,9 @@
     <title>Introducing ECL Watch</title>
 
     <para>ECL Watch is a service that runs on the Enterprise Services Platform
-    (ESP), a middleware component on the HPCC Platform.</para>
+    (ESP), a middleware component on the HPCC Systems platform.</para>
 
-    <para>ECL Watch provides an interface to the HPCC system and allows you to
+    <para>ECL Watch provides an interface to the HPCC Systems platform and allows you to
     view information and interrogate nodes to confirm all expected processes
     are running. It is a plugin that is useful for Systems Administrators to
     check processes, examine topology, and view logs. It is useful to ECL
@@ -78,7 +78,7 @@
     perform Workunit and data files maintenance.</para>
 
     <para>The ECL Watch interface is a browser based set of pages where you
-    can access and interface with the HPCC System. To Run <emphasis
+    can access and interface with the HPCC Systems platform. To Run <emphasis
     role="bold">ECL Watch</emphasis> using you browser, go to the node on your
     system running <emphasis role="bold">ESP/ECL Watch</emphasis> on port
     8010. For example, http://nnn.nnn.nnn.nnn:8010, where nnn.nnn.nnn.nnn is
@@ -278,7 +278,7 @@
 
           <para>The Monitor indicator light is used to provide an at a glance
           snapshot of your overall system health. If you have monitoring and
-          reporting configured (see <emphasis>HPCC Monitoring and
+          reporting configured (see <emphasis>HPCC Systems Monitoring and
           Reporting</emphasis>) then this light will display a color based on
           the the overall (configurable) system health. The light is black if
           there is no monitoring or reporting configured for your
@@ -427,17 +427,17 @@
           bottom of the tab. A copy facility is also provided.</para>
 
           <para>The <emphasis role="bold">Release Notes</emphasis> link opens
-          a new browser tab to the HPCC release notes page where you can find
+          a new browser tab to the HPCC Systems release notes page where you can find
           more release specific information about the contents of each version
           of HPCC.</para>
 
           <para>The <emphasis role="bold">Documentation</emphasis> link opens
-          a new browser tab to the HPCC documentation page, where you can view
-          and download the HPCC system documentation.</para>
+          a new browser tab to the HPCC Systems documentation page, where you can view
+          and download the HPCC Systems platform documentation.</para>
 
           <para>The <emphasis role="bold">Downloads</emphasis> link opens a
-          new browser tab to the HPCC downloads page, where you can find and
-          download the HPCC Platform, Client Tools, and Plugins.</para>
+          new browser tab to the HPCC Systems downloads page, where you can find and
+          download the HPCC Systems platform, client tools, and plugins.</para>
 
           <para>The <emphasis role="bold">Additional Resources</emphasis> link
           opens a submenu that provides links to areas on the HPCC Systems web
@@ -451,7 +451,7 @@
           system.</para>
 
           <para>The <emphasis role="bold">About</emphasis> link opens a dialog
-          to display information about the version of the HPCC platform
+          to display information about the version of the HPCC Systems platform
           installed on your server.</para>
         </sect3>
 
@@ -509,7 +509,7 @@
           <sect4 id="ECLWatch_AdvancedMenuChangePassword" role="nobrk">
             <title>Change Password</title>
 
-            <para>If authentication is enabled on your HPCC system, you can
+            <para>If authentication is enabled on your HPCC Systems platform, you can
             change your password, right from the User Details window.
             <orderedlist>
                 <listitem>
@@ -1077,11 +1077,11 @@
   <chapter id="ECLWatch_FilesChapter">
     <title>Files</title>
 
-    <para>This chapter contains sections dealing with HPCC Platform Files,
+    <para>This chapter contains sections dealing with HPCC Systems platform Files,
     found on the <emphasis role="bold">Files</emphasis> link in ECL
     Watch.</para>
 
-    <para>In an HPCC platform, data files are partitioned across nodes. The
+    <para>In an HPCC Systems platform, data files are partitioned across nodes. The
     file parts, referenced using Logical Filenames, are stored in the
     Distributed File Utility. This allows the collection of file parts to be
     referenced as a single entity.</para>
@@ -1744,7 +1744,7 @@
       <para>There are User Administration features available through ECL
       Watch. Common system administration tasks are accessible through the
       Operations menu in ECL Watch. The links to Users, Groups, Permissions,
-      and Resources allow you to manage these components of your HPCC system
+      and Resources allow you to manage these components of your HPCC Systems platform
       from the ECL Watch interface.</para>
 
       <xi:include href="Installing_and_RunningTheHPCCPlatform/Inst-Mods/UserSecurityMaint.xml"
@@ -1853,8 +1853,8 @@
         <title>Installing Ganglia in ECL Watch</title>
 
         <para>In order to use Ganglia in ECL Watch, you need to have Ganglia
-        installed on your HPCC System. For details on installing Ganglia for
-        ECL Watch, refer to the <emphasis>HPCC Monitoring and
+        installed on your HPCC Systems platform. For details on installing Ganglia for
+        ECL Watch, refer to the <emphasis>HPCC Systems Monitoring and
         Reporting</emphasis> manual.</para>
       </sect2>
     </sect1>
@@ -1873,7 +1873,7 @@
     Systems<superscript>®</superscript> Web Portal at <ulink
     url="http://hpccsystems.com/">http://hpccsystems.com/</ulink> for software
     updates, plugins, support, documentation, and more. This is where you can
-    find resources useful for running and maintaining HPCC on the web
+    find resources useful for running and maintaining HPCC Systems on the web
     portal.</para>
 
     <para>You can also get to the resources link on the HPCC
@@ -1881,14 +1881,14 @@
     <emphasis role="bold">Additional Resources</emphasis> link found on the
     sub-menu of at the top right hand side of navigation bar.</para>
 
-    <para>ECL Watch provides a link to the HPCC portal's download page: <ulink
+    <para>ECL Watch provides a link to the HPCC Systems download page: <ulink
     url="http://hpccsystems.com/download">http://hpccsystems.com/download</ulink>.
     This is the page where you can download Installation packages, virtual
     images, source code, documentation, and tutorials.</para>
   </chapter>
 
   <appendix id="SessMgmtFAQ">
-    <title>HPCC Session Management</title>
+    <title>HPCC Systems Session Management</title>
 
     <xi:include href="ECLWatch/ECLWa_mods/SessFaq.xml"
                 xpointer="xpointer(//*[@id='session-management'])"

docs/EN_US/HDFSConnector/HDFS_Mods/HDFS_Install.xml

@@ -17,7 +17,7 @@
       </listitem>
 
       <listitem>
-        <para>You must install the package on every HPCC Thor node. To install
+        <para>You must install the package on every HPCC Systems Thor node. To install
         the package, follow the installation instructions for your operating
         system:</para>
 
@@ -60,7 +60,7 @@
   <sect2>
     <title>Editing and distributing the Configuration file</title>
 
-    <para>After you install the HDFS to HPCC Connector package, you must edit
+    <para>After you install the HDFS to HPCC Systems Connector package, you must edit
     the configuration file and push it out to all nodes.</para>
 
     <orderedlist>
@@ -96,7 +96,7 @@
   <sect2 role="brk">
     <title>Installing the ECL library to your ECL IDE source folder</title>
 
-    <para>The HDSF to HPCC Connector library is a single ECL file containing
+    <para>The HDFS to HPCC Systems Connector library is a single ECL file containing
     three MACROs. These steps explain how to install to your ECL source
     repository.</para>
 

docs/EN_US/HDFSConnector/HDFS_Mods/HDFS_Intro.xml

@@ -4,13 +4,13 @@
 <sect1 id="IntroHDFS" role="nobrk">
   <title>Introduction</title>
 
-  <para>The HDFS to HPCC Connector provides a means to import data from
+  <para>The HDFS to HPCC Systems<superscript>®</superscript> Connector provides a means to import data from
   Hadoop's HDFS into an HPCC Systems<superscript>®</superscript> Thor
   platform. It also supports exporting the data back to HDFS or exporting and
   merging it. This allows you to use an HPCC cluster in conjunction with your
   Hadoop-based cluster.</para>
 
-  <para>The H2H Connector is an add-on to an HPCC Cluster and consists of
+  <para>The H2H Connector is an add-on to an HPCC Systems Cluster and consists of
   server-side components and ECL Macros that invoke them.</para>
 
   <para><itemizedlist>
@@ -45,7 +45,7 @@
                     <para>The HDFS Connector writes log files to a folder
                     named <emphasis
                     role="bluebold">mydataconnectors</emphasis> in the the
-                    HPCC log directory (the HPCC log location can be set using
+                    HPCC Systems log directory (the HPCC Systems log location can be set using
                     Configuration Manager). </para>
 
                     <para>The default location is:<programlisting>/var/log/HPCCSystems/mydataconnectors/</programlisting></para>
@@ -88,7 +88,7 @@
       </listitem>
 
       <listitem>
-        <para>The HDFS to HPCC Connector User's Guide</para>
+        <para>The HDFS to HPCC Systems Connector User's Guide</para>
       </listitem>
     </itemizedlist></para>
 </sect1>

docs/EN_US/HDFSConnector/HDFS_Mods/HDFS_PipeOut.xml

@@ -64,7 +64,7 @@
 
   <para>The <emphasis role="bold">HDFSConnector.Pipeout </emphasis>macro
   writes the given <emphasis>ECL_RS</emphasis> recordset to the target HDFS
-  system in file parts -- one file part for each HPCC Thor node. You can then
+  system in file parts -- one file part for each HPCC Systems Thor node. You can then
   use other means to merge the file parts or you can use <emphasis
   role="bold">HDFSConnector.PipeOutAndMerge</emphasis> to do both
   tasks.</para>

docs/EN_US/HDFSConnector/HDFS_to_HPCC_ConnectorIncluder.xml

@@ -3,7 +3,7 @@
 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
 <book xml:base="../">
   <bookinfo>
-    <title>HDFS to HPCC Connector User's Guide</title>
+    <title>HDFS to HPCC Systems<superscript>®</superscript> Connector User's Guide</title>
 
     <mediaobject>
       <imageobject>

docs/EN_US/HPCCCertify/Cert-Mods/CertSprayDespray.xml

@@ -204,7 +204,7 @@
     <sect2 id="Spray_the_Data_File_to_your_DR-THOR_Cluster">
       <title>Spray a Data File to your Thor Cluster</title>
 
-      <para>To use a data file in our HPCC cluster, we must first "spray" it
+      <para>To use a data file in our HPCC Systems cluster, we must first "spray" it
       to a Thor cluster. A <emphasis>spray</emphasis> or
       <emphasis>import</emphasis> is the relocation of a data file from one
       location to a Thor cluster. The term spray was adopted due to the nature

docs/EN_US/HPCCCertify/certify.xml

@@ -2,7 +2,7 @@
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
 <book lang="en_US" xml:base="../">
-  <title>HPCC Preflight and Certification</title>
+  <title>HPCC Systems<superscript>®</superscript> Preflight and Certification</title>
 
   <bookinfo>
     <mediaobject>
@@ -63,10 +63,10 @@ Copyright is used for the copyright line on title page. The ID attribute is Copy
   <chapter id="certification_approach">
     <title>Introduction : Certification Approach</title>
 
-    <para>This document provides steps you can use to certify your HPCC
+    <para>This document provides steps you can use to certify your HPCC Systems<superscript>®</superscript> 
     environment.</para>
 
-    <para>Use this procedure when you create a new HPCC system or after you
+    <para>Use this procedure when you create a new HPCC Systems instance or after you
     make any changes or upgrades to the system. This will ensure that your
     system is functioning properly.</para>
 

docs/EN_US/HPCCClientTools/CT_Mods/CT_Comm_Line_DFU.xml

@@ -326,7 +326,7 @@ replicate=1</programlisting>
 
           <para>The <emphasis role="bold">spray</emphasis>
           <emphasis>operation</emphasis> copies a file from the landing zone,
-          distributing it across all the nodes of the destination HPCC.</para>
+          distributing it across all the nodes of the destination HPCC Systems cluster.</para>
 
           <para>These <emphasis>options </emphasis>are used by the <emphasis
           role="bold">spray</emphasis> <emphasis>operation</emphasis>:</para>
@@ -366,7 +366,7 @@ replicate=1</programlisting>
                     have been obtained by previous use of the savexml
                     <emphasis>operation</emphasis>. This option provides the
                     feature of combining multiple source files into a single
-                    resulting logical file in the HPCC.</entry>
+                    resulting logical file in the HPCC Systems cluster.</entry>
                   </row>
 
                   <row>
@@ -731,7 +731,7 @@ dfuplus action=dspray srcname=le::imagedb
           nodes.</para>
 
           <para>The copy operation can also be used to copy files from other
-          HPCC environments (using the <emphasis>srcdali</emphasis> option).
+          HPCC Systems environments (using the <emphasis>srcdali</emphasis> option).
           This is also known as a remote copy. For a remote copy of a file
           that contains a variable length field, you must include the
           <emphasis role="bold">nosplit</emphasis> option.</para>

docs/EN_US/HPCCClientTools/CT_Mods/CT_ECL_CLI.xml

@@ -289,7 +289,7 @@ ecl deploy roxie - --name=FindPersonService
                 <row>
                   <entry>ecl deploy</entry>
 
-                  <entry>Creates a workunit on the HPCC system from the given
+                  <entry>Creates a workunit on the HPCC Systems platform from the given
                   ECL text, file, archive, shared object, or dll. The workunit
                   is created in the <emphasis>compiled</emphasis>
                   state.</entry>
@@ -402,7 +402,7 @@ ecl deploy roxie - --name=FindPersonService
                 <row>
                   <entry>--ecl-only</entry>
 
-                  <entry>Send ECL query to HPCC as text rather than as a
+                  <entry>Send ECL query to HPCC Systems cluster as text rather than as a
                   generated archive</entry>
                 </row>
 
@@ -727,7 +727,7 @@ ecl publish roxie ArchiveQuery.xml --name=FindPersonService --no-activate
                 <row>
                   <entry>--ecl-only</entry>
 
-                  <entry>Send ECL query to HPCC as text rather than as a
+                  <entry>Send ECL query to HPCC Systems cluster as text rather than as a
                   generated archive</entry>
                 </row>
 
@@ -1111,7 +1111,7 @@ ecl run thor findperson.ecl -I C:\MyECL\
                 <row>
                   <entry>--ecl-only</entry>
 
-                  <entry>Send ECL query to HPCC as text rather than as a
+                  <entry>Send ECL query to HPCC Systems cluster as text rather than as a
                   generated archive</entry>
                 </row>
 
@@ -1690,7 +1690,7 @@ ecl queries copy //192.168.1.10:8010/thor/findperson thor
                   <entry>ecl queries copy</entry>
 
                   <entry>Copies a query from one queryset to another. A query
-                  can be copied from one HPCC environment to another by using
+                  can be copied from one HPCC Systems environment to another by using
                   a path which begins with '//' followed by the IP or hostname
                   and Port of the source ECL Watch and then followed by the
                   source queryset and query.</entry>

docs/EN_US/HPCCClientTools/CT_Mods/CT_ECL_IDE.xml

@@ -202,7 +202,7 @@
               compiler matches each server you need to access. Check the
               <emphasis role="bold">Override Automatic Compiler
               Selection</emphasis> checkbox and specify the Complier that
-              matches your HPCC instance.</para>
+              matches your HPCC Systems instance.</para>
 
               <para><graphic fileref="../../images/CT03a.jpg" /></para>
             </listitem>
@@ -296,7 +296,7 @@
           to a new configuration file. All available configuration files are
           shown on the <emphasis role="bold">Configurations</emphasis> drop
           list when you log in and you simply select the one you want ECL IDE
-          to use to connect to an HPCC environment.</para>
+          to use to connect to an HPCC Systems environment.</para>
 
           <informaltable colsep="1" frame="all" rowsep="1">
             <tgroup cols="2">
@@ -754,7 +754,7 @@
         displays.<itemizedlist>
             <listitem>
               <para>If you have created a configuration file to connect to the
-              desired HPCC environment, select it from the <emphasis
+              desired HPCC Systems environment, select it from the <emphasis
               role="bold">Configurations</emphasis> drop list. If not, press
               the <emphasis role="bold">Preferences</emphasis>button to create
               one.</para>
@@ -1266,7 +1266,7 @@
           <title>Error Log Toolbox</title>
 
           <para>The Error Log toolbox displays errors and warnings from the
-          HPCC system.</para>
+          HPCC Systems platform.</para>
 
           <para>For example, attempting to create an ECL file in a folder
           without WRITE permission will display an access denied error as

docs/EN_US/HPCCClientTools/CT_Mods/CT_ESDL_CLI.xml

@@ -250,7 +250,7 @@
               <row>
                 <entry><emphasis>-cde </emphasis></entry>
 
-                <entry>Specifies the HPCC Component files directory (location
+                <entry>Specifies the HPCC Systems Component files directory (location
                 of xslt files).</entry>
               </row>
 

docs/EN_US/HPCCClientTools/CT_Mods/CT_Overview.xml

@@ -5,7 +5,7 @@
   <title>Overview</title>
 
   <para>This manual contains documentation for the set of Client Tools for use
-  with the LexisNexis HPCC. These tools include:</para>
+  with the HPCC Systems platform. These tools include:</para>
 
   <informaltable colsep="1" frame="all" rowsep="1">
     <tgroup cols="2">
@@ -181,7 +181,7 @@
     <sect2 id="WinPath" role="brk">
       <title>Client Tools and the Windows Path</title>
 
-      <para>The HPCC Client tools are designed to allow you to have more than
+      <para>The HPCC Systems Client tools are designed to allow you to have more than
       one version installed. For that reason, the choice to add the folder of
       executable files to your system path is optional during
       installation.</para>

docs/EN_US/HPCCClientTools/CT_Mods/CT_Overview_withoutIDE.xml

@@ -5,7 +5,7 @@
   <title>Overview</title>
 
   <para>This manual contains documentation for the set of Client Tools for use
-  with the LexisNexis HPCC. These tools include:</para>
+  with the HPCC Systems platform. These tools include:</para>
 
   <informaltable colsep="0" frame="none" rowsep="0">
     <tgroup cols="2">

docs/EN_US/HPCCClientTools/CT_Mods/ECLCC.xml

@@ -55,8 +55,8 @@
     <title>ECL Compiler</title>
 
     <para>The ECL Compiler is the compiler component of the High Performance
-    Computing Cluster (HPCC). It is embedded and included when you install the
-    HPCC. The compiler is the component that actually compiles the ECL
+    Computing Cluster (HPCC) Systems platform. It is embedded and included when you install the
+    HPCC Systems platform. The compiler is the component that actually compiles the ECL
     code.</para>
 
     <para>The syntax and many of the compiler options implemented are similar

docs/EN_US/HPCCClientTools/ClientTools.xml

@@ -3,7 +3,7 @@
 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
 <book lang="en_US" xml:base="../">
   <bookinfo>
-    <title>HPCC Client Tools</title>
+    <title>HPCC Systems<superscript>®</superscript> Client Tools</title>
 
     <mediaobject>
       <imageobject>

docs/EN_US/HPCCClientTools/TheECLIDEandHPCCClientTools.xml

@@ -3,7 +3,7 @@
 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
 <book lang="en_US" xml:base="../">
   <bookinfo>
-    <title>The ECL IDE and HPCC Client Tools</title>
+    <title>The ECL IDE and HPCC Systems<superscript>®</superscript> Client Tools</title>
 
     <mediaobject>
       <imageobject>

docs/EN_US/HPCCDataHandling/DH-Mods/DH-Mod1.xml

@@ -37,15 +37,15 @@
   <sect1 id="Working_with_a_data_file">
     <title>Working with data files</title>
 
-    <para>Once you start working with your HPCC system, you will want to
+    <para>Once you start working with your HPCC Systems platform, you will want to
     process some real data, this section shows you how to load data to your
-    HPCC system.</para>
+    HPCC Systems platform.</para>
 
     <sect2 id="Cautions_and_Warnings">
       <title>Before you begin</title>
 
       <para>First, you should consider the size of the data and the capacity
-      of your system. A typical production HPCC system would have much more
+      of your system. A typical production HPCC Systems platform would have much more
       data capacity than a development system. The size of the files you wish
       to work with is limited by the size of your system.</para>
     </sect2>

docs/EN_US/HPCCDataHandling/DataHandling.xml

@@ -3,7 +3,7 @@
 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
 <book lang="en_US" xml:base="../">
   <bookinfo>
-    <title>HPCC Data Handling</title>
+    <title>HPCC Systems<superscript>®</superscript> Data Handling</title>
 
     <mediaobject>
       <imageobject>
@@ -62,13 +62,13 @@
   </bookinfo>
 
   <chapter id="Data_Handling">
-    <title><emphasis>HPCC Data Handling</emphasis></title>
+    <title><emphasis>HPCC Systems<superscript>®</superscript> Data Handling</emphasis></title>
 
     <sect1 id="Introduction" role="nobrk">
       <title>Introduction</title>
 
       <para>There are a number of different ways in which data may be
-      transferred to, from, or within an HPCC system. For each of these data
+      transferred to, from, or within an HPCC Systems cluster. For each of these data
       transfers, there are a few key parameters that must be known.</para>
 
       <sect2 id="Prerequisites-for-most-file-movements">
@@ -148,7 +148,7 @@
   </chapter>
 
   <chapter id="HPCC_DataBackups">
-    <title><emphasis>HPCC Data Backups</emphasis></title>
+    <title><emphasis>HPCC Systems<superscript>®</superscript> Data Backups</emphasis></title>
 
     <sect1 id="Introduction2DataBackup" role="nobrk">
       <title>Introduction</title>

docs/EN_US/HPCCDataTutorial/DataTutorial.xml

@@ -2,10 +2,10 @@
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
 <book lang="en_US" xml:base="../">
-  <title>HPCC Data Tutorial</title>
+  <title>HPCC Systems<superscript>®</superscript> Data Tutorial</title>
 
   <bookinfo>
-    <title>HPCC Data Tutorial</title>
+    <title>HPCC Systems<superscript>®</superscript> Data Tutorial</title>
 
     <mediaobject>
       <imageobject>
@@ -79,11 +79,11 @@
 
       <para>This tutorial provides a walk-through of the development process,
       from beginning to end, and is designed to be an introduction to working
-      with data on any HPCCSystems HPCC<footnote>
+      with data on any HPCC Systems platform. HPCC<footnote>
           <para><emphasis role="bold">H</emphasis>igh <emphasis
           role="bold">P</emphasis>erformance <emphasis
           role="bold">C</emphasis>omputing <emphasis
-          role="bold">C</emphasis>luster (HPCC) is a massively parallel
+          role="bold">C</emphasis>luster (HPCC) Systems is a massively parallel
           processing computing platform that solves Big Data problems. See
           http://www.hpccsystems.com/Why-HPCC/How-it-works for more
           details.</para>
@@ -92,7 +92,7 @@
           role="bold">C</emphasis>ontrol <emphasis
           role="bold">L</emphasis>anguage (ECL) is a declarative, data centric
           programming language used to manage all aspects of the massive data
-          joins, sorts, and builds that truly differentiate HPCC (High
+          joins, sorts, and builds that truly differentiate HPCC Systems (High
           Performance Computing Cluster) from other technologies in its
           ability to provide flexible data analysis on a massive scale.</para>
         </footnote>to process our data and query it.</para>
@@ -101,8 +101,8 @@
 
       <itemizedlist>
         <listitem>
-          <para>You have a running HPCC. This can be a VM Edition or a single
-          or multinode HPCC platform</para>
+          <para>You have a running HPCC Systems platform. This can be a VM Edition or a single
+          or multinode HPCC Systems platform</para>
         </listitem>
       </itemizedlist>
 
@@ -127,11 +127,11 @@
         </listitem>
 
         <listitem>
-          <para>Spray the file to a Data Refinery cluster HPCC clusters
+          <para>Spray the file to a Data Refinery cluster HPCC Systems clusters
           "spray" data into file parts on each node.</para>
 
           <para>A <emphasis>spray</emphasis> or <emphasis>import</emphasis> is
-          the relocation of a data file from one location to an HPCC cluster.
+          the relocation of a data file from one location to an HPCC Systems cluster.
           The term spray was adopted due to the nature of the file movement --
           the file is partitioned across all nodes within a cluster.</para>
         </listitem>
@@ -172,7 +172,7 @@
       <title>The Original Data</title>
 
       <para>In this scenario, we receive a structured data file containing
-      records with people's names and addresses. The HPCC also supports
+      records with people's names and addresses. The HPCC Systems platform also supports
       unstructured data, but this example is simpler. This file is documented
       in the following table:</para>
 
@@ -270,7 +270,7 @@
         running on that server to enable file sprays and desprays.</para>
 
         <para>For smaller data files, you can use the upload/download file
-        utility in ECL Watch (a Web-based interface to your HPCC platform).
+        utility in ECL Watch (a Web-based interface to your HPCC Systems platform).
         The sample data file is ~100 mb.</para>
 
         <orderedlist>
@@ -295,7 +295,7 @@
             Watch</emphasis> URL. For example, http://nnn.nnn.nnn.nnn:8010,
             where nnn.nnn.nnn.nnn is your ESP<footnote>
                 <para>The ESP (Enterprise Services Platform) Server is the
-                communication layer server in you HPCC environment.</para>
+                communication layer server in you HPCC Systems environment.</para>
               </footnote> Server's IP address.</para>
 
             <para><informaltable colsep="1" frame="all" rowsep="1">
@@ -386,7 +386,7 @@
       <sect2 id="Spray_the_Data_File_to_your_DR-THOR_Cluster">
         <title>Spray the Data File to your Thor Cluster</title>
 
-        <para>To use the data file in our HPCC cluster, we must first "spray"
+        <para>To use the data file in our HPCC Systems cluster, we must first "spray"
         it to a Thor cluster. A <emphasis>spray</emphasis> or
         <emphasis>import</emphasis> is the relocation of a data file from one
         location to a Thor cluster. The term spray was adopted due to the

docs/EN_US/HPCCMonitoring/HPCCMonitoringAndReporting.xml

@@ -3,7 +3,7 @@
 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
 <book lang="en_US" xml:base="../">
   <bookinfo>
-    <title>HPCC Monitoring and Reporting (Technical Preview)</title>
+    <title>HPCC Systems<superscript>®</superscript> Monitoring and Reporting (Technical Preview)</title>
 
     <mediaobject>
       <imageobject>
@@ -69,7 +69,7 @@
 
     <para><emphasis role="bold">Ganglia:</emphasis></para>
 
-    <para>The HPCC monitoring component leverages Ganglia, an open source,
+    <para>The HPCC Systems monitoring component leverages Ganglia, an open source,
     scalable, distributed monitoring system to display system information in a
     graphical manner.</para>
 
@@ -106,12 +106,12 @@
 
     <para><emphasis role="bold">Nagios</emphasis></para>
 
-    <para>The HPCC reporting and alerting component leverages Nagios, a
+    <para>The HPCC Systems reporting and alerting component leverages Nagios, a
     powerful monitoring and notification system, which can help you identify
     and resolve infrastructure problems before they affect critical
     processes.</para>
 
-    <para>With the HPCC reporting and alerting component you can set up alerts
+    <para>With the HPCC Systems reporting and alerting component you can set up alerts
     to inform of any changes to:</para>
 
     <para><itemizedlist>
@@ -156,7 +156,7 @@
   <chapter id="Ganglya_Overview">
     <title>Ganglia</title>
 
-    <para>The HPCC Monitoring component leverages Ganglia, an open source,
+    <para>The HPCC Systems monitoring component leverages Ganglia, an open source,
     scalable, distributed monitoring system, to produce a graphical view of a
     Roxie cluster's servers. Ganglia leverages widely accepted technologies
     for data representation. It provides near real-time monitoring and
@@ -236,23 +236,23 @@
         <emphasis>/etc/ganglia/conf.d</emphasis> and
         <emphasis>/etc/ganglia/.pyconf</emphasis> files in place and then add
         the Roxie nodes you wish to monitor. You can do that by installing the
-        Ganglia components and HPCC Monitoring components on to each Roxie
+        Ganglia components and HPCC Systems Monitoring components on to each Roxie
         node.</para>
 
         <para>If you do not have Ganglia, or want to install it, read the
         Ganglia documentation provided at the above link, and install it and
         any system dependencies. You will then need to download and install
-        the HPCC Monitoring component.</para>
+        the HPCC Systems Monitoring component.</para>
 
         <sect3 id="Installing-HPCCGanglia" role="brk">
-          <title>Installing the HPCC Monitoring component</title>
+          <title>Installing the HPCC Systems Monitoring component</title>
 
-          <para>The HPCC Monitoring component is available for download. The
-          HPCC Monitoring components leverage the Ganglia monitoring tools,
+          <para>The HPCC Systems Monitoring component is available for download. The
+          HPCC Systems Monitoring components leverage the Ganglia monitoring tools,
           and would only be needed if you do not already have Ganglia
           monitoring components on your system.</para>
 
-          <para>To get the HPCC Monitoring components, find the appropriate
+          <para>To get the HPCC Systems Monitoring components, find the appropriate
           package for your system.</para>
 
           <para>Packages are available for download from the HPCC
@@ -283,14 +283,14 @@
     </sect1>
 
     <sect1 id="HPCC_Viewer">
-      <title>The HPCC Ganglia Viewer</title>
+      <title>The HPCC Systems Ganglia Viewer</title>
 
       <para>A Ganglia viewer comes preinstalled and configured in the 4.2.x
-      (or later) HPCC Virtual Machine. The monitoring provided with the
+      (or later) HPCC Systems Virtual Machine. The monitoring provided with the
       Virtual Machine is set up to monitor Roxie instances on the network.
       This document introduces the monitoring and describes how to get it
       working on your system. <figure>
-          <title>HPCC Monitoring</title>
+          <title>HPCC Systems Monitoring</title>
 
           <mediaobject>
             <imageobject>
@@ -331,7 +331,7 @@
       implement them on a larger system, is to examine the metrics in
       action.</para>
 
-      <para>Ganglia integration is built into the current HPCC Virtual Machine
+      <para>Ganglia integration is built into the current HPCC Systems Virtual Machine
       images. Download and start up a virtual image and look at how the
       monitoring component works.</para>
 
@@ -363,7 +363,7 @@
     </sect1>
 
     <sect1 id="GangliaIntegration">
-      <title>Ganglia Integration with HPCC</title>
+      <title>Ganglia Integration with HPCC Systems</title>
 
       <para>The Roxie nodes are able to report metrics to Ganglia when the
       nodes have Ganglia monitoring and the associated dependencies
@@ -391,7 +391,7 @@
         </listitem>
 
         <listitem>
-          <para>Deploy the monitoring daemon (gmond) and the HPCC Monitoring
+          <para>Deploy the monitoring daemon (gmond) and the HPCC Systems Monitoring
           package to each of the nodes you wish to monitor.</para>
         </listitem>
       </orderedlist>
@@ -400,7 +400,7 @@
       more Roxie nodes installed anywhere on the same network utilizing
       multi-cast.</para>
 
-      <para>To add a new Roxie node, install the HPCC Monitoring package on to
+      <para>To add a new Roxie node, install the HPCC Systems Monitoring package on to
       each Roxie node to monitor. In most basic configurations you may need to
       add the node(s) IP address(es) to the
       <emphasis>/etc/ganglia/gmetad.conf</emphasis> file. As long as the new
@@ -424,7 +424,7 @@
     <sect1 id="GangliaInECLWatch">
       <title>Ganglia in ECL Watch</title>
 
-      <para>With the Ganglia for HPCC Plugin installed. You can view the
+      <para>With the Ganglia for HPCC Systems Plugin installed. You can view the
       Ganglia statistics and graphs right through the ECL Watch interface. The
       out of the box monitoring displays several key statistics by default.
       You can customize and configure the views.</para>
@@ -451,7 +451,7 @@
         <para>In order to get the Ganglia in ECL Watch, You need to have
         Ganglia on your HPCC Systems. <orderedlist>
             <listitem>
-              <para>Install or ensure you have the HPCC Monitoring components
+              <para>Install or ensure you have the HPCC Systems Monitoring components
               on a node where ECL Watch is installed.</para>
             </listitem>
 
@@ -502,14 +502,14 @@
   <chapter id="HPCC_Nagios_Chapter">
     <title>Nagios</title>
 
-    <para>The HPCC Reporting component leverages Nagios, an open source,
+    <para>The HPCC Systems Reporting component leverages Nagios, an open source,
     system and network infrastructure monitoring application to monitor and
-    alert HPCC Administrators. Nagios leverages established and accepted open
+    alert HPCC Systems Administrators. Nagios leverages established and accepted open
     source technologies to alert users to changes or potential issues. Nagios
     provides regular periodic system monitoring and reporting.</para>
 
-    <para>With the HPCC integration, you can generate Nagios configuration
-    files to monitor HPCC server health. Once the Nagios is configured, you
+    <para>With the HPCC Systems integration, you can generate Nagios configuration
+    files to monitor HPCC Systems server health. Once the Nagios is configured, you
     can monitor:<itemizedlist>
         <listitem>
           <para>Disk Usage</para>
@@ -569,12 +569,12 @@
       <title>Nagios Introduction</title>
 
       <para>Nagios is a powerful monitoring and notification system, which can
-      be used with HPCC to help identify and resolve infrastructure problems
+      be used with HPCC Systems to help identify and resolve infrastructure problems
       before they affect critical processes. Nagios hardware notifications can
       help keep your system highly available and alerts can assist in
       pre-emptive maintenance for processes which are down or behaving outside
       expected parameters to ensure system stability, reliability, and uptime.
-      Scripts and tools are provided to extract HPCC Platform system metrics
+      Scripts and tools are provided to extract HPCC Systems platform system metrics
       and easily integrate that data into Nagios.</para>
 
       <para>Administrators should note that different platforms may not
@@ -596,7 +596,7 @@
           </listitem>
 
           <listitem>
-            <para>Review our HPCC Monitoring and Reporting documentation in
+            <para>Review our HPCC Systems Monitoring and Reporting documentation in
             its entirety.</para>
           </listitem>
 
@@ -623,11 +623,11 @@
       implement it on a larger system, is to examine an established session in
       action.</para>
 
-      <para>Nagios integration is built into the current HPCC Virtual Machine
+      <para>Nagios integration is built into the current HPCC Systems Virtual Machine
       images. Download and start up a virtual image and look at how the
       monitoring component works.</para>
 
-      <para>The Nagios component for HPCC on the VM allows you:</para>
+      <para>The Nagios component for HPCC Systems on the VM allows you:</para>
 
       <itemizedlist>
         <listitem>
@@ -745,26 +745,26 @@
     <sect1 id="NagiosInstallation">
       <title>Installation of Nagios</title>
 
-      <para>The HPCC Nagios package provides tools and utilities for
-      generating Nagios configurations. These configurations check HPCC and
-      perform some of the HPCC specific checks. HPCC Nagios installation is
+      <para>The HPCC Systems Nagios package provides tools and utilities for
+      generating Nagios configurations. These configurations check HPCC Systems and
+      perform some of the HPCC Systems specific checks. HPCC Systems Nagios installation is
       provided on the HPCC Systems<superscript>®</superscript> portal.</para>
 
       <sect2 id="HPCC_Nagios_Installation">
-        <title>HPCC Nagios Installation Package</title>
+        <title>HPCC Systems Nagios Installation Package</title>
 
-        <para>To get the HPCC Nagios monitoring on your system you need the
+        <para>To get the HPCC Systems Nagios monitoring on your system you need the
         Installation package. Download the installation package from the HPCC
         Systems portal.</para>
 
         <para>The HPCC Systems<superscript>®</superscript> web portal is where
-        you can find HPCC resources, downloads, plugins, as well as helpful
+        you can find HPCC Systems resources, downloads, plugins, as well as helpful
         information.</para>
 
         <para><ulink
         url="http://hpccsystems.com/download/free-community-edition/monitoring">http://hpccsystems.com/</ulink></para>
 
-        <para>You can find the HPCC Monitoring and Reporting Installation
+        <para>You can find the HPCC Systems Monitoring and Reporting Installation
         packages at:</para>
 
         <para><ulink
@@ -777,7 +777,7 @@
       <sect2 id="HPCC_InstallNagios" role="brk">
         <title>Install Nagios</title>
 
-        <para>To Install Nagios for HPCC, you must have HPCC System platform
+        <para>To Install Nagios for HPCC Systems, you must have HPCC Systems platform
         installed and also have the open-source Nagios package
         installed.</para>
 
@@ -789,7 +789,7 @@
               Nagios monitoring must have network connectivity to all the
               monitored nodes.</para>
 
-              <para>With the hpcc-nagios tools installed, you have HPCC check
+              <para>With the hpcc-nagios tools installed, you have HPCC Systems check
               utilities in:</para>
 
               <para><programlisting> /usr/lib/nagios/plugins/ </programlisting></para>
@@ -804,7 +804,7 @@
               configurations. The generated configurations can be modified
               with optional flags to fit the environment that is being
               monitored. The default package also provides some utilities to
-              monitor HPCC processes such as Roxies, ESP Services by node and
+              monitor HPCC Systems processes such as Roxies, ESP Services by node and
               port, Dali, and dafilesrv. Other processes could also be
               monitored if a check utility is provided and the generated
               config file is modified (find/replace all would probably
@@ -936,7 +936,7 @@
                   <row>
                     <entry>-e or -env</entry>
 
-                    <entry>hpcc environment configuration file</entry>
+                    <entry>HPCC Systems environment configuration file</entry>
 
                     <entry>/etc/HPCCSystems/environment.xml</entry>
                   </row>
@@ -1467,7 +1467,7 @@
         <sect3 id="HPCC_NagiosHelp">
           <title>Help</title>
 
-          <para>For help with HPCC Nagios enter:</para>
+          <para>For help with HPCC Systems Nagios enter:</para>
 
           <programlisting> /opt/HPCCSystems/bin/hpcc-nagios-tools</programlisting>
 

docs/EN_US/HPCCMonitoring/MonRep-Mods/MonRep-VM.xml

@@ -2,10 +2,10 @@
 <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
 <sect2 id="get_hpcc">
-  <title>Get the latest HPCC Virtual Image File</title>
+  <title>Get the latest HPCC Systems<superscript>®</superscript> Virtual Image File</title>
 
-  <para>The complete details for installing and running HPCC in a virtual
-  machine are available in the document: <emphasis role="bold">Running HPCC in
+  <para>The complete details for installing and running HPCC Systems in a virtual
+  machine are available in the document: <emphasis role="bold">Running HPCC Systems in
   a Virtual Machine</emphasis>, available from <ulink
   url="hpccsystems.com/download/docs">http://hpccsystems.com/download/docs</ulink>
   .</para>
@@ -15,7 +15,7 @@
 
   <para><orderedlist>
       <listitem>
-        <para>Download the latest HPCC Virtual Machine image file from:</para>
+        <para>Download the latest HPCC Systems Virtual Machine image file from:</para>
 
         <para><ulink
         url="http://HPCCsystems.com/download/hpcc-vm-image">http://hpccsystems.com/download/hpcc-vm-image</ulink></para>

docs/EN_US/HPCCSystemAdmin/HPCCSystemAdministratorsGuide.xml

@@ -2,10 +2,10 @@
 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
 <book xml:base="../">
-  <title>HPCC System Administrator's Guide</title>
+  <title>HPCC Systems<superscript>®</superscript> Administrator's Guide</title>
 
   <bookinfo>
-    <title>HPCC System Administrator's Guide</title>
+    <title>HPCC  Systems<superscript>®</superscript> Administrator's Guide</title>
 
     <mediaobject>
       <imageobject>
@@ -70,14 +70,14 @@
     <sect1 id="HPCC_SysAdminIntro" role="nobrk">
       <title>Introduction</title>
 
-      <para>HPCC (High Performance Computing Cluster) is a massive
+      <para>HPCC (High Performance Computing Cluster) Systems is a massive
       parallel-processing computing platform that solves Big Data
       problems.</para>
 
-      <para>HPCC stores and processes large quantities of data, processing
+      <para>HPCC Systems platform stores and processes large quantities of data, processing
       billions of records per second using massive parallel processing
       technology. Large amounts of data across disparate data sources can be
-      accessed, analyzed, and manipulated in fractions of seconds. HPCC
+      accessed, analyzed, and manipulated in fractions of seconds. HPCC Systems
       functions as both a processing and a distributed data storage
       environment, capable of analyzing terabytes of information.</para>
     </sect1>
@@ -90,7 +90,7 @@
       Server, and ECLCC Server. LDAP security is optionally available.</para>
 
       <para><figure>
-          <title>HPCC Architectural Diagram</title>
+          <title>HPCC Systems Architectural Diagram</title>
 
           <mediaobject>
             <imageobject>
@@ -130,8 +130,8 @@
       <sect2 id="HPCC_Clusters" role="brk">
         <title>Clusters</title>
 
-        <para>HPCC environment contains clusters which you define and use
-        according to your needs. The types of clusters used in HPCC:</para>
+        <para>HPCC Systems environment contains clusters which you define and use
+        according to your needs. The types of clusters used by HPCC Systems:</para>
 
         <sect3 id="SysAdm_Thor_Cluster">
           <title>Thor</title>
@@ -178,7 +178,7 @@
         <title>System Servers</title>
 
         <para>The System Servers are integral middleware components of an HPCC
-        system. They are used to control workflow and inter-component
+        Systems platform. They are used to control workflow and inter-component
         communication.</para>
 
         <sect3 id="SysAdm_Dali">
@@ -195,7 +195,7 @@
           -clients</emphasis>)</para>
 
           <para>Another task Dali performs is to act as the locking manager.
-          HPCC uses Dali's locking manager to control shared and exclusive
+          HPCC Systems uses Dali's locking manager to control shared and exclusive
           locks to metadata.</para>
         </sect3>
 
@@ -340,7 +340,7 @@
         <title>Client Interfaces</title>
 
         <para>The following Client Interfaces are available to interact with
-        the HPCC Platform.</para>
+        the HPCC Systems platform.</para>
 
         <sect3 id="SysAdm_ECLIDE">
           <title>ECL IDE</title>
@@ -428,17 +428,17 @@
     <title>Hardware and Software Requirements</title>
 
     <para>This chapter describes some of the hardware and software
-    requirements in order to run the HPCC System. HPCC is designed to run on
+    requirements in order to run the HPCC Systems platform. HPCC Systems is designed to run on
     commodity hardware, which makes building and maintaining large scale
     (petabytes) clusters economically feasible. When planning your cluster
     hardware, you will need to balance a number of considerations specific to
     your needs.</para>
 
     <para>This section provides some insight into the hardware and
-    infrastructure that HPCC works well on. This is not an exclusive
+    infrastructure that HPCC Systems works well on. This is not an exclusive
     comprehensive set of instructions, nor a mandate on what hardware you must
     have. Consider this as a guide to use when looking to implement or scale
-    your HPCC system. These suggestions should be taken into consideration for
+    your HPCC Systems platform. These suggestions should be taken into consideration for
     your specific enterprise needs.</para>
 
     <xi:include href="Installing_and_RunningTheHPCCPlatform/Inst-Mods/Hardware.xml"
@@ -462,19 +462,19 @@
     <title>Hardware and Components</title>
 
     <para>This section provides some insight as to what sort of hardware and
-    infrastructure optimally HPCC works well on. This is not an exclusive
+    infrastructure optimally HPCC Systems works well on. This is not an exclusive
     comprehensive set of instructions, nor a mandate on what hardware you must
     have. Consider this as a guide to use when looking to implement or scale
-    your HPCC system. These suggestions should be taken into consideration for
+    your HPCC Systems platform. These suggestions should be taken into consideration for
     your specific enterprise needs.</para>
 
-    <para>HPCC is designed to run on commodity hardware, which makes building
+    <para>HPCC Systems is designed to run on commodity hardware, which makes building
     and maintaining large scale (petabytes) clusters economically feasible.
     When planning your cluster hardware, you will need to balance a number of
     considerations, including fail-over domains and potential performance
-    issues. Hardware planning should include distributing HPCC across multiple
+    issues. Hardware planning should include distributing HPCC Systems across multiple
     physical hosts, such as a cluster. Generally, one type of best practice is
-    to run HPCC processes of a particular type, for example Thor, Roxie, or
+    to run HPCC Systems processes of a particular type, for example Thor, Roxie, or
     Dali, on a host configured specifically for that type of process.</para>
 
     <sect1 id="SysAdm_ThorHW">
@@ -490,21 +490,21 @@
       larger physical servers to run multiple Thor slave nodes per physical
       server.</para>
 
-      <para>It is important to note that HPCC by nature is a parallel
+      <para>It is important to note that HPCC Systems by nature is a parallel
       processing system and all Thor slave nodes will be exercising at
-      precisely the same time. So when allocating more than one HPCC Thor
+      precisely the same time. So when allocating more than one HPCC Systems Thor
       slave per physical machine assure that each slave meets the recommended
       requirements.</para>
 
       <para>For instance, 1 physical server with 48 cores, 96GB RAM, 10Gb/sec
       network and 2GB/sec sequential I/O would be capable of running ten (10)
-      HPCC Thor slaves at optimal efficiency. The order of optimization for
+      HPCC Systems Thor slaves at optimal efficiency. The order of optimization for
       resource usage in a Thor slave node is disk I/O 60%, network 30%, and
       CPU 10%. Any increase in sequential I/O will have the most impact on
       speed, followed by improvements in network, followed by improvements in
       CPU.</para>
 
-      <para>Network architecture is also an important consideration. HPCC Thor
+      <para>Network architecture is also an important consideration. HPCC Systems Thor
       nodes work optimally in a streamlined network architecture between all
       Thor slave processes.</para>
 
@@ -516,18 +516,18 @@
     <sect1 id="SysAdm_RoxieHW">
       <title>Roxie Hardware Configurations</title>
 
-      <para>HPCC Roxie processes require require a proper, yet different (from
+      <para>HPCC Systems Roxie processes require require a proper, yet different (from
       Thor) balance of CPU, RAM, network, and disk I/O in order to ensure
-      efficient operations. A single HPCC Roxie node works optimally when
+      efficient operations. A single HPCC Systems Roxie node works optimally when
       allocated 6 or more CPU cores, 24GB RAM, 1Gb/sec network backbone, and
       400/sec 4k random read IOPS.</para>
 
-      <para>Each HPCC Roxie node is presented two hard drives, each capable of
+      <para>Each HPCC Systems Roxie node is presented two hard drives, each capable of
       200/sec 4k random seek IOPS. Hard drive recommendations for Roxie
       efficiency are 15K SAS, or SSD. A good rule of thumb is the more random
       read IOPS the better and faster your Roxie will perform.</para>
 
-      <para>Running multiple HPCC Roxie nodes on a single physical server is
+      <para>Running multiple HPCC Systems Roxie nodes on a single physical server is
       not recommended, except in the cases of virtualization or
       containers.</para>
 
@@ -541,12 +541,12 @@
     <sect1 id="SysAdm_Dali_Sasha">
       <title>Dali and Sasha Hardware Configurations</title>
 
-      <para>HPCC Dali processes store cluster metadata in RAM. For optimal
+      <para>HPCC Systems Dali processes store cluster metadata in RAM. For optimal
       efficiency, provide at least 48GB of RAM, 6 or more CPU cores, 1Gb/sec
-      network interface and a high availability disk for a single HPCC Dali.
-      HPCC's Dali processes are one of the few native active/passive
+      network interface and a high availability disk for a single HPCC Systems Dali.
+      The HPCC Systems Dali processes are one of the few native active/passive
       components. Using standard "swinging disk" clustering is recommended for
-      a high availability setup. For a single HPCC Dali process, any suitable
+      a high availability setup. For a single HPCC Systems Dali process, any suitable
       High Availability (HA) RAID level is fine.</para>
 
       <para>Sasha only stores data to locally available disks, reading data
@@ -626,7 +626,7 @@
     </sect1>
 
     <sect1 id="SysAdm_OtherHPCCcomponents">
-      <title>Other HPCC Components</title>
+      <title>Other HPCC Systems Components</title>
 
       <para>ECL Agent, ECLCC Server, DFU Server, the Thor master, and ECL
       Watch are administrative processes which are used for supporting
@@ -641,21 +641,21 @@
   <chapter id="Routine_Maintenance">
     <title>Routine Maintenance</title>
 
-    <para>In order to ensure that your HPCC system keeps running optimally,
+    <para>In order to ensure that your HPCC Systems platform keeps running optimally,
     some care and maintenance is required. The following sections address
-    routine maintenance tasks for your HPCC system.</para>
+    routine maintenance tasks for your HPCC Systems platform.</para>
 
     <!--***SYSTEM HEALTH CHECK UP***TO COME***-->
 
     <sect1 id="SysAdmin_DataHandling">
       <title>Data Handling</title>
 
-      <para>When you start working with your HPCC system, you will want to
+      <para>When you start working with your HPCC Systems platform, you will want to
       have some data on the system to process. Data gets transferred to the
-      HPCC system by a process called a spray. Likewise to get data out from
-      an HPCC system it must be desprayed.</para>
+      HPCC Systems platform by a process called a spray. Likewise to get data out from
+      an HPCC Systems platform it must be desprayed.</para>
 
-      <para>As HPCC is a computer cluster the data gets deployed out over the
+      <para>As the HPCC Systems platform is a computer cluster the data gets deployed out over the
       nodes that make up the cluster. A <emphasis>spray</emphasis> or import
       is the relocation of a data file from one location (such as a Landing
       Zone) to a cluster. The term spray was adopted due to the nature of the
@@ -677,8 +677,8 @@
       large files, you will need a tool that supports the secure copy
       protocol, something like a WinSCP.</para>
 
-      <para>For more information about HPCC data handling see the
-      <emphasis>HPCC Data Handling</emphasis> and the <emphasis>HPCC Data
+      <para>For more information about HPCC Systems data handling see the
+      <emphasis>HPCC Systems<superscript>®</superscript> Data Handling</emphasis> and the <emphasis>HPCC Systems<superscript>®</superscript> Data
       Tutorial</emphasis> documents.</para>
 
       <!--***CAN TIE THIS ALL TOGETHER - as part of routine maint. clean up some data files... archive data... etc. ***TO COME***-->
@@ -700,7 +700,7 @@
         place, by adding HPCC Systems<superscript>®</superscript> into your
         operating environment there are some additional considerations to be
         aware of. The following sections discuss backup considerations for the
-        individual HPCC system components.</para>
+        individual HPCC Systems components.</para>
 
         <sect3 id="SysAdm_BkU_Dali">
           <title>Dali</title>
@@ -796,7 +796,7 @@
 
           <para><emphasis role="bold">Backupnode</emphasis></para>
 
-          <para>Backupnode is a tool that is packaged with HPCC. Backupnode
+          <para>Backupnode is a tool that is packaged with HPCC Systems platform. Backupnode
           allows you to backup Thor nodes on demand or in a script. You can
           also use backupnode regularly in a crontab or by adding a backupnode
           component with Configuration Manager to your environment. You would
@@ -905,7 +905,7 @@
     <sect1 id="SysAdm_Log_Files">
       <title>Log Files</title>
 
-      <para>HPCC provides a wealth of information which can be used to debug,
+      <para>HPCC Systems provides a wealth of information which can be used to debug,
       track transactions, application performance, and troubleshooting
       purposes. You can review HPCC Systems messages as they are reported and
       captured in the log files. Log files can help you in understanding what
@@ -914,9 +914,9 @@
       <sect2 id="SysAdm_Component_Logs">
         <title>Component Logs</title>
 
-        <para>HPCC component files are written to <emphasis
+        <para>HPCC Systems component files are written to <emphasis
         role="bold">/var/log/HPCCSystems</emphasis> (default location). You
-        can optionally configure your HPCC system to write the logs to a
+        can optionally configure your HPCC Systems to write the logs to a
         different directory. You should know where the log files are, and
         refer to the logs first when troubleshooting any issues.</para>
 
@@ -935,7 +935,7 @@
         <!-- # JIRA 18201 #-->
 
         <para>Understanding the log files, and what is normally reported in
-        the log files, helps in troubleshooting the HPCC system.</para>
+        the log files, helps in troubleshooting HPCC Systems clusters.</para>
 
         <para>As part of routine maintenance you may want to backup, archive,
         and remove the older log files. Some log files can grow quite large
@@ -1040,7 +1040,7 @@
         <para>To view logs on ECL Watch, click on the <emphasis
         role="bold">Operations</emphasis> icon, then click on the <emphasis
         role="bold">System Servers</emphasis> link. That opens the System
-        Servers page in ECL Watch. There are several HPCC system components
+        Servers page in ECL Watch. There are several HPCC Systems components
         listed on that page. In the <emphasis role="bold">Directory</emphasis>
         column for each component there is a computer drive icon. Click the
         icon in the row for the component log you wish to view. <figure>
@@ -1115,9 +1115,9 @@
   <chapter id="OnDemand_Maintenance">
     <title>System Configuration and Management</title>
 
-    <para>The HPCC system requires configuration. The Configuration Manager
+    <para>HPCC Systems require configuration. The Configuration Manager
     tool (configmgr) included with the system software is a valuable piece of
-    setting up your HPCC system. The Configuration Manager is a graphical tool
+    setting up your HPCC Systems platform. The Configuration Manager is a graphical tool
     provided that can be used to configure your system. Configuration Manager
     has a wizard that you can run which will easily generate an environment
     file to get you configured, up and running quickly. There is an advanced
@@ -1169,9 +1169,9 @@
     <sect1 id="SysAdm_Env.conf">
       <title>Environment.conf</title>
 
-      <para>Another component of HPCC system configuration is the
+      <para>Another component of HPCC Systems configuration is the
       environment.conf file. Environment.conf contains some global definitions
-      that the configuration manager uses to configure the HPCC system. In
+      that the configuration manager uses to configure the HPCC Systems. In
       most cases, the defaults are sufficient.</para>
 
       <para><informaltable colsep="1" frame="all" rowsep="1">
@@ -1188,7 +1188,7 @@
 
                 <entry><emphasis role="bold">WARNING</emphasis>: These
                 settings are essential to proper system operation. Only expert
-                level HPCC administrators should attempt to change any aspects
+                level HPCC Systems administrators should attempt to change any aspects
                 of this file.</entry>
               </row>
             </tbody>
@@ -1198,8 +1198,8 @@
 
       <programlisting>/etc/HPCCSystems</programlisting>
 
-      <para>Environment.conf is required upon startup of HPCC. The
-      environment.conf is where the HPCC environment file is defined.</para>
+      <para>Environment.conf is required upon startup of the HPCC Systems platform. The
+      environment.conf is where the HPCC Systems environment file is defined.</para>
 
       <programlisting>/opt/HPCCSystems/environment.xml</programlisting>
 
@@ -1309,7 +1309,7 @@ classpath=/opt/HPCCSystems/classes
 runtime=/var/lib/HPCCSystems
 lock=/var/lock/HPCCSystems</programlisting>
 
-        <para>HPCC will not run properly without the proper paths, and in some
+        <para>The HPCC Systems platform will not run properly without the proper paths, and in some
         cases needs the absolute path. If a process or component can't find a
         path you will get an error message such as the following:</para>
 
@@ -1489,7 +1489,7 @@ lock=/var/lock/HPCCSystems</programlisting>
       <sect2 id="Using_nice">
         <title>Using nice</title>
 
-        <para>The HPCC platform supports <emphasis>nice</emphasis>-based
+        <para>The HPCC Systems platform supports <emphasis>nice</emphasis>-based
         priorities using the nice Linux utility which invokes scripts and
         programs with specified priorities. The priority assigned to a process
         indicates to the CPU to provide more or less time than to other
@@ -1497,7 +1497,7 @@ lock=/var/lock/HPCCSystems</programlisting>
         19 is the lowest.</para>
 
         <para>The default environment.conf file is delivered with the nice
-        value disabled. If you wish to use nice to prioritize HPCC processes,
+        value disabled. If you wish to use nice to prioritize HPCC Systems processes,
         you need to modify the environment.conf file to enable nice. You can
         also adjust the nice value in environment.conf.</para>
       </sect2>
@@ -1594,7 +1594,7 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
     <sect1 id="SystemD_initScripts">
       <title>Initialization under Systemd</title>
 
-      <para>The primary tool for starting and stopping the HPCC platform on a
+      <para>The primary tool for starting and stopping the HPCC Systems platform on a
       target machine using systemd is the
       <emphasis>hpccsystems-platform.target</emphasis>. This target script is
       dependent on the environment.xml file, and gets generated using the
@@ -1675,11 +1675,11 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
       <para>The performance of your system can vary depending on how some
       components interact. One area which could impact performance is the
       relationship with users, groups, and Active Directory. If possible,
-      having a separate Active Directory specific to HPCC could be a good
+      having a separate Active Directory specific to HPCC Systems could be a good
       policy. There have been a few instances where just one Active Directory
       servicing many, diverse applications has been less than optimal.</para>
 
-      <para>HPCC makes setting up your Active Directory OU's relatively easy.
+      <para>HPCC Systems makes setting up your Active Directory OU's relatively easy.
       ESP creates all the OU's for you when it starts up, based on the
       settings you defined in Configuration Manager. You can then start
       Dali/ESP and use ECLWatch to add or modify users or groups.</para>
@@ -1811,18 +1811,18 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
     <title>Best Practices</title>
 
     <para>This chapter outlines various forms of best practices established by
-    long time HPCC users and administrators running HPCC in a high
+    long time HPCC Systems users and administrators running HPCC Systems in a high
     availability, demanding production environment. While it is not required
     that you run your environment in this manner, as your specific
     requirements may vary. This section provides some best practice
-    recommendations established after several years of running HPCC in a
+    recommendations established after several years of running HPCC Systems in a
     demanding, intense, production environment.</para>
 
     <sect1 id="BP_Cluster_Redundancy" role="nobrk">
       <title>Cluster Redundancy</title>
 
       <para>There are several aspects of cluster redundancy that should be
-      considered when setting up your HPCC system.</para>
+      considered when setting up your HPCC Systems platform.</para>
 
       <para><informaltable colsep="1" frame="all" rowsep="1">
           <?dbfo keep-together="always"?>
@@ -1940,11 +1940,11 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
     <sect1 id="BP_High_Availability">
       <title>High Availability</title>
 
-      <para>If you require high availability for your HPCC system, there are
+      <para>If you require high availability for your HPCC Systems platform, there are
       some additional considerations that you should be aware of. This is not
       comprehensive list, and it is not meant to be step-by-step instructions
       for setting up disaster recovery. Instead this section just provides
-      some more information to consider when incorporating HPCC into your
+      some more information to consider when incorporating HPCC Systems into your
       disaster recovery plan.</para>
 
       <sect2 id="Thor_HA">
@@ -2073,7 +2073,7 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
       <para>There are several other aspects to best practice considerations,
       and these will change with your system requirements. The following
       sections are some best practice considerations for some aspects of the
-      HPCC system. Keep in mind that suggested best practices are merely
+      HPCC Systems platform. Keep in mind that suggested best practices are merely
       suggested and may not be appropriate for your needs. A thorough review
       of the considerations highlighted here can be very helpful if your needs
       align with the stated considerations.</para>
@@ -2253,7 +2253,7 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
             </mediaobject>
           </figure></para>
 
-        <para>Open up the HPCC Configuration Manager and proceed to the
+        <para>Open up the HPCC Systems Configuration Manager and proceed to the
         Advanced View option. For more information about using ConfigMgr see
         Using Configuration Manager. <orderedlist>
             <listitem>
@@ -2291,7 +2291,7 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
         configured to take full advantage of the resources available per node
         using Virtual Thor slaves.</para>
 
-        <para>In HPCC versions prior to 6.0.0, cluster configurations were
+        <para>In HPCC Systems platform versions prior to 6.0.0, cluster configurations were
         typically set to N number of <emphasis
         role="bold">slavesPerNode</emphasis><indexterm>
             <primary>slavesPerNode</primary>
@@ -2461,7 +2461,7 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
         <para>Thor, Roxie, and ECL Agent clusters all have options in the
         configuration to enable huge page support. The Transparent Huge Pages
         are enabled for Thor, Roxie, and ECL Agent clusters in the default
-        HPCC environment. Thor clusters can stand to benefit more from huge
+        HPCC Systems environment. Thor clusters can stand to benefit more from huge
         pages than can Roxie.</para>
 
         <para>You can check the file
@@ -2480,7 +2480,7 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
           "hugepages=N" parameter at boot. With huge pages you also need to
           explicitly allocate the size.</para>
 
-          <para>In HPCC, there are three places in the configuration manager
+          <para>In HPCC Systems, there are three places in the configuration manager
           to set the attributes to use Huge Pages.</para>
 
           <para>There are attributes in each component, in the ECL Agent
@@ -2491,7 +2491,7 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
 heapUseTransparentHugePages</programlisting>
 
           <para>Enable Huge Pages in your operating system, then configure
-          HPCC for the component(s) you wish.</para>
+          HPCC Systems for the component(s) you wish.</para>
         </sect3>
       </sect2>
     </sect1>
@@ -2508,10 +2508,10 @@ heapUseTransparentHugePages</programlisting>
   <chapter id="Resources">
     <title>System Resources</title>
 
-    <para>There are additional resources available for the HPCC System.</para>
+    <para>There are additional resources available for the HPCC Systems System.</para>
 
     <sect1 id="HPCC_Resources" role="nobrk">
-      <title>HPCC Resources</title>
+      <title>HPCC Systems Resources</title>
 
       <para>The resources link can be found under the Operations Icon link.
       The resources link in ECL Watch provides a link to the HPCC
@@ -2519,10 +2519,10 @@ heapUseTransparentHugePages</programlisting>
       Systems<superscript>®</superscript> Web Portal at <ulink
       url="http://hpccsystems.com/">http://hpccsystems.com/</ulink> for
       software updates, plugins, support, documentation, and more. This is
-      where you can find resources useful for running and maintaining HPCC on
+      where you can find resources useful for running and maintaining HPCC Systems on
       the web portal.</para>
 
-      <para>ECL Watch provides a link to the HPCC portal's download page:
+      <para>ECL Watch provides a link to the HPCC Systems portal's download page:
       <ulink
       url="http://hpccsystems.com/download">http://hpccsystems.com/download</ulink>.
       This is the page where you can download Installation packages, virtual
@@ -2532,7 +2532,7 @@ heapUseTransparentHugePages</programlisting>
     <sect1 id="SysAdm_Addl_Resources">
       <title>Additional Resources</title>
 
-      <para>Additional help with HPCC and Learning ECL is also available.
+      <para>Additional help with HPCC Systems and Learning ECL is also available.
       There are online courses available. Go to :</para>
 
       <para><ulink

docs/EN_US/HPCCSystemAdmin/SA-Mods/CassandraWUServer.xml

@@ -4,19 +4,19 @@
 <sect1 id="CassandraWUStorage">
   <title>Using Cassandra for Workunit Storage</title>
 
-  <para>Beginning with version 6.0.0, you can configure your system to use
+  <para>Beginning with HPCC Systems<superscript>®</superscript> version 6.0.0, you can configure your system to use
   Apache <trademark>Cassandra</trademark> database for Workunit storage.
   Apache's Cassandra NoSQL data store is a software framework that supports
   data-intensive distributed applications under a free license.</para>
 
-  <para>The default HPCC configuration continues to be the same--Workunits are
+  <para>The default HPCC Systems<superscript>®</superscript> configuration continues to be the same--Workunits are
   stored in Dali's data store and Sasha is typically configured to archive
   workunits to disk to save memory usage.</para>
 
   <para>Switching to Cassandra Workunit storage eliminates the need to archive
   workunits and allows you to manage your data independently.</para>
 
-  <para>This section details the steps to configure your HPCC platform to use
+  <para>This section details the steps to configure your HPCC Systems platform to use
   Cassandra as a Workunit server.</para>
 
   <sect2 id="CassandraWorkunitServer">
@@ -89,7 +89,7 @@
     <para><orderedlist>
         <listitem>
           <para>Install Cassandra and configure it as you wish. The only
-          requirements to work with an HPCC platform are:</para>
+          requirements to work with an HPCC Systems platform are:</para>
 
           <para><orderedlist numeration="loweralpha">
               <listitem>
@@ -99,13 +99,13 @@
 
               <listitem>
                 <para>If you want security, you should set up Cassandra's
-                authentication and create a superuser for HPCC to use. These
+                authentication and create a superuser for HPCC Systems to use. These
                 credentials must then be entered in the DaliPlugin
                 configuration in Configuration Manager.</para>
               </listitem>
 
               <listitem>
-                <para>Ensure your Cassandra server can be reached by your HPCC
+                <para>Ensure your Cassandra server can be reached by your HPCC Systems
                 nodes. (listen_address and rpc_address)</para>
               </listitem>
 
@@ -117,21 +117,21 @@
         </listitem>
 
         <listitem>
-          <para>Use Configuration Manager to configure your HPCC platform to
+          <para>Use Configuration Manager to configure your HPCC Systems platform to
           use Cassandra for Workunit storage.</para>
         </listitem>
 
         <listitem>
           <para>Make sure Cassandra is running.</para>
 
-          <para>Once you have configured your HPCC Platform to use Cassandra
+          <para>Once you have configured your HPCC Systems platform to use Cassandra
           for Workunit storage, you must make sure Cassandra is running before
           starting your system.</para>
         </listitem>
 
         <listitem>
-          <para>Push out your environment.xml and restart your HPCC
-          Platform.</para>
+          <para>Push out your environment.xml and restart your HPCC Systems
+          platform.</para>
         </listitem>
 
         <listitem>
@@ -161,7 +161,7 @@
   </sect2>
 
   <sect2 id="cfgCassandraWuStorage" role="brk">
-    <title>Configure your HPCC platform to use Cassandra for Workunit
+    <title>Configure your HPCC Systems platform to use Cassandra for Workunit
     storage</title>
 
     <para>This option is configured by adding a DaliPlugin component to your
@@ -170,12 +170,12 @@
     <sect3 id="cassandra_ConnectToConfigMgr">
       <title>Connect to Configuration Manager</title>
 
-      <para>In order to change the configuration for HPCC components, connect
+      <para>In order to change the configuration for HPCC Systems components, connect
       to the Configuration Manager.</para>
 
       <orderedlist numeration="arabic">
         <listitem>
-          <para>Stop all HPCC Components, if they are running.</para>
+          <para>Stop all HPCC Systems components, if they are running.</para>
         </listitem>
 
         <listitem>
@@ -342,7 +342,7 @@ sudo cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/environment.
           role="bold">every</emphasis> node.</para>
 
           <para>You may want to create a script to push out the XML file to
-          all nodes. A sample script is provided with HPCC. The following
+          all nodes. A sample script is provided with the HPCC Systems platform. The following
           command copies the XML files out to all nodes as required:</para>
 
           <para><programlisting>sudo /opt/HPCCSystems/sbin/hpcc-push.sh -s &lt;sourcefile&gt; -t &lt;destinationfile&gt;
@@ -350,7 +350,7 @@ sudo cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/environment.
         </listitem>
 
         <listitem>
-          <para>Restart the HPCC system on <emphasis
+          <para>Restart the HPCC Systems platform on <emphasis
           role="bold">every</emphasis> node.</para>
         </listitem>
       </orderedlist>

docs/EN_US/HPCCSystemAdmin/SA-Mods/DAFtslave.xml

@@ -5,24 +5,24 @@
   <title>Support Utilities</title>
 
   <para>There are a few additional components which are neither system servers
-  nor client interfaces but nonetheless important in supporting HPCC
+  nor client interfaces but nonetheless important in supporting HPCC Systems<superscript>®</superscript>
   tasks.</para>
 
   <sect3 id="DAFilesrv">
     <title>dafilesrv</title>
 
     <para>The dafilesrv is a daemon that runs on system servers or physical
-    locations on the HPCC system. This daemon enables the HPCC components to
+    locations on the HPCC Systems platform. This daemon enables the HPCC Systems components to
     have file access to physical file locations. File access could be
     spraying, despraying, copying, accessing logs, etc. Anything that requires
     a file from another node, must have dafilesrv running on that node. The
     dafilesrv daemon can be configured to allow SSL connections only, which
     secures remote access to physical files.</para>
 
-    <para>The dafilesrv daemon runs as a process on every HPCC node. The
+    <para>The dafilesrv daemon runs as a process on every HPCC Systems node. The
     daemon will typically keep running even if your system is stopped. That is
     an important fact to keep in mind if you are stopping your system for
-    maintenance, installations, or upgrades. Even if you issue the HPCC system
+    maintenance, installations, or upgrades. Even if you issue the HPCC Systems
     stop command, you would still need to stop the dafilesrv daemon.</para>
 
     <para>One way to check and see if dafilesrv is running, is to issue a
@@ -43,7 +43,7 @@
     <programlisting>hpcc-run.sh -c dafilesrv@mydafilesrv.service stop</programlisting>
 
     <para>You must have sudo permission level access in order to start or stop
-    any of the HPCC components, including dafilesrv.</para>
+    any of the HPCC Systems components, including dafilesrv.</para>
 
     <para>After you verify that dafilesrv is not running you can then proceed
     with the installation.</para>

docs/EN_US/HPCCSystemAdmin/SA-Mods/SecMgrMod.xml

@@ -44,7 +44,7 @@
       </itemizedlist></para>
 
     <para><emphasis role="bold">Buildset definition</emphasis> - The plugin
-    declares itself as an HPCC Security Manager Plugin component, and declares
+    declares itself as an HPCC Systems<superscript>®</superscript> Security Manager Plugin component, and declares
     the location of the plugin files and the configuration definition
     schema.</para>
 
@@ -67,7 +67,7 @@
     <para><emphasis role="bold">Configuration Definition</emphasis> - The
     plugin must provide a definition of the configuration elements and the
     structure it expects to receive at the time it is instantiated. The XSD
-    file is consumed by the HPCC Configuration manager component and is
+    file is consumed by the HPCC Systems Configuration Manager component and is
     rendered as a GUI form. The configuration definition is defined as an
     element of the component name (as declared in the buildset) followed by
     attributes and/or complex elements.</para>
@@ -170,13 +170,13 @@
 
     <para><emphasis role="bold">Configuration transformation rules</emphasis>
     - (optional) specified as an xsl template, this set of rules can be
-    applied to the configuration XML. Refer to XSL templates in the HPCC
+    applied to the configuration XML. Refer to XSL templates in the HPCC Systems
     source tree.</para>
 
     <sect2 id="concrete-example">
       <title>Concrete Example</title>
 
-      <para>The HPCC Platform includes a security manager plugin
+      <para>The HPCC Systems platform includes a security manager plugin
       implementation (HTPasswd) and can be used as a guidance for the plugin
       development process:</para>
 

docs/EN_US/HPCCSystemAdmin/SA-Mods/SecMgrModConfDeploy.xml

@@ -5,17 +5,17 @@
   <title role="nbrk">Configure and Deploy the Security Manager Plugin</title>
 
   <para>The following sections detail the process of configuring your HPCC
-  system to use the Security Manager Plugin.</para>
+  Systems<superscript>®</superscript> platform to use the Security Manager Plugin.</para>
 
   <sect1 id="how-to-configure-an-existing-security-manager-plugin">
     <title>How to Configure a Security Manager Plugin</title>
 
     <para>Once the plugin has been installed, the plugin can be configured
-    onto the HPCC platform using Configuration Manager.</para>
+    onto the HPCC Systems platform using Configuration Manager.</para>
 
     <para><orderedlist>
         <listitem>
-          <para>Stop all HPCC Components.</para>
+          <para>Stop all HPCC Systems components.</para>
 
           <para>Verify that they are stopped. You can use a single command,
           such as : <programlisting>sudo /opt/HPCCSystems/sbin/hpcc-run.sh -a hpcc-init status</programlisting></para>

docs/EN_US/HPCCSystemAdmin/SA-Mods/SysAdminConfigMod.xml

@@ -6,16 +6,16 @@
     <title>Using Configuration Manager</title>
 
     <para id="cfgmgr_introP0">Configuration Manager is the utility with which
-    we configure the HPCC platform. The HPCC platform's configuration is
+    we configure the HPCC Systems<superscript>®</superscript> platform. The HPCC Systems platform's configuration is
     stored in an XML file named <emphasis
     role="bold">environment.xml</emphasis>. Once you generate an environment
     (xml) file, it gets saved into a source directory (default is <emphasis
     role="bold">/etc/HPCCSystems/source</emphasis>). You then need to stop the
-    system to copy it into the active HPCC directory, then distribute it into
-    place on to each node and restart the HPCC system. At no time during
+    system to copy it into the active HPCC Systems directory, then distribute it into
+    place on to each node and restart the HPCC Systems platform. At no time during
     configuration do you work on the live environment file.</para>
 
-    <para id="cfgmgr_introP1">When you install the HPCC system package, a
+    <para id="cfgmgr_introP1">When you install the HPCC Systems package, a
     default single-node environment.xml file is generated. After that, you can
     use the Configuration Manager to modify it and/or create a different
     environment file to configure components, or add nodes. There is a
@@ -43,15 +43,15 @@
     detailed in <emphasis>Using Configuration Manager</emphasis>.</para>
 
     <para>The following sections will provide the details for configuring an
-    HPCC environment using the Configuration Manager.</para>
+    HPCC Systems environment using the Configuration Manager.</para>
 
     <sect1 id="configuring-a-multi-node-system">
       <title>Running the Configuration Manager</title>
 
-      <para>This section will guide you through configuring an HPCC
+      <para>This section will guide you through configuring an HPCC Systems
       environment using the Configuration Manager.</para>
 
-      <para>The HPCC package should already be installed on ALL nodes.</para>
+      <para>The HPCC Systems package should already be installed on ALL nodes.</para>
 
       <para>You can use any tool or shell script you choose.</para>
 
@@ -85,7 +85,7 @@
         </listitem>
       </orderedlist>
 
-      <para>There are different ways to configure your HPCC system. You can
+      <para>There are different ways to configure your HPCC Systems platform. You can
       use the <emphasis role="bold">Generate environment wizard</emphasis> and
       use that environment or experienced users can then use the <emphasis
       role="bold">Advanced View</emphasis> for more specific customization.
@@ -122,7 +122,7 @@
             <para>Press the Next button.</para>
 
             <para>Next you will need to define the IP addresses that your HPCC
-            system will be using.</para>
+            Systems platform will be using.</para>
           </listitem>
 
           <listitem>
@@ -246,7 +246,7 @@
                 <entry><inlinegraphic
                 fileref="../../images/OSSgr3.png" /></entry>
 
-                <entry>Keep in mind, that your HPCC configuration may be
+                <entry>Keep in mind, that your HPCC Systems configuration may be
                 different depending on your needs. For example, you may not
                 need a Roxie or you may need several smaller Roxie clusters.
                 In addition, in a production [Thor] system, you would ensure
@@ -266,9 +266,9 @@
             <listitem>
               <?dbfo keep-together="always"?>
 
-              <para>Stop the HPCC system.</para>
+              <para>Stop the HPCC Systems platform.</para>
 
-              <para>If it is running stop the HPCC system (on every node),
+              <para>If it is running stop the HPCC Systems platform (on every node),
               using a command such as this:</para>
  
  <programlisting> sudo systemctl stop hpccsystems-platform.target</programlisting> 			  
@@ -284,7 +284,7 @@
                   <listitem>
                     <para>You may have a multi-node system and a custom script
                     such as the one illustrated in Appendix of the <emphasis
-                    role="bluebold">Installing and Running the HPCC
+                    role="bluebold">Installing and Running the HPCC Systems
                     Platform</emphasis> document to start and stop your
                     system. If that is the case please use the appropriate
                     command for stopping your system on every node.</para>
@@ -305,7 +305,7 @@
                           <inlinegraphic fileref="../../images/caution.png" />
                         </entry>
 
-                        <entry>Be sure HPCC is stopped before attempting to
+                        <entry>Be sure the HPCC Systems platform is stopped before attempting to
                         copy the environment.xml file.</entry>
                       </row>
                     </tbody>
@@ -362,13 +362,13 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
               <para>You may want to use a script to push out the XML file to
               all nodes. See the <emphasis>Example Scripts</emphasis> section
               in the Appendix of the <emphasis role="bluebold">Installing and
-              Running the HPCC Platform</emphasis> document. You can use the
+              Running the HPCC Systems platform</emphasis> document. You can use the
               scripts as a model to create your own script to copy the
               environment.xml file out to all your nodes.</para>
             </listitem>
 
             <listitem>
-              <para>Restart the HPCC platform on all nodes.</para>
+              <para>Restart the HPCC Systems platform on all nodes.</para>
             </listitem>
           </orderedlist>
         </sect3>
@@ -387,24 +387,24 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
 
       <para>This is a System Administrative topic designed to provide some
       insight as to an aspect of System Administration for you HPCC
-      System.</para>
+      Systems cluster.</para>
     </sect1>
 
     <sect1 id="System_sizings">
       <title>System Sizings</title>
 
       <para>This section provides some guidance in determining the sizing
-      requirements for an initial installation of HPCC. The following are some
+      requirements for an initial installation of HPCC Systems. The following are some
       suggested configuration guides that can be helpful when planning your
       system.</para>
 
       <sect2 id="SysAdmin_MinSuggestedHW" role="nobrk">
         <title>Minimum Suggested Hardware</title>
 
-        <para>HPCC was designed to run on common commodity hardware, and could
+        <para>HPCC Systems was designed to run on common commodity hardware, and could
         function on even lesser hardware. The following list is the suggested
         minimum hardware specifications. At the very minimum you should
-        consider the following hardware components for your HPCC system. These
+        consider the following hardware components for your HPCC Systems. These
         guidelines were put together based on real world usage of mission
         critical (uptime) with high volume data. <informaltable border="all"
             colsep="1" rowsep="1">
@@ -551,10 +551,10 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
       <sect2 id="Sample-Size-HighDataVolume">
         <title>Sample Sizing for High Data volume (Typical)</title>
 
-        <para>The most typical scenario for HPCC is utilizing it with a high
+        <para>The most typical scenario for HPCC Systems is utilizing it with a high
         volume of data. This suggested sample sizing would be appropriate for
         a site with large volumes of data. A good policy is to set the Thor
-        size to 4 times the source data on your HPCC. Typically, Roxie would
+        size to 4 times the source data on your HPCC Systems. Typically, Roxie would
         be about 1/4 the size of Thor. This is because the data is compressed
         and the system does not hold any transient data in Roxie. Remember
         that you do not want the number of Roxie nodes to exceed the number of

docs/EN_US/IMDB/IMDB.xml

@@ -68,7 +68,7 @@
 
       <para>This exercise shows the methodology to extract useful information
       from data. Finding interesting links and relationships from large or
-      massive datasets is a typical use of the HPCCSystems High Performance
+      massive datasets is a typical use of the HPCC Systems High Performance
       Computing Cluster (HPCC) platform.</para>
 
       <para>In this example, we will download the data files from the Internet
@@ -79,7 +79,7 @@
       everyone should understand the data and relationships intuitively.
       However, the data is comprehensive enough to provide a solid example and
       inspiration for new users to gain skills to attack their own real-world
-      problems with an HPCC.</para>
+      problems with an HPCC Systems.</para>
 
       <para>In this example, we will:</para>
 
@@ -120,9 +120,9 @@
               <row>
                 <entry><inlinegraphic fileref="images/OSSgr3.png" /></entry>
 
-                <entry>While this example will run on a single-node HPCC, you
+                <entry>While this example will run on a single-node HPCC Systems platform, you
                 will see a dramatic difference in performance on a multi-node
-                system. The true power of an HPCC is its ability to work on
+                system. The true power of an HPCC Systems<superscript>®</superscript> platform is its ability to work on
                 different portions of the data file in parallel. This is known
                 as Massively Parallel Processing (MPP).</entry>
               </row>
@@ -146,7 +146,7 @@
         pictures.</para>
 
         <para>It is manageable in size (~400MB) and is sufficient in size to
-        exercise an HPCC platform but not too big to download<emphasis
+        exercise an HPCC Systems platform but not too big to download<emphasis
         role="bold">.</emphasis></para>
 
         <para>The plain text data files are available from the following ftp
@@ -240,8 +240,8 @@ Blankline</programlisting></para>
         Zone</emphasis></title>
 
         <para>In this step, you will copy the data files to a location from
-        which it can be sprayed to your HPCC cluster. A Landing Zone is a
-        storage location attached to your HPCC. It has a utility running to
+        which it can be sprayed to your HPCC Systems cluster. A Landing Zone is a
+        storage location attached to your HPCC Systems. It has a utility running to
         facilitate file spraying to a cluster.</para>
 
         <para>For smaller data files, maximum of 2GB, you can use the
@@ -249,7 +249,7 @@ Blankline</programlisting></para>
         ~400 mb.</para>
 
         <para>Next you will distribute (or Spray) the dataset to all the nodes
-        in the HPCC cluster. The power of the HPCC comes from its ability to
+        in the HPCC Systems cluster. The power of the HPCC Systems comes from its ability to
         assign multiple processors to work on different portions of the data
         file in parallel.</para>
 
@@ -363,7 +363,7 @@ Blankline</programlisting></para>
         <title>Spray the Data File to your <emphasis>Data Refinery (Thor)
         Cluster</emphasis></title>
 
-        <para>To use the data file in our HPCC system, we must "spray" it to
+        <para>To use the data file in our HPCC Systems platform, we must "spray" it to
         all the nodes. A <emphasis>spray</emphasis> or
         <emphasis>import</emphasis> is the relocation of a data file from one
         location (such as a Landing Zone) to multiple file parts on nodes in a
@@ -486,7 +486,7 @@ Blankline</programlisting></para>
 
           <listitem>
             <para>After both sprays are complete, we can query the logical
-            files on the HPCC to see the files we sprayed.</para>
+            files on the HPCC Systems platform to see the files we sprayed.</para>
           </listitem>
 
           <listitem>

docs/EN_US/Installing_and_RunningTheHPCCPlatform/Inst-Mods/Hardware.xml

@@ -3,7 +3,7 @@
 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
 <book>
   <bookinfo>
-    <title>Installing the HPCC Platform: Hardware Module</title>
+    <title>Installing the HPCC Systems<superscript>®</superscript> Platform: Hardware Module</title>
 
     <mediaobject>
       <imageobject>
@@ -78,10 +78,10 @@
     <title>Hardware and Software Requirements</title>
 
     <para>This section describes some hardware and software requirements or
-    recommendations in order to run the HPCC. Essentially the HPCC system is
+    recommendations in order to run HPCC Systems. Essentially the HPCC Systems platform is
     designed to run on commodity hardware, and would probably work well on
     almost any hardware. To really take advantage of the power of an HPCC
-    system you should deploy your HPCC system on more modern advanced
+    Systems platform you should deploy your system on more modern advanced
     hardware.</para>
 
     <para>Hardware and software technology are constantly changing and
@@ -97,7 +97,7 @@
       <title>Network Switch</title>
 
       <para>The network switch is a significant component of the HPCC
-      System.</para>
+      Systems platform.</para>
 
       <sect2 id="Switch-Requirements">
         <title>Switch requirements</title>
@@ -117,7 +117,7 @@
           </listitem>
         </itemizedlist>
 
-        <para>Ideally your HPCC system will perform better when each node is
+        <para>Ideally your HPCC Systems will perform better when each node is
         connected directly into a single switch. You should be able to provide
         a port for each node on a single switch to optimize system
         performance. Your switch size should correspond to the size of your
@@ -156,7 +156,7 @@
 
         <para>Generally, higher-end, higher throughput switches are also going
         to provide better performance. For larger systems, a high-capacity
-        managed switch that can be configured and tuned for HPCC efficiency is
+        managed switch that can be configured and tuned for HPCC Systems efficiency is
         the best choice.</para>
       </sect2>
     </sect1>
@@ -248,7 +248,7 @@
     <sect1 id="Nodes-Hardware">
       <title>Nodes-Hardware</title>
 
-      <para>An HPCC System can run as a single node system or a multi node
+      <para>An HPCC Systems platform can run as a single node system or a multi node
       system.</para>
 
       <para>These hardware recommendations are intended for a multi-node
@@ -360,8 +360,8 @@
         <title>Operating System Requirements</title>
 
         <para>Binary installation packages are available for many Linux
-        Operating systems. HPCC System platform requirements are readily
-        available on the HPCC Portal.</para>
+        Operating systems. HPCC Systems platform requirements are readily
+        available on the HPCC Systems<superscript>®</superscript> Portal.</para>
 
         <para><ulink
         url="https://hpccsystems.com/training/documentation/system-requirements">https://hpccsystems.com/training/documentation/system-requirements</ulink></para>
@@ -370,7 +370,7 @@
       <sect2 id="configuration-manager">
         <title>Dependencies</title>
 
-        <para>Installing HPCC on your system depends on having required
+        <para>Installing HPCC Systems on your system depends on having required
         component packages installed on the system. The required dependencies
         can vary depending on your platform. In some cases the dependencies
         are included in the installation packages. In other instances the
@@ -393,12 +393,12 @@
       <sect2 id="SSH_Keys" role="brk">
         <title>SSH Keys</title>
 
-        <para>The HPCC components use ssh keys to authenticate each other.
+        <para>The HPCC Systems components use ssh keys to authenticate each other.
         This is required for communication between nodes. A script to generate
         keys has been provided .You should run that script and distribute the
         public and private keys to all nodes after you have installed the
         packages on all nodes, but before you configure a multi-node
-        HPCC.</para>
+        HPCC Systems platform.</para>
 
         <para><itemizedlist spacing="compact">
             <listitem>
@@ -442,10 +442,10 @@
 
       <itemizedlist spacing="compact">
         <listitem>
-          <para>Running the HPCC platform requires communication from your
-          user workstation with a browser to the HPCC. You will use it to
-          access ECL Watch--a Web-based interface to your HPCC system. ECL
-          Watch enables you to examine and manage many aspects of the HPCC and
+          <para>Running the HPCC Systems platform requires communication from your
+          user workstation with a browser to the HPCC Systems platform. You will use it to
+          access ECL Watch--a Web-based interface to your HPCC Systems platform. ECL
+          Watch enables you to examine and manage many aspects of the HPCC Systems platform and
           allows you to see information about jobs you run, data files, and
           system metrics.</para>
 

docs/EN_US/Installing_and_RunningTheHPCCPlatform/Inst-Mods/UnityLauncher.xml

@@ -4,7 +4,7 @@
 <sect1 id="Unity_Launcher">
   <title>Unity Launcher Icon</title>
 
-  <para>The HPCC platform supports an Ubuntu Unity Launcher icon.</para>
+  <para>The HPCC Systems platform supports an Ubuntu Unity Launcher icon.</para>
 
   <para>This allows you to start, stop, restart, or query the status of an
   installed single node system from an icon on the Unity Launcher of a desktop
@@ -17,7 +17,7 @@
         <listitem>
           <para>This is only useful on a single-node system at this time.
           Future versions may operate in a different manner and support
-          multi-node HPCC systems<superscript>®</superscript>.</para>
+          multi-node HPCC Systems<superscript>®</superscript>.</para>
         </listitem>
       </varlistentry>
     </variablelist></para>
@@ -31,7 +31,7 @@
         Systems<superscript>®</superscript> application icon.</para>
 
         <figure>
-          <title>HPCC Application Icon</title>
+          <title>HPCC Systems Application Icon</title>
 
           <mediaobject>
             <imageobject>

docs/EN_US/Installing_and_RunningTheHPCCPlatform/Inst-Mods/UserSecurityMaint.xml

@@ -4,14 +4,14 @@
 <sect1 id="User_Security_Maint">
   <title>User Security Maintenance</title>
 
-  <para>Configuring an HPCC System to use Active Directory or LDAP-based
+  <para>Configuring an HPCC Systems<superscript>®</superscript> platform to use Active Directory or LDAP-based
   security allows you to set permissions to control access to Features, File
   Scopes, and Workunit Scopes.</para>
 
   <sect2 id="User_Security_Intro">
     <title>Introduction</title>
 
-    <para>HPCC systems<superscript>®</superscript> maintains security in a
+    <para>HPCC Systems<superscript>®</superscript> maintains security in a
     number of ways. HPCC Systems<superscript>®</superscript> can be configured
     to manage users' security rights by pointing either at Microsoft's Active
     Directory on a Windows system, or a 389Directory Server on Linux
@@ -24,7 +24,7 @@
     Dali server.</para>
 
     <para>Establish permissions by group or by user and define them by
-    association with a particular feature of the HPCC System. Permissions can
+    association with a particular feature of the HPCC Systems platform. Permissions can
     be defined for each unique combination of group and feature. Permissions
     are separated into the following categories:<informaltable frame="all">
         <tgroup cols="2" colsep="1">
@@ -123,8 +123,8 @@
 
       <listitem>
         <para><emphasis role="bold">Permissions</emphasis>. Shows the features
-        of the HPCC System where permissions may be set. Use this area to view
-        the permissions currently set for any area of the HPCC System, or to
+        of the HPCC Systems where permissions may be set. Use this area to view
+        the permissions currently set for any area of HPCC Systems, or to
         add groups and users and set/modify their permission for a specific
         feature</para>
       </listitem>
@@ -185,7 +185,7 @@
       <para>In a security-enabled environment, access to ECL Watch and its
       features is controlled using a login and password. The <emphasis
       role="bold">Users</emphasis> area enables you to control who has access
-      to ECL Watch and the features of your HPCC System to which they have
+      to ECL Watch and the features of your HPCC Systems to which they have
       access. Permissions can be set for users based on their individual needs
       and users can also be added to groups which have already been set up.
       Use the <emphasis role="bold">Users</emphasis> menu item to:</para>
@@ -412,9 +412,9 @@
         <title>To promote a user to an Administrator</title>
 
         <para>To modify a users credentials you must have Administrator level
-        access. You can designate the HPCC Administrator account to have
-        limited permissions only relating to HPCC elements and not LDAP
-        administrator's rights. To promote a user to an HPCC Administrator,
+        access. You can designate the HPCC Systems Administrator account to have
+        limited permissions only relating to HPCC Systems elements and not LDAP
+        administrator's rights. To promote a user to an HPCC Systems Administrator,
         add the user to the configured <emphasis
         role="bold">Administrators</emphasis> group.</para>
 
@@ -640,7 +640,7 @@
       <para>There may be occasions when you need to modify the permissions for
       individual users. For example, users may have individual security needs
       that are not completely covered in any group or, there may be occasions
-      when a user requires temporary access to an HPCC feature. Permissions
+      when a user requires temporary access to an HPCC Systems feature. Permissions
       set in this area of ECL Watch only affect the user you choose. Most
       individual permissions you set here overwrite ones set in any group to
       which the user belongs, except in the case of an explicit deny.</para>
@@ -750,7 +750,7 @@
 
       <para>Setting up groups ensures that all users with the same permission
       needs have the same permission settings. You can give users the access
-      they require to the feature areas of HPCC that they need. There is no
+      they require to the feature areas of HPCC Systems that they need. There is no
       limit to the number of groups you can create. You can create as many
       groups as you need to control access for all your users regardless of
       their tasks.</para>
@@ -1152,7 +1152,7 @@
     <title>Feature resources</title>
 
     <para>There are several features for which you can set up access control
-    in HPCC. Access to features of the HPCC system is controlled by via the
+    in HPCC Systems. Access to features of the HPCC Systems platform is controlled by via the
     <emphasis role="bold">ESP Features for SMC</emphasis> category. <graphic
     fileref="../../images/Perm006.jpg" vendor="eclwatchSS" /></para>
 
@@ -1230,7 +1230,7 @@
       <title>SMC Feature Permissions</title>
 
       <para>The following table describes the level of access required to be
-      able to use these HPCC ECL Watch features.</para>
+      able to use these HPCC Systems ECL Watch features.</para>
 
       <para><informaltable>
           <tgroup cols="3">
@@ -1643,7 +1643,7 @@
   <sect2 id="FeaturePermissions_FileAccessControl">
     <title><emphasis role="bold">File Access Control</emphasis></title>
 
-    <para>The HPCC's LDAP <emphasis role="bold">Dali Server</emphasis>
+    <para>The HPCC Systems LDAP <emphasis role="bold">Dali Server</emphasis>
     technology provides the ability to set secure access permissions to data
     file folders (or file scopes). This is controlled by the use of file scope
     resources.</para>
@@ -1685,7 +1685,7 @@
     role="bold">/var/lib/HPCCSystems/hpcc-data/thor/collectionx/securedata
     </emphasis></para>
 
-    <para>All HPCC components and tools respect LDAP file access security. The
+    <para>All HPCC Systems components and tools respect LDAP file access security. The
     following exceptions are assumed to be system level or for administrative
     users:</para>
 

docs/EN_US/Installing_and_RunningTheHPCCPlatform/Inst-Mods/anagram1.xml

@@ -19,7 +19,7 @@
         (Start <emphasis role="bold">&gt;&gt;</emphasis> All Programs
         <emphasis role="bold">&gt;&gt;</emphasis> HPCC
         Systems <emphasis role="bold"> &gt;&gt;</emphasis> ECL
-        IDE ) and login to your HPCC.</para>
+        IDE) and login to your HPCC Systems platform instance.</para>
       </listitem>
 
       <listitem>

docs/EN_US/Installing_and_RunningTheHPCCPlatform/Inst-Mods/anagram2.xml

@@ -44,8 +44,8 @@
     
 
     <para>In this step, you will copy the data files to a location from which
-    it can be sprayed to your HPCC cluster.
-    A Landing Zone is a storage location attached to your HPCC.
+    it can be sprayed to your HPCC Systems cluster.
+    A Landing Zone is a storage location attached to your HPCC Systems platform.
     It has a utility running to facilitate file spraying to a cluster.</para>
 
     <para>For smaller data files, maximum of 2GB,
@@ -53,7 +53,7 @@
     Watch. This data file is only ~400 kb.</para>
 
     <para>Next you will distribute (or Spray) the dataset to all the nodes in
-    the HPCC cluster. The power of the HPCC
+    the HPCC Systems cluster. The power of HPCC Systems 
     comes from its ability to assign multiple processors to work on different
     portions of the data file in parallel. Even though the VM
     Edition only has a single node, the data must be sprayed to the
@@ -150,7 +150,7 @@
     
 
     <para>To use the data file in our HPCC
-    system, we must "spray" it to all the nodes. A <emphasis>spray</emphasis>
+    Systems cluster, we must "spray" it to all the nodes. A <emphasis>spray</emphasis>
     or <emphasis>import</emphasis> is the relocation of a data file from one
     location (such as a Landing Zone) to multiple file parts on nodes in a
     cluster.</para>
@@ -583,7 +583,7 @@ OUTPUT(ValidWords)
 
     <para>Now that the query is published to a Roxie cluster, we can run it
     using the WsECL service. WsECL is a web-based interface to queries on an
-    HPCC platform. Use the following URL:</para>
+    HPCC Systems platform. Use the following URL:</para>
 
     <para><emphasis role="bold">http://nnn.nnn.nnn.nnn:pppp (where
     nnn.nnn.nnn.nnn is your ESP Server's

docs/EN_US/Installing_and_RunningTheHPCCPlatform/Inst-Mods/hpcc_ldap.xml

@@ -2,11 +2,11 @@
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
 <sect1 id="ldap_config">
-  <title>Configuring HPCC for Authentication</title>
+  <title>Configuring HPCC Systems<superscript>®</superscript> for Authentication</title>
 
-  <para>This section details the steps to configure your HPCC platform to use
+  <para>This section details the steps to configure your HPCC Systems platform to use
   authentication. There are currently a few ways to use authentication with
-  your HPCC system: simple htpasswd authentication, LDAP, or another plugin
+  your HPCC Systems platform: simple htpasswd authentication, LDAP, or another plugin
   security method.</para>
 
   <para>The htpasswd authentication method is basic password authentication.
@@ -58,12 +58,12 @@
     <sect3 id="htpasswd_ConnectToConfigMgr">
       <title>Connect to Configuration Manager</title>
 
-      <para>In order to change the configuration for HPCC components, connect
+      <para>In order to change the configuration for HPCC Systems components, connect
       to the Configuration Manager.</para>
 
       <orderedlist numeration="arabic">
         <listitem>
-          <para>Stop all HPCC Components, if they are running.</para>
+          <para>Stop all HPCC Systems components, if they are running.</para>
         </listitem>
 
         <listitem>
@@ -120,7 +120,7 @@
     </sect3>
 
     <sect3 id="Enabling_htpasswd_AUthentication">
-      <title>Enabling htpasswd authentication in HPCC</title>
+      <title>Enabling htpasswd authentication in HPCC Systems</title>
 
       <orderedlist continuation="continues">
         <listitem>
@@ -266,7 +266,7 @@
 
       <para>Users and passwords are kept in the htpasswd file. The htpasswd
       file must exist on the ESP Node where you have enabled authentication.
-      HPCC only recognizes MD5 encrypted passwords.</para>
+      HPCC Systems only recognizes MD5 encrypted passwords.</para>
 
       <para>The default location is: <emphasis
       role="bold">/etc/HPCCSystems/.htpasswd</emphasis> on the ESP node that
@@ -295,26 +295,26 @@
     securing your system, or parts of your system. In addition to these
     configuration settings you should run the <emphasis
     role="bold">initldap</emphasis> utility to create the required default
-    HPCC Admin user on your LDAP server.</para>
+    HPCC Systems Admin user on your LDAP server.</para>
 
     <para>If you choose to use LDAP authentication you must enable LDAP
-    security in your HPCC System configuration. With LDAP security enabled on
+    security in your HPCC Systems configuration. With LDAP security enabled on
     your system you can then choose to enable file scope security. You can
     choose to use LDAP authentication without enabling file scope security.
     The following sections describe how to enable LDAP authentication and file
-    scope security for your HPCC system.</para>
+    scope security for your HPCC Systems platform.</para>
 
     <!--***Note: (9/2014) Adding Documentation for initLdap.*** -->
 
     <sect3 id="UsingLDAP_ConnectToConfigMgr">
       <title>Connect to Configuration Manager</title>
 
-      <para>In order to change the configuration for HPCC components, connect
+      <para>In order to change the configuration for HPCC Systems components, connect
       to the Configuration Manager.</para>
 
       <orderedlist numeration="arabic">
         <listitem>
-          <para>Stop all HPCC Components, if they are running.</para>
+          <para>Stop all HPCC Systems components, if they are running.</para>
         </listitem>
 
         <listitem>
@@ -705,10 +705,10 @@
 
             <listitem>
               <para>Locate the <emphasis role="bold">ldapUser</emphasis> field
-              and verify that there is a valid HPCC user who is a member of
+              and verify that there is a valid HPCC Systems user who is a member of
               the Authenticated Users group on your LDAP server. For example,
               the "<emphasis>roxie</emphasis>" user assumes that the
-              "<emphasis>roxie</emphasis>" user is a valid HPCC authenticated
+              "<emphasis>roxie</emphasis>" user is a valid HPCC Systems authenticated
               user.</para>
             </listitem>
 
@@ -761,8 +761,8 @@
     <sect3 id="UsingLDAP_theInitldapUtility">
       <title>The initldap Utility</title>
 
-      <para>The initldap utility creates the HPCC Administrator's user account
-      and the HPCC OUs for a newly defined LDAP server. The initldap utility
+      <para>The initldap utility creates the HPCC Systems Administrator's user account
+      and the HPCC Systems OUs for a newly defined LDAP server. The initldap utility
       extracts these settings from the LDAPServer component(s) in the
       environment.xml bound to the configured ESPs.</para>
 
@@ -782,7 +782,7 @@
       <para><programlisting>Enter the '389DirectoryServer' LDAP Admin User name on '10.123.456.78'...Directory Manager        
 Enter the LDAP Admin user 'Directory Manager' password...********
 
-Ready to initialize HPCC LDAP Environment, using the following settings
+Ready to initialize HPCC Systems LDAP Environment, using the following settings
        LDAP Server     : 10.123.456.78
        LDAP Type       : 389DirectoryServer
        HPCC Admin User : HPCCAdmin389
@@ -796,7 +796,7 @@ Proceed?  y/n
       <para>When a new ESP user account is created, a private
       "hpccinternal::&lt;user&gt;" file scope is also created granting new
       users full access to that scope and restricting access to other users.
-      This file scope is used to store temporary HPCC files such as spill
+      This file scope is used to store temporary HPCC Systems files such as spill
       files and temp files.</para>
 
       <para>If you are enabling LDAP file scope security and already have user

docs/EN_US/Installing_and_RunningTheHPCCPlatform/Inst-Mods/ssl-esp.xml

@@ -10,7 +10,7 @@
     <sect1 id="ssl4esp">
       <title>Configuring ESP Server to use HTTPS (SSL)</title>
 
-      <para>The HPCC Enterprise Services Platform server (ESP) supports Secure
+      <para>The HPCC Systems Enterprise Services Platform server (ESP) supports Secure
       Sockets Layer (SSL), a protocol used to send and receive private data or
       documents.</para>
 
@@ -19,7 +19,7 @@
       connection start with HTTPS instead of HTTP.</para>
 
       <para>The SSL option in the ESP Server allows secure and encrypted
-      communication between a browser or SOAP client application and the HPCC
+      communication between a browser or SOAP client application and the HPCC Systems
       platform.</para>
 
       <para>SSL capabilities are configured in the Configuration Manager, but
@@ -382,12 +382,12 @@ sudo cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/environment.
 
             <para>You might prefer to use a script to automate this step,
             especially if you have many nodes. See the Example Scripts section
-            in the Appendix of the Installing and Running the HPCCPlatform
+            in the Appendix of the Installing and Running the HPCC Systems platform
             manual.</para>
           </listitem>
 
           <listitem>
-            <para>Restart the HPCC system and certify the components as
+            <para>Restart the HPCC Systems platform and certify the components as
             usual.</para>
           </listitem>
         </orderedlist>

docs/EN_US/Installing_and_RunningTheHPCCPlatform/Installing_and_RunningTheHPCCPlatform.xml

@@ -2,10 +2,10 @@
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
 <book lang="en_US" xml:base="../">
-  <title>Installing &amp; Running the HPCC Platform</title>
+  <title>Installing &amp; Running the HPCC Systems<superscript>®</superscript> Platform</title>
 
   <bookinfo>
-    <title>Installing &amp; Running the HPCC Platform</title>
+    <title>Installing &amp; Running the HPCC Systems<superscript>®</superscript> Platform</title>
 
     <mediaobject>
       <imageobject>
@@ -74,16 +74,16 @@
         <ulink
         url="https://hpccsystems.com/Why-HPCC/How-it-works">https://hpccsystems.com/Why-HPCC/How-it-works</ulink>
         for more details.</para>
-      </footnote> Community Edition on a single node to start and then
+      </footnote> Systems<superscript>®</superscript> Community Edition on a single node to start and then
     optionally, expand it to a larger cluster of nodes.</para>
 
-    <para>The HPCC Thor technology is designed to effectively process,
+    <para>The HPCC Systems Thor technology is designed to effectively process,
     analyze, and find links and associations within high volumes of complex
     data. This can detect non-obvious relationships, scale to support
     petabytes of data, and is significantly faster than competing technologies
     while requiring less hardware and resources.</para>
 
-    <para>The HPCC Roxie technology - also known as the Rapid Data Delivery
+    <para>The HPCC Systems Roxie technology - also known as the Rapid Data Delivery
     Engine or RDDE - uses a combination of technologies and techniques that
     produce extremely fast throughput for queries on indexed data.</para>
 
@@ -116,14 +116,14 @@
 
       <para>We recommend taking the time to read this manual in its entirety;
       however, the following is a quick start summary of steps. There are many
-      aspects of the HPCC System platform and this guide is intended to help
+      aspects of the HPCC Systems platform and this guide is intended to help
       you get the most out of your system. This section is not intended to
       replace the more comprehensive material in the remainder of this
       book.</para>
 
       <orderedlist>
         <listitem>
-          <para>Install HPCC.</para>
+          <para>Install HPCC Systems platform.</para>
 
           <para>Download the installation package from <ulink
           url="https://hpccsystems.com/download/free-community-edition">https://hpccsystems.com/download</ulink>
@@ -142,7 +142,7 @@
         </listitem>
 
         <listitem>
-          <para>Start your HPCC System.</para>
+          <para>Start your HPCC Systems platform.</para>
 
           <xi:include href="Installing_and_RunningTheHPCCPlatform/Inst-Mods/SysDStart.xml"
                       xpointer="element(/1)"
@@ -162,7 +162,7 @@
           system.</para>
 
           <para>Using a browser, go to <emphasis role="bold">ECL
-          Watch</emphasis> running on port 8010 of your HPCC Node.</para>
+          Watch</emphasis> running on port 8010 of your HPCC Systems Node.</para>
 
           <para>For example, http://nnn.nnn.nnn.nnn:8010, where
           nnn.nnn.nnn.nnn is your node's IP address.</para>
@@ -186,7 +186,7 @@
       <sect2 id="Installing_NowWhat">
         <title>Now What?</title>
 
-        <para>Now that you have HPCC started and running, what do you want to
+        <para>Now that you have HPCC Systems started and running, what do you want to
         do? Maybe evaluate your needs and proceed to develop a custom
         configuration suitable for those needs. Maybe you want to expand your
         system and add nodes. Those topics and several others are covered in
@@ -195,7 +195,7 @@
         <para>To familiarize yourself with what your system can do we
         recommend following the steps in:<itemizedlist spacing="compact">
             <listitem>
-              <para>The <emphasis role="bold">HPCC Data
+              <para>The <emphasis role="bold">HPCC Systems Data
               Tutorial</emphasis></para>
             </listitem>
 
@@ -206,7 +206,7 @@
 
             <listitem>
               <para>Read <emphasis role="bold">Using Config Manager</emphasis>
-              to learn how to configure an HPCC platform using Advanced
+              to learn how to configure an HPCC Systems platform using Advanced
               View.</para>
             </listitem>
 
@@ -220,7 +220,7 @@
   </chapter>
 
   <chapter id="HPCC-installation-and-startup">
-    <title>HPCC Installation and Startup</title>
+    <title>HPCC Systems Installation and Startup</title>
 
     <para>Follow these steps to install the packages and start components in a
     single-node configuration to begin. Once it is successfully installed, you
@@ -228,7 +228,7 @@
     system.</para>
 
     <para>Configuration Manager is the utility with which we configure the
-    HPCC platform. It is run on your Linux Server and you access its interface
+    HPCC Systems platform. It is run on your Linux Server and you access its interface
     using a browser.<figure>
         <title>System Overview: Thor</title>
 
@@ -250,9 +250,9 @@
     <sect1 id="initial-set-up-single-node">
       <title>Initial Setup-Single Node</title>
 
-      <para>This section covers installing the HPCC on a single node. This
-      will enable the HPCC system to operate successfully; however, the real
-      strength of the HPCC is when it is run in a multi-node environment and
+      <para>This section covers installing the HPCC Systems on a single node. This
+      will enable the HPCC Systems platform to operate successfully; however, the real
+      strength of the HPCC Systems platform is when it is run in a multi-node environment and
       can leverage the ability to perform operations using Massively Parallel
       Processing (MPP).</para>
 
@@ -446,14 +446,14 @@ gpgcheck=0</programlisting></para>
             role="bold">L</emphasis>anguage (ECL) is a declarative, data
             centric programming language used to manage all aspects of the
             massive data joins, sorts, and builds that truly differentiate
-            HPCC (High Performance Computing Cluster) from other technologies
+            HPCC Systems (High Performance Computing Cluster) from other technologies
             in its ability to provide flexible data analysis on a massive
             scale.</para>
           </footnote> code using either ECL IDE, the command line ECL
         compiler, or the ECL Command line tool.</para>
 
         <sect3 id="InstallTheECLIDEandClientTools">
-          <title>Install the ECL IDE and HPCC Client Tools</title>
+          <title>Install the ECL IDE and HPCC Systems Client Tools</title>
 
           <para><orderedlist>
               <listitem>
@@ -502,7 +502,7 @@ gpgcheck=0</programlisting></para>
                     </mediaobject>
                   </figure></para>
 
-                <para>Follow the link to the HPCC System's portal download
+                <para>Follow the link to the HPCC Systems portal download
                 page.</para>
 
                 <para>Alternatively, you could use your browser to go directly
@@ -612,17 +612,17 @@ gpgcheck=0</programlisting></para>
           used to submit it to a target cluster for compilation by the remote
           compiler server (eclccserver).</para>
 
-          <para>To submit a job using the ecl CLI, make sure the HPCC has been
+          <para>To submit a job using the ECL CLI, make sure the HPCC Systems platform has been
           started and use the following syntax: <programlisting>ecl run  hello.ecl --target=hthor --server=&lt;IP Address of the ESP node&gt;:8010</programlisting></para>
 
           <para>The workunit<footnote>
-              <para>A Workunit is a record of a task submitted to an HPCC. It
+              <para>A Workunit is a record of a task submitted to an HPCC Systems cluster. It
               contains an identifier--workunit ID, the ECL code, results, and
               other information about the job.</para>
             </footnote> result is returned to the command line.</para>
 
           <para>View the full details of the workunit using the ECL Watch
-          interface for your HPCC at this location
+          interface for your HPCC Systems platform at this location
           http://nnn.nnn.nnn.nnn:8010, where nnn.nnn.nnn.nnn is the IP of your
           ESP server node. Either search for the workunit using the workunit
           ID or select ECL Workunits/Browse and find your workunit in the list
@@ -631,7 +631,7 @@ gpgcheck=0</programlisting></para>
           <para>Setting up an <emphasis role="bold">ecl.ini</emphasis> file
           makes running a workunit a little easier when you want to use the
           same settings every time you submit a workunit in this way. See the
-          <emphasis>HPCC Client Tools </emphasis>manual for details.</para>
+          <emphasis>HPCC Systems Client Tools </emphasis>manual for details.</para>
 
           <para>If your ECL is more complex than a single source file, you can
           use the eclcc compiler locally to create an archive to be sent to
@@ -716,7 +716,7 @@ gpgcheck=0</programlisting></para>
                 target cluster.</para>
 
                 <para><emphasis role="bold">Thor</emphasis> is the Data
-                Refinery component of your HPCC. It is a disk based massively
+                Refinery component of your HPCC Systems platform. It is a disk based massively
                 parallel computer cluster, optimized for sorting,
                 manipulating, and transforming massive data.</para>
 
@@ -792,7 +792,7 @@ gpgcheck=0</programlisting></para>
       <title>Configuring a Multi-Node System</title>
 
       <para>While the single-node system is fully-functional, it does not take
-      advantage of the true power of an HPCC--the ability to perform
+      advantage of the true power of HPCC Systems--the ability to perform
       operations using Massively Parallel Processing (MPP). This section
       provides the steps to expand your single-node system into a multi-node
       system using the Configuration Manager Wizard.</para>
@@ -813,7 +813,7 @@ gpgcheck=0</programlisting></para>
 
         <orderedlist>
           <listitem>
-            <para>If it is running, stop the HPCC system, using this
+            <para>If it is running, stop the HPCC Systems platform, using this
             command:</para>
 
             <xi:include href="Installing_and_RunningTheHPCCPlatform/Inst-Mods/SysDStop.xml"
@@ -833,7 +833,7 @@ gpgcheck=0</programlisting></para>
                       <entry><inlinegraphic
                       fileref="images/OSSgr3.png" /></entry>
 
-                      <entry>You can use this command to confirm HPCC
+                      <entry>You can use this command to confirm HPCC Systems
                       processes are stopped:<para><programlisting>sudo systemctl status hpccsystems-platform.target</programlisting></para></entry>
                     </row>
                   </tbody>
@@ -888,7 +888,7 @@ gpgcheck=0</programlisting></para>
           <listitem>
             <?dbfo keep-together="always"?>
 
-            <para>Enter all the IP addresses you want to use for this HPCC.
+            <para>Enter all the IP addresses you want to use for this HPCC Systems cluster.
             Alternatively, you could enter the hostname(s).</para>
 
             <para>The IP addresses do not need to be contiguous. In the image
@@ -1102,9 +1102,9 @@ sudo cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/environment.
 
           <listitem>
             <para>If you have added new machines to the cluster, you need to
-            copy and install the HPCC package onto all nodes, and generate and
+            copy and install the HPCC Systems package onto all nodes, and generate and
             clone the SSH keys. This can be done using the install-cluster.sh
-            script which is provided with HPCC. Use the following
+            script which is provided with HPCC Systems. Use the following
             command:</para>
 
             <programlisting>/opt/HPCCSystems/sbin/install-cluster.sh -k &lt;package-file-name&gt;</programlisting>
@@ -1124,7 +1124,7 @@ sudo cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/environment.
             role="bold">every</emphasis> node.</para>
 
             <para>You may want to create a script to push out the XML file to
-            all nodes. A sample script is provided with HPCC. The following
+            all nodes. A sample script is provided with HPCC Systems. The following
             command copies the XML files out to all nodes as required:</para>
 
             <para><programlisting>sudo /opt/HPCCSystems/sbin/hpcc-push.sh -s &lt;sourcefile&gt; -t &lt;destinationfile&gt;
@@ -1140,9 +1140,9 @@ sudo cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/environment.
 
         <orderedlist continuation="continues">
           <listitem>
-            <para>Restart the HPCC system on <emphasis
+            <para>Restart the HPCC Systems on <emphasis
             role="bold">every</emphasis> node. The following command starts
-            the HPCC system on an individual node:</para>
+             HPCC Systems on an individual node:</para>
 
             <xi:include href="Installing_and_RunningTheHPCCPlatform/Inst-Mods/SysDStart.xml"
                         xpointer="element(/1)"
@@ -1163,14 +1163,14 @@ sudo cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/environment.
 
                     <entry><para>You may want to use a script to push this
                     command out to every node. A sample script is provided
-                    with HPCC. Use the following command to start HPCC on all
+                    with HPCC Systems. Use the following command to start HPCC Systems on all
                     nodes:</para><para><programlisting>sudo /opt/HPCCSystems/sbin/hpcc-run.sh systemctl start hpccsystems-platform.target</programlisting></para></entry>
                   </row>
                 </tbody>
               </tgroup>
             </informaltable>
 
-            <para>This script can also be used to stop HPCC on all nodes and
+            <para>This script can also be used to stop HPCC Systems on all nodes and
             to start and stop individual components on all nodes. See the
             appendix (<link linkend="Example-Scripts">Appendix:Example
             Scripts</link>) for more details.</para>
@@ -1180,7 +1180,7 @@ sudo cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/environment.
         <sect3 id="Addl_SSH_KeyInfo">
           <title>Additional SSH Key Information</title>
 
-          <para>On a multi-node HPCC system, certificates and SSH keys must
+          <para>On multi-node HPCC Systems, certificates and SSH keys must
           all match across all nodes for the system to work properly. If you
           used the <emphasis>install-cluster.sh</emphasis> script as outlined
           in the steps above, this would make sure that everything is properly
@@ -1219,7 +1219,7 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
         <sect3 id="StartStop_ToStartSystem">
           <title>To start the system:</title>
 
-          <para>To start your HPCC system issue the following command;</para>
+          <para>To start your HPCC Systems platform issue the following command;</para>
 
           <xi:include href="Installing_and_RunningTheHPCCPlatform/Inst-Mods/SysDStart.xml"
                       xpointer="element(/1)"
@@ -1232,7 +1232,7 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
         <sect3 id="StartStop_StopTheSystem">
           <title>To stop the system:</title>
 
-          <para>To stop your HPCC system issue the following command;</para>
+          <para>To stop your HPCC Systems platform issue the following command;</para>
 
           <xi:include href="Installing_and_RunningTheHPCCPlatform/Inst-Mods/SysDStop.xml"
                       xpointer="element(/1)"
@@ -1289,7 +1289,7 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
 
         <orderedlist>
           <listitem>
-            <para>If the system is running, stop the HPCC system, using this
+            <para>If the system is running, stop the HPCC Systems platform, using this
             command on <emphasis role="bold">every</emphasis> node:</para>
 
             <xi:include href="Installing_and_RunningTheHPCCPlatform/Inst-Mods/SysDStop.xml"
@@ -1340,14 +1340,14 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
     <title>More Examples</title>
 
     <para>This section contains additional ECL examples you can use on your
-    HPCC cluster. You can run these on a single-node system or a larger
+    HPCC Systems cluster. You can run these on a single-node system or a larger
     multi-node cluster.</para>
 
     <sect1 id="IR_AnagramExamples" role="nobrk">
       <title>Anagram Examples</title>
 
-      <para>The following examples display some of things that HPCC can do.
-      Running through these examples will help your understanding of HPCC and
+      <para>The following examples display some of things that HPCC Systems can do.
+      Running through these examples will help your understanding of HPCC Systems and
       ECL.</para>
 
       <xi:include href="Installing_and_RunningTheHPCCPlatform/Inst-Mods/anagram1.xml"
@@ -1364,7 +1364,7 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
     <title>Next Steps</title>
 
     <para>Available from the menu in the ECL IDE there are several documents
-    which provide details on various aspects of the HPCC.</para>
+    which provide details on various aspects of the HPCC Systems.</para>
 
     <para>You can access them from the help menu: Help <emphasis
     role="bold">&gt;&gt;</emphasis> Documentation.</para>
@@ -1390,7 +1390,7 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
     <para>To familiarize yourself with what your system can do we recommend
     following the steps in<itemizedlist spacing="compact">
         <listitem>
-          <para>The <emphasis role="bold">HPCC Data Tutorial</emphasis></para>
+          <para>The <emphasis role="bold">HPCC Systems Data Tutorial</emphasis></para>
         </listitem>
 
         <listitem>
@@ -1400,7 +1400,7 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
 
         <listitem>
           <para>Read <emphasis role="bold">Using Config Manager</emphasis> to
-          learn how to configure an HPCC platform using Advanced View.</para>
+          learn how to configure an HPCC Systems platform using Advanced View.</para>
         </listitem>
 
         <listitem>
@@ -1488,7 +1488,7 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
                 <row>
                   <entry>&lt;package-name&gt;</entry>
 
-                  <entry>Name of the HPCC package to install. Required</entry>
+                  <entry>Name of the HPCC Systems package to install. Required</entry>
                 </row>
 
                 <row>
@@ -1538,7 +1538,7 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
           </listitem>
 
           <listitem>
-            <para>installs the HPCC platform package(s) on all nodes
+            <para>installs the HPCC Systems platform package(s) on all nodes
             specified.</para>
           </listitem>
 
@@ -1568,7 +1568,7 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
         <para><?hard-pagebreak ?><emphasis
         role="bold">Examples:</emphasis></para>
 
-        <para>This example installs the HPCC Platform packages to remaining
+        <para>This example installs the HPCC Systems platform packages to remaining
         nodes and pushes out the active environment.xml file to those
         nodes.:</para>
 
@@ -1577,7 +1577,7 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
 
         <para>(where <emphasis>n.n.nnnn</emphasis> is the build number)</para>
 
-        <para>This example installs the HPCC Platform packages to all nodes
+        <para>This example installs the HPCC Systems platform packages to all nodes
         and pushes out the active environment.xml file to those nodes. It also
         generates ssh keys and pushes them out to all nodes.</para>
 
@@ -1586,7 +1586,7 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
 
         <para>(where <emphasis>n.n.nnnn</emphasis> is the build number)</para>
 
-        <para>This example installs the HPCC Platform packages and pushes out
+        <para>This example installs the HPCC Systems platform packages and pushes out
         the active environment.xml file to 8 concurrent nodes.:</para>
 
         <para><programlisting>sudo /opt/HPCCSystems/sbin/install-cluster.sh -n 8 hpccsystems-platform-xxxx-<emphasis>n.n.nnnn</emphasis> 
@@ -1688,7 +1688,7 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
           </informaltable></para>
 
         <para>The <emphasis role="bold">deploy-java-files.sh</emphasis>
-        script, is used to deploy java files (source) to HPCC cluster hosts
+        script, is used to deploy java files (source) to HPCC Systems cluster hosts
         and update the classpath variable in environment.conf.</para>
 
         <para>This script runs a command on all IP addresses or host names in
@@ -1802,7 +1802,7 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
                 <row>
                   <entry>-c, --comp</entry>
 
-                  <entry>HPCC component. For example, dali@mydali.service,
+                  <entry>HPCC Systems component. For example, dali@mydali.service,
                   roxie@myroxie.service, etc.</entry>
                 </row>
 
@@ -1865,9 +1865,9 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
     </sect1>
 
     <sect1 id="Uninstalling-the-HPCC">
-      <title>Uninstalling the HPCC Platform</title>
+      <title>Uninstalling the HPCC Systems Platform</title>
 
-      <para>To uninstall the HPCC platform, issue the appropriate commands for
+      <para>To uninstall the HPCC Systems platform, issue the appropriate commands for
       your system. If necessary, do so on each node that it is installed
       on.</para>
 
@@ -1915,7 +1915,7 @@ init_start_thor--></property></para>
       <title>hpcc-init</title>
 
       <para>CentOS 6 and other System V based operating systems do not support
-      the systemd calls utilized by the HPCC System. We will continue to
+      the systemd calls utilized by HPCC Systems. We will continue to
       support the old System V style init.d calls.</para>
 
       <para><emphasis role="bold">hpcc-init
@@ -2016,7 +2016,7 @@ init_start_thor--></property></para>
           </tgroup>
         </informaltable>The <emphasis role="bold">hpcc-init
       </emphasis>function is used to start, stop, restart, setup, or check the
-      status of any or all HPCC components.</para>
+      status of any or all HPCC Systems components.</para>
 
       <?hard-pagebreak ?>
 
@@ -2032,7 +2032,7 @@ sudo /etc/init.d/hpcc-init -c esp start
 </programlisting>
 
       <sect2 id="HPCC_systemd_svc">
-        <title>HPCC systemd services</title>
+        <title>HPCC Systems systemd services</title>
 
         <para>HPCC Systems is extending support and development to more
         systemd services. We intend to continue support for Cent OS 6 and
@@ -2040,7 +2040,7 @@ sudo /etc/init.d/hpcc-init -c esp start
         system service will support "start", "stop" and "restart"
         options.</para>
 
-        <para>The reporting and logging for HPCC systemd will differ from the
+        <para>The reporting and logging for HPCC Systems systemd will differ from the
         previous hpcc-init type. The systemd logs do not have any output to
         STDOUT/STDERROR, instead it logs to /var/log/syslog. To view the
         output:</para>
@@ -2060,14 +2060,14 @@ sudo /etc/init.d/hpcc-init -c esp start
 
         <programlisting>/etc/init.d/hpcc-init status</programlisting>
 
-        <para>HPCC services started through systemd will be listed as active
+        <para>HPCC Systems services started through systemd will be listed as active
         in systemd. They can be listed as "sudo systemctl list-units
         [PATTERN...]". To remove them from the systemd active service list,
         you must run the stop service from the "service" or "systemctl"
         commands (as shown above) even though it is already stopped by
         directly calling /etc/init.d/&lt;hpcc-init|dafilesrv&gt; stop.</para>
 
-        <para>HPCC uninstall will automatically remove HPCC services from
+        <para>HPCC Systems uninstall will automatically remove HPCC Systems services from
         active list and /etc/systemd/system/ directory.</para>
       </sect2>
     </sect1>
@@ -2129,7 +2129,7 @@ sudo /etc/init.d/hpcc-init -c esp start
         </listitem>
 
         <listitem>
-          <para>Install the HPCC ECL IDE (Double-click the setup.msi file and
+          <para>Install the HPCC Systems ECL IDE (Double-click the installation file and
           Wine will install it).</para>
         </listitem>
       </orderedlist>
@@ -2139,10 +2139,10 @@ sudo /etc/init.d/hpcc-init -c esp start
       <title>External Language Support</title>
 
       <para>This section covers the steps to add external language support to
-      the HPCC platform. HPCC offers support for several programming
+      the HPCC Systems platform. HPCC Systems offers support for several programming
       languages, some have additional dependencies that must be installed.
       External language support is included with the platform installation
-      package, however there are RPM-based HPCC Platform installation packages
+      package, however there are RPM-based HPCC Systems platform installation packages
       that explicitly state <emphasis role="bold">with
       plugins</emphasis>.</para>
 
@@ -2192,7 +2192,7 @@ sudo /etc/init.d/hpcc-init -c esp start
       </itemizedlist>
 
       <para>The following sections detail what is required to utilize these
-      languages in your HPCC platform.</para>
+      languages in your HPCC Systems platform.</para>
 
       <para>In addition to these languages, you can add support for additional
       languages by creating your own plugin. This is not very difficult to do.
@@ -2203,7 +2203,7 @@ sudo /etc/init.d/hpcc-init -c esp start
       <sect2 id="Add_On_Java" role="brk">
         <title>Java</title>
 
-        <para>You can run external Java code on the HPCC platform. Compiled
+        <para>You can run external Java code on the HPCC Systems platform. Compiled
         Java can be used either as a .class (or a .jar) and called from ECL
         just like any other ECL function.</para>
 
@@ -2211,7 +2211,7 @@ sudo /etc/init.d/hpcc-init -c esp start
 
         <programlisting>javap -s</programlisting>
 
-        <para>To set up Java to integrate with the HPCC platform:</para>
+        <para>To set up Java to integrate with the HPCC Systems platform:</para>
 
         <orderedlist>
           <listitem>
@@ -2238,7 +2238,7 @@ sudo /etc/init.d/hpcc-init -c esp start
                 <listitem>
                   <para>using classpath value in environment.conf</para>
 
-                  <para>The default configuration file for the HPCC platform
+                  <para>The default configuration file for the HPCC Systems platform
                   is <emphasis
                   role="bold">/etc/HPCCSystems/environment.conf</emphasis> you
                   will need to edit this file to point to your Java build
@@ -2267,7 +2267,7 @@ sudo /etc/init.d/hpcc-init -c esp start
 
             <para>For more information see the <link
             linkend="Starting-and-stopping">Starting-and-stopping</link> the
-            HPCC System in the <emphasis>Installing and Running The HPCC
+            HPCC Systems platform in the <emphasis>Installing and Running The HPCC Systems
             Platform</emphasis> document.</para>
           </listitem>
 
@@ -2288,7 +2288,7 @@ integer add1(integer val) := IMPORT(java, 'JavaCat.add1:(I)I');
 
 add1(10);
 </programlisting>If this successfully executes, you have correctly set up Java
-            to work with your HPCC platform.</para>
+            to work with your HPCC Systems platform.</para>
 
             <para>If you get a "unable to load libjvm.so" error you should
             reinstall or try a different Java package.</para>
@@ -2298,7 +2298,7 @@ add1(10);
         <para>You can call Java from ECL just like any other ECL function.
         Java static functions can be easily prototyped using ECL types.</para>
 
-        <para>Additional examples of Java for HPCC can be found at:</para>
+        <para>Additional examples of Java for HPCC Systems can be found at:</para>
 
         <para><ulink
         url="https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/ecl/embedjava.ecl">https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/ecl/embedjava.ecl</ulink></para>
@@ -2359,9 +2359,9 @@ ENDEMBED;
 
 add1(10);
 </programlisting>If this successfully executes, you have correctly set up
-            JavaScript to work with your HPCC platform.</para>
+            JavaScript to work with your HPCC Systems platform.</para>
 
-            <para>Additional examples of HPCC code can be found at:</para>
+            <para>Additional examples of HPCC Systems code can be found at:</para>
 
             <para><ulink
             url="https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/ecl/embedjava.ecl">https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/ecl/embedjava.ecl</ulink></para>
@@ -2372,7 +2372,7 @@ add1(10);
       <sect2 id="Add_Python_support" role="brk">
         <title>Python</title>
 
-        <para>HPCC supports Python2 by default. The HPCC platform includes
+        <para>HPCC Systems supports Python2 by default. The HPCC Systems platform includes
         plugins for both Python2 and Python3, but only one may be safely
         enabled at a time as the Python libraries export the same symbols for
         both versions. Enabling both may lead to unpredictable results
@@ -2430,10 +2430,10 @@ ENDEMBED;
 split_words('Once upon a time');
 
 </programlisting>If this successfully executes, you have correctly set up
-            Python to work with your HPCC platform. You can now embed Python
-            anywhere you would use ECL within with your HPCC System.</para>
+            Python to work with your HPCC Systems platform. You can now embed Python
+            anywhere you would use ECL within with your HPCC Systems platform.</para>
 
-            <para>Additional examples of HPCC code can be found at:</para>
+            <para>Additional examples of HPCC Systems code can be found at:</para>
 
             <para><ulink
             url="https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/regress/ecl">https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/regress/ecl/</ulink></para>
@@ -2441,7 +2441,7 @@ split_words('Once upon a time');
         </orderedlist>
 
         <para>In order for Python to work properly it is important that the
-        version of Python and the HPCC system are set up correctly to support
+        version of Python and HPCC Systems are set up correctly to support
         using the installed version of Python. If you see "ld: cannot find
         --lpy2embed" error then your system is likely set up for Python3.
         Likewise, if you see "ld: cannot find --lpy3embed" then your system is
@@ -2484,7 +2484,7 @@ split_words('Once upon a time');
       <sect2 id="R" role="brk">
         <title>R</title>
 
-        <para>The HPCC Platform supports embedded R code. To enable R support
+        <para>The HPCC Systems platform supports embedded R code. To enable R support
         within The HPCC Systems<superscript>®</superscript> Platform:</para>
 
         <orderedlist>
@@ -2630,9 +2630,9 @@ s1b :=DATASET(250000, TRANSFORM({ integer a }, SELF.a := COUNTER+1));
 s2b :=DATASET(250000, TRANSFORM({ integer a }, SELF.a := (COUNTER/2)+1));
 SUM(NOFOLD(s1b + s2b), a); 
 </programlisting>If this successfully executes, you have correctly set up R to
-            work with your HPCC platform.</para>
+            work with your HPCC Systems platform.</para>
 
-            <para>Additional examples of HPCC code can be found at:</para>
+            <para>Additional examples of HPCC Systems code can be found at:</para>
 
             <para><ulink
             url="https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/ecl/regress/embedR.ecl">https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/regress/ecl/embedR.ecl</ulink></para>
@@ -2647,7 +2647,7 @@ SUM(NOFOLD(s1b + s2b), a);
           <para>Some additional considerations for mapping data types in
           R.</para>
 
-          <para>In HPCC the ECL <emphasis role="bold">RECORD</emphasis> maps
+          <para>In HPCC Systems the ECL <emphasis role="bold">RECORD</emphasis> maps
           to an R <emphasis>list</emphasis>.</para>
 
           <para>An ECL <emphasis role="bold">DATASET</emphasis> including a
@@ -2657,8 +2657,8 @@ SUM(NOFOLD(s1b + s2b), a);
           <para>An ECL <emphasis role="bold">SET</emphasis> is mapped to an R
           <emphasis>vector</emphasis>.</para>
 
-          <para>These principals apply to passing data from HPCC to R or data
-          returning to HPCC from R. There are usage examples of these concepts
+          <para>These principals apply to passing data from HPCC Systems to R or data
+          returning to HPCC Systems from R. There are usage examples of these concepts
           available at:</para>
 
           <para><ulink

docs/EN_US/InstantCloud/InstantCloud.xml

@@ -307,7 +307,7 @@
             <para>Click on the <emphasis role="bold">Launch Cluster
             </emphasis>link at the top.</para>
 
-            <para>The <emphasis role="bold">Launch a New HPCC Cluster
+            <para>The <emphasis role="bold">Launch a New HPCC Systems Cluster
             </emphasis>window displays.</para>
 
             <para></para>
@@ -315,8 +315,8 @@
         </orderedlist></para>
     </sect1>
 
-    <sect1 id="InstaCloud_LaunchNewHPCC">
-      <title>Launch a New HPCC Cluster</title>
+    <sect1 id="InstaCloud_LaunchNew">
+      <title>Launch a New HPCC Systems Cluster</title>
 
       <para>In this section, you will launch a set of Ubuntu machines to use
       for your HPCC Systems Thor platform. The Instant Cloud page uses the
@@ -358,7 +358,7 @@
         </listitem>
 
         <listitem>
-          <para>Creates the internal user (HPCC).</para>
+          <para>Creates the internal user (hpcc).</para>
         </listitem>
 
         <listitem>
@@ -646,14 +646,14 @@
           role="bold">C</emphasis>ontrol <emphasis
           role="bold">L</emphasis>anguage (ECL) is a declarative, data centric
           programming language used to manage all aspects of the massive data
-          joins, sorts, and builds that truly differentiate HPCC (High
+          joins, sorts, and builds that truly differentiate HPCC Systems (High
           Performance Computing Cluster) from other technologies in its
           ability to provide flexible data analysis on a massive scale.</para>
         </footnote> code using either ECL IDE, the command line ECL compiler,
       or the ECLPlus tool.</para>
 
       <sect2 id="IC_InstallECLIDEandClienTools">
-        <title>Install the ECL IDE and HPCC Client Tools</title>
+        <title>Install the ECL IDE and HPCC Systems Client Tools</title>
 
         <para>You only need to install the ECL IDE once. If you have already
         installed it, you can skip this section.</para>
@@ -856,7 +856,7 @@
               target cluster.</para>
 
               <para><emphasis role="bold">Thor</emphasis> is the Data Refinery
-              component of your HPCC. It is a disk based massively parallel
+              component of your HPCC Systems. It is a disk based massively parallel
               computer cluster, optimized for sorting, manipulating, and
               transforming massive data.</para>
 
@@ -947,7 +947,7 @@
             <para>Open the ECL IDE (<emphasis role="bold">Start</emphasis>
             &gt;&gt; <emphasis role="bold">All Programs</emphasis> &gt;&gt;
             <emphasis role="bold">HPCC Systems</emphasis> &gt;&gt; ECL IDE )
-            and login to your HPCC.</para>
+            and login to your HPCC Systems.</para>
           </listitem>
 
           <listitem>
@@ -1059,8 +1059,8 @@ OUTPUT(L);</programlisting></para>
         <title>Load the Dictionary File to your Landing Zone</title>
 
         <para>In this step, you will copy the data files to a location from
-        which it can be sprayed to your HPCC Thor cluster. A Landing Zone is a
-        storage location attached to your HPCC. It has a utility running to
+        which it can be sprayed to your HPCC Systems Thor cluster. A Landing Zone is a
+        storage location attached to your HPCC Systems. It has a utility running to
         facilitate file spraying to a cluster.</para>
 
         <para>For smaller data files, maximum of 2GB, you can use the
@@ -1068,7 +1068,7 @@ OUTPUT(L);</programlisting></para>
         kb.</para>
 
         <para>Next you will distribute (or Spray) the dataset to all the nodes
-        in the HPCC Thor cluster. The power of the HPCC comes from its ability
+        in the HPCC Systems Thor cluster. The power of the HPCC Systems comes from its ability
         to assign multiple processors to work on different portions of the
         data file in parallel. Even though the VM Edition only has a single
         node, the data must be sprayed to the cluster.</para>
@@ -1147,7 +1147,7 @@ OUTPUT(L);</programlisting></para>
         <title>Spray the Data File to your <emphasis>Thor
         Cluster</emphasis></title>
 
-        <para>To use the data file in our HPCC Thor system, we must "spray" it
+        <para>To use the data file in our HPCC Systems Thor system, we must "spray" it
         to all the nodes. A <emphasis>spray</emphasis> or
         <emphasis>import</emphasis> is the relocation of a data file from one
         location (such as a Landing Zone) to multiple file parts on nodes in a
@@ -1488,7 +1488,7 @@ s3cmd --configure
     <para>To familiarize yourself with what your system can do, we recommend
     following the steps in:<itemizedlist spacing="compact">
         <listitem>
-          <para>The <emphasis role="bold">HPCC Data Tutorial</emphasis></para>
+          <para>The <emphasis role="bold">HPCC Systems Data Tutorial</emphasis></para>
         </listitem>
 
         <listitem>
@@ -1498,7 +1498,7 @@ s3cmd --configure
 
         <listitem>
           <para>Read <emphasis role="bold">Using Config Manager</emphasis> to
-          learn how to configure an HPCC platform using Advanced View.</para>
+          learn how to configure an HPCC Systems platform using Advanced View.</para>
         </listitem>
 
         <listitem>

docs/EN_US/One-Click_HPCCinAWS/One-Click_RuningHPCCinAmazonWebServicesEC2.xml

@@ -307,7 +307,7 @@
             <para>Click on the <emphasis role="bold">Launch Cluster
             </emphasis>link at the top.</para>
 
-            <para>The <emphasis role="bold">Launch a New HPCC Cluster
+            <para>The <emphasis role="bold">Launch a New HPCC Systems Cluster
             </emphasis>window displays.</para>
 
             <para></para>
@@ -316,7 +316,7 @@
     </sect1>
 
     <sect1>
-      <title>Launch a New HPCC Cluster</title>
+      <title>Launch a New HPCC Systems Cluster</title>
 
       <para>In this section, you will launch a set of Ubuntu 12.04 machines to
       use for your HPCC Systems Thor platform. The Instant Cloud page uses the
@@ -358,7 +358,7 @@
         </listitem>
 
         <listitem>
-          <para>Creates the internal user (HPCC).</para>
+          <para>Creates the internal user (hpcc).</para>
         </listitem>
 
         <listitem>
@@ -646,14 +646,13 @@
           role="bold">C</emphasis>ontrol <emphasis
           role="bold">L</emphasis>anguage (ECL) is a declarative, data centric
           programming language used to manage all aspects of the massive data
-          joins, sorts, and builds that truly differentiate HPCC (High
-          Performance Computing Cluster) from other technologies in its
+          joins, sorts, and builds that truly differentiate HPCC Systems from other technologies in its
           ability to provide flexible data analysis on a massive scale.</para>
         </footnote> code using either ECL IDE, the command line ECL compiler,
       or the ECLPlus tool.</para>
 
       <sect2>
-        <title>Install the ECL IDE and HPCC Client Tools</title>
+        <title>Install the ECL IDE and HPCC Systems Client Tools</title>
 
         <para>You only need to install the ECL IDE once. If you have already
         installed it, you can skip this section. .</para>
@@ -841,7 +840,7 @@
               target cluster.</para>
 
               <para><emphasis role="bold">Thor</emphasis> is the Data Refinery
-              component of your HPCC. It is a disk based massively parallel
+              component of your HPCC Systems. It is a disk based massively parallel
               computer cluster, optimized for sorting, manipulating, and
               transforming massive data.</para>
 
@@ -932,7 +931,7 @@
             <para>Open the ECL IDE (<emphasis role="bold">Start</emphasis>
             &gt;&gt; <emphasis role="bold">All Programs</emphasis> &gt;&gt;
             <emphasis role="bold">HPCC Systems</emphasis> &gt;&gt; ECL IDE )
-            and login to your HPCC.</para>
+            and login to your HPCC Systems.</para>
           </listitem>
 
           <listitem>
@@ -1044,8 +1043,8 @@ OUTPUT(L);</programlisting></para>
         <title>Load the Dictionary File to your Landing Zone</title>
 
         <para>In this step, you will copy the data files to a location from
-        which it can be sprayed to your HPCC Thor cluster. A Landing Zone is a
-        storage location attached to your HPCC. It has a utility running to
+        which it can be sprayed to your HPCC Systems platform Thor cluster. A Landing Zone is a
+        storage location attached to your HPCC Systems platform. It has a utility running to
         facilitate file spraying to a cluster.</para>
 
         <para>For smaller data files, maximum of 2GB, you can use the
@@ -1053,7 +1052,7 @@ OUTPUT(L);</programlisting></para>
         kb.</para>
 
         <para>Next you will distribute (or Spray) the dataset to all the nodes
-        in the HPCC Thor cluster. The power of the HPCC comes from its ability
+        in the HPCC Systems Thor cluster. The power of the HPCC Systems comes from its ability
         to assign multiple processors to work on different portions of the
         data file in parallel. Even though the VM Edition only has a single
         node, the data must be sprayed to the cluster.</para>
@@ -1141,7 +1140,7 @@ OUTPUT(L);</programlisting></para>
         <title>Spray the Data File to your <emphasis>Thor
         Cluster</emphasis></title>
 
-        <para>To use the data file in our HPCC Thor system, we must "spray" it
+        <para>To use the data file in our HPCC Systems Thor system, we must "spray" it
         to all the nodes. A <emphasis>spray</emphasis> or
         <emphasis>import</emphasis> is the relocation of a data file from one
         location (such as a Landing Zone) to multiple file parts on nodes in a
@@ -1516,7 +1515,7 @@ s3cmd --configure
     <para>To familiarize yourself with what your system can do, we recommend
     following the steps in:<itemizedlist spacing="compact">
         <listitem>
-          <para>The <emphasis role="bold">HPCC Data Tutorial</emphasis></para>
+          <para>The <emphasis role="bold">HPCC Systems Data Tutorial</emphasis></para>
         </listitem>
 
         <listitem>
@@ -1526,7 +1525,7 @@ s3cmd --configure
 
         <listitem>
           <para>Read <emphasis role="bold">Using Config Manager</emphasis> to
-          learn how to configure an HPCC platform using Advanced View.</para>
+          learn how to configure an HPCC Systems platform using Advanced View.</para>
         </listitem>
 
         <listitem>

docs/EN_US/RoxieReference/RoxieRefMods/RoxieCopySettings.xml

@@ -111,7 +111,7 @@
     not otherwise specified Roxie copies from clusters in its own environment
     first. To enable the Preferred Clusters feature, you can use the HPCC
     Systems Configuration Manager. (for additional information about
-    Configuring your HPCC System see <emphasis>Installing and Running the HPCC
+    Configuring HPCC Systems see <emphasis>Installing and Running the HPCC Systems
     Platform</emphasis>)<figure>
         <title>Roxie Preferred Clusters</title>
 
@@ -123,7 +123,7 @@
       </figure></para>
 
     <para>The Preferred Clusters tab can be found on the RoxieCluster page
-    within the HPCC Configuration Manager.</para>
+    within the HPCC Systems Configuration Manager.</para>
 
     <para>On the Preferred Clusters tab, you can add the name and the priority
     of your Roxie clusters. The highest priority number is the preferred
@@ -150,7 +150,7 @@
     callers to select the right set of queries when calling through a
     VIP.</para>
 
-    <para>This setting can be found in the Topology section within the HPCC
+    <para>This setting can be found in the Topology section within the HPCC Systems
     Configuration Manager.</para>
 
     <para><figure>

docs/EN_US/RoxieReference/RoxieRefMods/directAccessToRoxie.xml

@@ -73,7 +73,7 @@
     <sect2>
       <title><emphasis role="bold">ESP and WsECL</emphasis></title>
 
-      <para>A standard installation of the HPCC platform includes an
+      <para>A standard installation of the HPCC Systems platform includes an
       Enterprise Services Platform (ESP) with the WsECL service configured
       through a service binding to port 8002 (configurable).</para>
 
@@ -150,7 +150,7 @@
 
         <para>8002 is the default port. If you have a modified the port
         setting, use the port you have selected for that purpose. With the 7.0
-        release of HPCC you will need to enter your credentials to log in to
+        release of HPCC Systems you will need to enter your credentials to log in to
         the interface, and your session will lock after a (configurable)
         period of inactivity.</para>
 

docs/EN_US/RoxieReference/RoxieReference.xml

@@ -413,7 +413,7 @@
       <para></para>
 
       <para><emphasis role="bold">Note</emphasis>: These steps are explained
-      in detail in the HPCC Data Tutorial and the Programmer's Guide.</para>
+      in detail in the HPCC Systems Data Tutorial and the Programmer's Guide.</para>
     </sect1>
 
     <sect1 id="Methods-to-Submit-Jobs-to-a-Roxie-Cluster">
@@ -585,7 +585,7 @@ ecl queries recreate roxie MyQuery --timeLimit=2000
       <orderedlist>
         <listitem>
           <para>Use ECL IDE to write your query and then compile it setting
-          the target as the roxie cluster in your HPCC environment.</para>
+          the target as the roxie cluster in your HPCC Systems environment.</para>
         </listitem>
 
         <listitem>
@@ -600,7 +600,7 @@ ecl queries recreate roxie MyQuery --timeLimit=2000
       <title>Viewing Query Sets using ECL Watch</title>
 
       <para>Using ECL Watch, you can view the query for all clusters on your
-      HPCC. Click on the <emphasis role="bold">Query Sets/Browse</emphasis>
+      HPCC Systems platform. Click on the <emphasis role="bold">Query Sets/Browse</emphasis>
       menu item to see the clusters which are currently using Query Sets.
       Click on the <emphasis role="bold">myroxie</emphasis> link to view the
       list of queries currently available for roxie. Using this feature you
@@ -649,7 +649,7 @@ ecl queries recreate roxie MyQuery --timeLimit=2000
     <sect1>
       <title>Using WsECL to run a roxie query</title>
 
-      <para>WsECL is the ECL Web Service interface that is provided with HPCC
+      <para>WsECL is the ECL Web Service interface that is provided with HPCC Systems
       and is available using the following URL: http://nnn.nnn.nnn.nnn:8002,
       where nnn.nnn.nnn.nnn is the IP address of your ESP.</para>
 
@@ -973,7 +973,7 @@ ecl queries recreate roxie MyQuery --timeLimit=2000
 
     <para>This section contains information for performing preflight checks on
     a Roxie cluster. For details about other components, see the
-    <emphasis>HPCC System Administrator's Guide</emphasis>.</para>
+    <emphasis>HPCC Systems Administrator's Guide</emphasis>.</para>
 
     <xi:include href="HPCCCertify/Cert-Mods/CertPreflight.xml"
                 xpointer="xpointer(//*[@id='Preflight_Roxie'])"

docs/EN_US/RuningHPCCinAmazonWebServicesEC2/RuningHPCCinAmazonWebServicesEC2.xml

@@ -289,7 +289,7 @@
                     <para><emphasis role="bold">TCP ports 1-65535</emphasis>
                     (for internal access only)</para>
 
-                    <para>Type the Group ID for the HPCC group in the Source
+                    <para>Type the Group ID for the HPCC Systems group in the Source
                     text box.</para>
                   </listitem>
 
@@ -297,7 +297,7 @@
                     <para><emphasis role="bold">UDP ports 1-65535</emphasis>
                     (for internal access only)</para>
 
-                    <para>Type the Group ID for the HPCC group in the Source
+                    <para>Type the Group ID for the HPCC Systems group in the Source
                     text box.</para>
                   </listitem>
 
@@ -307,7 +307,7 @@
 
                     <para>Add a custon ICMP rule for Echo Request.</para>
 
-                    <para>Type the Group ID for the HPCC group in the Source
+                    <para>Type the Group ID for the HPCC Systems group in the Source
                     text box.</para>
                   </listitem>
 
@@ -317,7 +317,7 @@
 
                     <para>Add a custon ICMP rule for Echo Reply.</para>
 
-                    <para>Type the Group ID for the HPCC group in the Source
+                    <para>Type the Group ID for the HPCC Systems group in the Source
                     text box.</para>
                   </listitem>
                 </itemizedlist></para>
@@ -411,7 +411,7 @@
               </listitem>
 
               <listitem>
-                <para>Use the HPCC security group created earlier.</para>
+                <para>Use the HPCC Systems (HPCC) security group created earlier.</para>
               </listitem>
 
               <listitem>
@@ -669,7 +669,7 @@
             </listitem>
           </orderedlist>
 
-          <para>You are now ready to use your HPCC Thor platform. You can
+          <para>You are now ready to use your HPCC Systems Thor platform. You can
           follow the basic samples found later in this guide or try some of
           the suggestions in the <link linkend="NextSteps">Next Steps chapter.
           </link></para>
@@ -926,7 +926,7 @@
           </listitem>
 
           <listitem>
-            <para>Select the HPCC Security Group (if not already
+            <para>Select the HPCC Systems Security Group (if not already
             selected).</para>
 
             <para>You should see the details below. You may need to resize the
@@ -986,9 +986,9 @@
 
       <sect2 role="brk">
         <title>Open up additional TCP ports (8002, 8008, 8010, 8015, 8145,
-        8050, and 9876) for HPCC services</title>
+        8050, and 9876) for HPCC Systems services</title>
 
-        <para>This allows external access to HPCC services using a
+        <para>This allows external access to HPCC Systems services using a
         browser-based interface and the ECL IDE on your local machine.</para>
 
         <para><informaltable colsep="0" frame="none" rowsep="0">
@@ -1421,7 +1421,7 @@
             <para><programlisting>http://s3.amazonaws.com/hpccsystems-installs/userdatascripts.html</programlisting></para>
 
             <para>The user-data script you choose will determine which version
-            of the HPCC platform to instantiate. Older versions will remain
+            of the HPCC Systems platform to instantiate. Older versions will remain
             available so you can recreate any version of a platform. This
             allows you to continue using the version you are familiar with and
             upgrade when you want to.</para>
@@ -1460,7 +1460,7 @@
                   </row>
 
                   <row>
-                    <entry>Installs the latest stable release of the HPCC
+                    <entry>Installs the latest stable release of the HPCC Systems
                     platform package</entry>
                   </row>
 
@@ -1475,7 +1475,7 @@
                   </row>
 
                   <row>
-                    <entry>Installs supplemental packages for HPCC</entry>
+                    <entry>Installs supplemental packages for HPCC Systems</entry>
                   </row>
                 </tbody>
               </tgroup>
@@ -1570,7 +1570,7 @@
           </listitem>
         </orderedlist>
 
-        <para>You now have an un-configured cluster with the HPCC Platform
+        <para>You now have an un-configured cluster with the HPCC Systems platform
         software installed. Continue on to configure your cluster.</para>
 
         <para><informaltable colsep="1" frame="all" rowsep="1">
@@ -1619,7 +1619,7 @@
       <para>Note in the instance details (bottom frame) that each instance has
       a private and a public IP address that can be derived from the private
       and public DNS entries (your entries will be different). You will need
-      the private IPs later when using the HPCC Configuration Manager.</para>
+      the private IPs later when using the HPCC Systems Configuration Manager.</para>
 
       <para><figure>
           <title>Instance Details</title>
@@ -1659,7 +1659,7 @@
               <entry>Private IPs are for inter-node communications. Public DNS
               names are for communicating to a node from outside the cloud.
               <emphasis role="bold">You will need the private IPs later when
-              using the HPCC Configuration Manager. You will also need to know
+              using the HPCC Systems Configuration Manager. You will also need to know
               the public DNS name of your ESP node and your Landing Zone
               node.</emphasis></entry>
             </row>
@@ -1672,7 +1672,7 @@
       <title>Collect the Private IP addresses of your nodes.</title>
 
       <para>The EC2 instances are given random IP addresses and are usually
-      not contiguous. The HPCC Configuration Manager needs a list of IPs as
+      not contiguous. The HPCC Systems Configuration Manager needs a list of IPs as
       input criteria.</para>
 
       <para>If you have only a few nodes, you can collect this information
@@ -1735,7 +1735,7 @@
         </listitem>
 
         <listitem>
-          <para>Copy the list of IPs and later paste into the HPCC
+          <para>Copy the list of IPs and later paste into the HPCC Systems
           Configuration Manager (see the next section)</para>
         </listitem>
       </orderedlist>
@@ -1746,7 +1746,7 @@
 
       <para>At this point, your nodes are running and the HPCC Systems
       platform packages and all dependencies are installed. In this section,
-      you will use the HPCC's Configuration Manager to configure your HPCC
+      you will use the HPCC Systems Configuration Manager to configure your HPCC
       Systems Thor platform.</para>
 
       <para>If you are using PuTTY, you should use PuTTYgen to convert the
@@ -1804,7 +1804,7 @@
 
       <sect2>
         <title>Access the Configuration Manager's Wizard interface to generate
-        your HPCC environment configuration file</title>
+        your HPCC Systems environment configuration file</title>
 
         <orderedlist numeration="arabic">
           <listitem>
@@ -1842,7 +1842,7 @@
           <listitem>
             <para><emphasis role="bold">Leave the Roxie set to 0.</emphasis>
             For details on using a Roxie cluster, see the <emphasis>Installing
-            and Running the HPCC Platform</emphasis> manual. Details on
+            and Running the HPCC Systems platform</emphasis> manual. Details on
             running a Roxie cluster on AWS will appear in a future
             manual.</para>
           </listitem>
@@ -2108,14 +2108,14 @@
           role="bold">C</emphasis>ontrol <emphasis
           role="bold">L</emphasis>anguage (ECL) is a declarative, data centric
           programming language used to manage all aspects of the massive data
-          joins, sorts, and builds that truly differentiate HPCC (High
+          joins, sorts, and builds that truly differentiate HPCC Systems (High
           Performance Computing Cluster) from other technologies in its
           ability to provide flexible data analysis on a massive scale.</para>
         </footnote> code using either ECL IDE, the command line ECL compiler,
       or the ECLPlus tool.</para>
 
       <sect2>
-        <title>Install the ECL IDE and HPCC Client Tools</title>
+        <title>Install the ECL IDE and HPCC Systems Client Tools</title>
 
         <para>You only need to install the ECL IDE once. If you have already
         installed it, you can skip this section. .</para>
@@ -2168,7 +2168,7 @@
                   </mediaobject>
                 </figure></para>
 
-              <para>Follow the link to the HPCC System's portal.</para>
+              <para>Follow the link to the HPCC Systems portal.</para>
             </listitem>
 
             <listitem>
@@ -2304,7 +2304,7 @@
               target cluster.</para>
 
               <para><emphasis role="bold">Thor</emphasis> is the Data Refinery
-              component of your HPCC. It is a disk based massively parallel
+              component of your HPCC Systems. It is a disk based massively parallel
               computer cluster, optimized for sorting, manipulating, and
               transforming massive data.</para>
 
@@ -2395,7 +2395,7 @@
             <para>Open the ECL IDE (<emphasis role="bold">Start</emphasis>
             &gt;&gt; <emphasis role="bold">All Programs</emphasis> &gt;&gt;
             <emphasis role="bold">HPCC Systems</emphasis> &gt;&gt; ECL IDE )
-            and login to your HPCC.</para>
+            and login to your HPCC Systems.</para>
           </listitem>
 
           <listitem>
@@ -2507,8 +2507,8 @@ OUTPUT(L);</programlisting></para>
         <title>Load the Dictionary File to your Landing Zone</title>
 
         <para>In this step, you will copy the data files to a location from
-        which it can be sprayed to your HPCC Thor cluster. A Landing Zone is a
-        storage location attached to your HPCC. It has a utility running to
+        which it can be sprayed to your HPCC Systems Thor cluster. A Landing Zone is a
+        storage location attached to your HPCC Systems. It has a utility running to
         facilitate file spraying to a cluster.</para>
 
         <para>For smaller data files, maximum of 2GB, you can use the
@@ -2516,7 +2516,7 @@ OUTPUT(L);</programlisting></para>
         kb.</para>
 
         <para>Next you will distribute (or Spray) the dataset to all the nodes
-        in the HPCC Thor cluster. The power of the HPCC comes from its ability
+        in the HPCC Systems Thor cluster. The power of the HPCC Systems comes from its ability
         to assign multiple processors to work on different portions of the
         data file in parallel. Even though the VM Edition only has a single
         node, the data must be sprayed to the cluster.</para>
@@ -2603,7 +2603,7 @@ OUTPUT(L);</programlisting></para>
         <title>Spray the Data File to your <emphasis>Thor
         Cluster</emphasis></title>
 
-        <para>To use the data file in our HPCC Thor system, we must "spray" it
+        <para>To use the data file in our HPCC Systems Thor system, we must "spray" it
         to all the nodes. A <emphasis>spray</emphasis> or
         <emphasis>import</emphasis> is the relocation of a data file from one
         location (such as a Landing Zone) to multiple file parts on nodes in a
@@ -3074,7 +3074,7 @@ s3cmd --configure
     <para>To familiarize yourself with what your system can do, we recommend
     following the steps in:<itemizedlist spacing="compact">
         <listitem>
-          <para>The <emphasis role="bold">HPCC Data Tutorial</emphasis></para>
+          <para>The <emphasis role="bold">HPCC Systems Data Tutorial</emphasis></para>
         </listitem>
 
         <listitem>
@@ -3084,7 +3084,7 @@ s3cmd --configure
 
         <listitem>
           <para>Read <emphasis role="bold">Using Config Manager</emphasis> to
-          learn how to configure an HPCC platform using Advanced View.</para>
+          learn how to configure an HPCC Systems platform using Advanced View.</para>
         </listitem>
 
         <listitem>
@@ -3203,7 +3203,7 @@ s3cmd --configure
 
         <qandaentry>
           <question>
-            <para>Can I use a Mac workstation to access my HPCC Thor on
+            <para>Can I use a Mac workstation to access my HPCC Systems Thor on
             AWS?</para>
           </question>
 

docs/EN_US/RunningHPCCinaVirtualMachine/RunningHPCCinaVirtualMachine.xml

@@ -2,10 +2,10 @@
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
 <book id="Running_HPCC_In_A_Virtual_Machine" lang="en_US" xml:base="../">
-  <title>Running HPCC in a Virtual Machine</title>
+  <title>Running HPCC Systems in a Virtual Machine</title>
 
   <bookinfo>
-    <title>HPCC in a Virtual Machine</title>
+    <title>HPCC Systems in a Virtual Machine</title>
 
     <mediaobject>
       <imageobject>
@@ -67,7 +67,7 @@
     <title>Introduction</title>
 
     <para>These instructions will guide you through installing and running an
-    HPCC<footnote>
+    HPCC Systems<superscript>®</superscript><footnote>
         <para><emphasis role="bold">H</emphasis>igh <emphasis
         role="bold">P</emphasis>erformance <emphasis
         role="bold">C</emphasis>omputing <emphasis
@@ -76,23 +76,22 @@
         <ulink
         url="http://hpccsystems.com/Why-HPCC/How-it-works">http://hpccsystems.com/Why-HPCC/How-it-works</ulink>
         for more details.</para>
-      </footnote> System on a single node inside a Linux virtual machine
+      </footnote> on a single node inside a Linux virtual machine
     running on a Windows host.</para>
 
     <para>Packaged to run inside a virtual machine, this version provides a
-    hands-on experience with an HPCC system. You can experiment with it and
+    hands-on experience with HPCC Systems. You can experiment with it and
     even create real-world data analytics applications-all on your desktop or
     laptop PC.</para>
 
-    <para>This version includes the tools and functionality of an HPCC without
+    <para>This version includes the tools and functionality of an HPCC Systems without
     the need for a physical cluster of servers. It provides enough for you to
-    evaluate an HPCC system and learn to use ECL<footnote>
+    evaluate HPCC Systems and learn to use ECL<footnote>
         <para><emphasis role="bold">E</emphasis>nterprise <emphasis
         role="bold">C</emphasis>ontrol <emphasis
         role="bold">L</emphasis>anguage (ECL) is a declarative, data-centric
         programming language used to manage all aspects of the massive data
-        joins, sorts, and builds that truly differentiate HPCC (High
-        Performance Computing Cluster) from other technologies in its ability
+        joins, sorts, and builds that truly differentiate HPCC Systems<superscript>®</superscript> from other technologies in its ability
         to provide flexible data analysis on a massive scale.</para>
       </footnote>. Naturally, you do not get the power of parallel processing,
     but you can use this version as an evaluation, learning, and
@@ -121,7 +120,7 @@
     <sect1 id="VM_Requirements">
       <title>System Requirements</title>
 
-      <para>Running HPCC in a virtual machine requires (at minimum):</para>
+      <para>Running HPCC Systems in a virtual machine requires (at minimum):</para>
 
       <itemizedlist>
         <listitem>
@@ -158,7 +157,7 @@
       <para>Users should have familiarity with installing and running Windows
       applications.</para>
 
-      <para>To run HPCC in a virtual machine, hardware virtualization must be
+      <para>To run the HPCC Systems platform in a virtual machine, hardware virtualization must be
       enabled in the BIOS of your machine. This setting may be called VT-x or
       AMD-V.</para>
     </sect1>
@@ -167,17 +166,17 @@
   <chapter id="VM_GettingTheTools">
     <title>Getting the Tools and the VM Image</title>
 
-    <para>To run the virtual machine version of the HPCC System, you need
+    <para>To run the virtual machine version of the HPCC Systems platform, you need
     virtualization software. These packages allow you to run virtual images
     inside a single host. There are a several different vendors who make
     virtualization software, while any or all of these could work, we support
-    Oracle VM VirtualBox<superscript>®</superscript> .</para>
+    Oracle VM VirtualBox<superscript>®</superscript>.</para>
 
     <sect1 id="VM_VirtualBox">
       <title>VM VirtualBox</title>
 
       <para>Oracle's virtualization software, VM VirtualBox is supported for
-      running the HPCC virtual machine image.</para>
+      running the HPCC Systems virtual machine image.</para>
 
       <para>In the following section(s), you will:</para>
 
@@ -187,7 +186,7 @@
         </listitem>
 
         <listitem>
-          <para>Download the HPCC virtual machine image from HPCC
+          <para>Download the HPCC Systems virtual machine image from HPCC
           Systems.</para>
         </listitem>
 
@@ -235,11 +234,11 @@
       </sect2>
 
       <sect2 id="VM_ImportVirtualImage">
-        <title id="get_HPCC">Import the HPCC Virtual Image File</title>
+        <title id="get_HPCC">Import the HPCC Systems Virtual Image File</title>
 
         <para><orderedlist>
             <listitem>
-              <para>Download the latest HPCC virtual machine image file
+              <para>Download the latest HPCC Systems virtual machine image file
               from:</para>
 
               <para><ulink
@@ -295,7 +294,7 @@
               pressing <emphasis role="bold">Next</emphasis> as appropriate,
               then press <emphasis role="bold">Import</emphasis>.</para>
 
-              <para>Wait for the HPCC virtual machine to import. This may take
+              <para>Wait for the HPCC Systems virtual machine to import. This may take
               a few minutes.</para>
             </listitem>
 
@@ -446,18 +445,18 @@
           </orderedlist></para>
 
         <para>Note the IP address provided. You will use this address to
-        connect to ECL Watch, and interact with HPCC.</para>
+        connect to ECL Watch, and interact with HPCC Systems.</para>
       </sect2>
     </sect1>
   </chapter>
 
   <chapter id="VM_RunningHPCC_VM">
-    <title>Running the HPCC VM</title>
+    <title>Running the HPCC Systems VM</title>
 
-    <para>In this section, we will access the HPCC using the web-based
+    <para>In this section, we will access the HPCC Systems using the web-based
     interface: ECL Watch<footnote>
-        <para>ECL Watch is a Web-based interface to your HPCC system. It
-        enables you to examine and manage many aspects of the HPCC and allows
+        <para>ECL Watch is a Web-based interface to your HPCC Systems instance. It
+        enables you to examine and manage many aspects of HPCC Systems and allows
         you to see information about jobs you run, data files, and system
         metrics.</para>
       </footnote>.From ECL Watch, we will download the ECL IDE<footnote>
@@ -465,7 +464,7 @@
         used to create queries into your data and ECL files with which to
         build your queries. This is a Windows application.</para>
       </footnote>. If you already have the ECL IDE installed, you can skip
-    this section and continue at <emphasis>Running the HPCC ECL IDE when you
+    this section and continue at <emphasis>Running the HPCC Systems ECL IDE when you
     had a previous version installed</emphasis>.</para>
 
     <para><orderedlist>
@@ -515,7 +514,7 @@
               </mediaobject>
             </figure></para>
 
-          <para>Follow the link to the HPCC System's portal download
+          <para>Follow the link to the HPCC Systems portal download
           page.</para>
         </listitem>
 
@@ -642,13 +641,13 @@
           <para>Press the <emphasis role="bold">OK</emphasis> button.</para>
 
           <para>At this point you are now connected and ready to work with the
-          HPCC!</para>
+          HPCC Systems!</para>
         </listitem>
       </orderedlist>
     </sect1>
 
     <sect1 id="VM_RunningtheIDE_wPreviousVersion">
-      <title>Running the HPCC ECL IDE when you had a previous version
+      <title>Running the HPCC Systems ECL IDE when you had a previous version
       installed</title>
 
       <orderedlist>
@@ -740,7 +739,7 @@
         <listitem>
           <para>Press the <emphasis role="bold">OK</emphasis> button.</para>
 
-          <para>You are now connected and ready to work with the HPCC!</para>
+          <para>You are now connected and ready to work with the HPCC Systems platform!</para>
         </listitem>
       </orderedlist>
     </sect1>
@@ -749,7 +748,7 @@
       <title>Write some ECL</title>
 
       <para>Let's write, compile, and execute a simple "Hello World" program
-      on our HPCC.</para>
+      on our HPCC Systems platform.</para>
 
       <orderedlist>
         <listitem>
@@ -799,7 +798,7 @@
           cluster.</para>
 
           <para><emphasis role="bold">Thor</emphasis> is the Data Refinery
-          component of your HPCC. It is a massively parallel computer cluster,
+          component of your HPCC Systems. It is a massively parallel computer cluster,
           optimized for sorting, manipulating, and transforming massive data.
           This process is also known as ETL (Extract, Transform, and
           Load)</para>
@@ -892,14 +891,14 @@
     <sect1 id="VM_Working_with_a_data_file">
       <title>Working with data files</title>
 
-      <para>Once you start working with your HPCC system, you will want to
+      <para>Once you start working with your HPCC Systems, you will want to
       process some real data, this section shows you how to load data to your
-      HPCC system.</para>
+      HPCC Systems platform.</para>
 
       <sect2 id="VM_Cautions_and_Warnings">
         <title>Before you begin</title>
 
-        <para>A typical production HPCC system would have much more data
+        <para>A typical production HPCC Systems platform would have much more data
         capacity than using a virtual system for testing purposes. The size of
         the file you wish to work with is limited by the size of your virtual
         machine.</para>
@@ -1114,7 +1113,7 @@
       <title>Next Steps</title>
 
       <para>Available from the menu in ECL Watch are several documents which
-      provide details on various aspects of the HPCC.</para>
+      provide details on various aspects of the HPCC Systems.</para>
 
       <figure>
         <title>ECL Watch Resource Page</title>
@@ -1146,7 +1145,7 @@
 
       <para><itemizedlist>
           <listitem>
-            <para>The <emphasis role="bold">HPCC Data
+            <para>The <emphasis role="bold">HPCC Systems Data
             Tutorial</emphasis></para>
 
             <para>This is a simple, step-by-step tutorial that shows the
@@ -1236,7 +1235,7 @@
           </question>
 
           <answer>
-            <para>The HPCC VM Edition runs on a single node, has a limit of 20
+            <para>The HPCC Systems VM Edition runs on a single node, has a limit of 20
             GB in it workspace, and doesn't support custom
             configurations.</para>
           </answer>
@@ -1248,7 +1247,7 @@
           </question>
 
           <answer>
-            <para>You can run the HPCC VM using the Linux VM Player. The HPCC
+            <para>You can run the HPCC Systems VM using the Linux VM Player. The HPCC Systems
             ECL IDE is a Windows application, but can run under WINE. See the
             Client Tools Manual for details.</para>
           </answer>
@@ -1295,7 +1294,7 @@
 
           <answer>
             <para>Yes. Community Edition binaries run natively on 64-bit Linux
-            server(s). You can access that HPCC from any Windows workstation
+            server(s). You can access HPCC Systems from any Windows workstation
             (32- or 64-bit) that can run the ECL IDE and a supported
             browser.</para>
           </answer>

docs/EN_US/VisualizingECL/VizMods/VizIntro.xml

@@ -4,7 +4,7 @@
 <chapter id="VizIntro">
   <title><emphasis>Visualization Introduction</emphasis></title>
 
-  <para>The Visualization bundle is an open-source add-on to the HPCC platform
+  <para>The Visualization bundle is an open-source add-on to the HPCC Systems<superscript>®</superscript> platform
   to allow you to create visualizations from the results of queries written in
   ECL.</para>
 
@@ -18,7 +18,7 @@
   part of a solution; we must be able to make sense of the data, too. Data
   visualizations simplify the complex.</para>
 
-  <para>The Visualizer bundle extends the HPCC platform's functionality by
+  <para>The Visualizer bundle extends the HPCC Systems platform's functionality by
   allowing you to plot your data onto charts, graphs, and maps to add a visual
   representation that can be easily understood.</para>
 

docs/EN_US/WsSQLUG/WsSQL_ESPWebServiceGuide.xml

@@ -54,11 +54,11 @@
     <title>Introduction</title>
 
     <para>The WsSQL Web service is an add-on service that provides an SQL
-    interface into HPCC Systems. The Web service accepts a subset of prepared
-    and standard SQL queries. This provides access to most HPCC data and
+    interface into HPCC Systems<superscript>®</superscript>. The Web service accepts a subset of prepared
+    and standard SQL queries. This provides access to most HPCC Systems data and
     published queries over HTTP or HTTPS using SOAP or REST interfaces.</para>
 
-    <para>The WsSQL service maps HPCC logical files to RDBMS tables. HPCC
+    <para>The WsSQL service maps HPCC Systems logical files to RDBMS tables. HPCC Systems
     Published Queries are exposed as RDBMS Stored Procedures.</para>
 
     <para>The WsSQL service also provides convenient methods to obtain system
@@ -69,23 +69,23 @@
     fashion by users who are more comfortable using SQL than ECL. This makes
     it possible to submit ad-hoc queries without learning ECL.</para>
 
-    <para>The service exposes HPCC logical files as RDB tables.</para>
+    <para>The service exposes HPCC Systems logical files as RDB tables.</para>
 
     <para><itemizedlist mark="bullet">
         <listitem>
-          <para>HPCC Logical File &lt;-&gt; RDB Table</para>
+          <para>HPCC Systems Logical File &lt;-&gt; RDB Table</para>
         </listitem>
 
         <listitem>
-          <para>HPCC Record Fields &lt;-&gt; RDB Table Columns</para>
+          <para>HPCC Systems Record Fields &lt;-&gt; RDB Table Columns</para>
         </listitem>
 
         <listitem>
-          <para>HPCC Published query &lt;-&gt; RDB Stored Procedure</para>
+          <para>HPCC Systems Published query &lt;-&gt; RDB Stored Procedure</para>
         </listitem>
 
         <listitem>
-          <para>Provides HPCC system and data RDB metadata</para>
+          <para>Provides HPCC Systems with system and data RDB metadata</para>
         </listitem>
 
         <listitem>
@@ -97,7 +97,7 @@
         </listitem>
 
         <listitem>
-          <para>Provides means for utilizing HPCC index files for faster
+          <para>Provides means for utilizing HPCC Systems index files for faster
           reads.</para>
 
           <para></para>
@@ -107,7 +107,7 @@
     <sect1>
       <title>Supported File Types</title>
 
-      <para>The WsSQL service supports all HPCC file types except :</para>
+      <para>The WsSQL service supports all HPCC Systems file types except :</para>
 
       <para><itemizedlist>
           <listitem>
@@ -125,7 +125,7 @@
             which contain the record definition in the logical file's
             metadata.</emphasis> Sprayed files do not contain this metadata.
             This metadata exists on any file or index which is written to the
-            HPCC Distributed File System (DFS). Sprayed data files typically
+            HPCC Systems Distributed File System (DFS). Sprayed data files typically
             undergo some processing and an OUTPUT of the transformed data to
             disk before use, so this should not interfere with the service's
             usefulness. You can use the
@@ -141,7 +141,7 @@
   <chapter>
     <title>Setup</title>
 
-    <para>The WsSQL service is included in the HPCC Platform. </para>
+    <para>The WsSQL service is included in the HPCC Systems platform. </para>
 
     <sidebar>
       <para>Prior to version 7.0, WsSQL was an add-on product and was
@@ -292,11 +292,11 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
   </chapter>
 
   <chapter>
-    <title>Using HPCC Files as a data source</title>
+    <title>Using HPCC Systems Files as a data source</title>
 
     <para>Once installed and configured, the WsSQL service will process
     submitted SQL statements and generate dynamic ECL code. The code is
-    submitted to and executed by your HPCC Platform. The result set is
+    submitted to and executed by your HPCC Systems platform. The result set is
     returned to your application.</para>
 
     <para><variablelist>
@@ -308,7 +308,7 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
             which contain the record definition in the logical file's
             metadata.</emphasis> Sprayed files do not contain this metadata.
             This metadata exists on any file or index which is written to the
-            HPCC Distributed File System (DFS). Sprayed data files typically
+            HPCC Systems Distributed File System (DFS). Sprayed data files typically
             undergo some processing and an OUTPUT of the transformed data to
             disk before use, so this should not interfere with the service's
             usefulness. You can use the
@@ -320,7 +320,7 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
         </varlistentry>
       </variablelist></para>
 
-    <para>In addition, you can utilize indexes on the HPCC in one of two
+    <para>In addition, you can utilize indexes on the HPCC Systems in one of two
     ways:</para>
 
     <orderedlist numeration="arabic">
@@ -334,7 +334,7 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
       </listitem>
 
       <listitem>
-        <para>Specify the related indexes in the HPCC logical file
+        <para>Specify the related indexes in the HPCC Systems logical file
         description.</para>
       </listitem>
     </orderedlist>
@@ -344,7 +344,7 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
 
       <para>The WsSQL service attempts to perform index based reads whenever
       possible. However, in order to take advantage of index reads, the target
-      HPCC files need to be annotated with the pertinent index file names.
+      HPCC Systems files need to be annotated with the pertinent index file names.
       This is accomplished by adding the following key/value entry on the
       file's description using ECL Watch.</para>
 
@@ -437,14 +437,14 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
         <para><emphasis role="bold">GetDBSystemInfo</emphasis></para>
 
         <para>You can use this method to gather version information from the
-        HPCC Platform.</para>
+        HPCC Systems platform.</para>
       </listitem>
 
       <listitem>
         <para><emphasis role="bold">GetMetadata</emphasis></para>
 
         <para>This method provides metadata you can use to create a view or
-        model of the target HPCC system as a SQL accessible DB. You can
+        model of the target HPCC Systems platform as a SQL accessible DB. You can
         request Tables, Stored Procedures, and/or Targetclusters.</para>
       </listitem>
 
@@ -498,7 +498,7 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
         creates a new table and loads the data from the source file creating a
         table (logical file) that WsSQL can use. This function is intended to
         use when you have a logical file without metadata or to import a new
-        file into an HPCC platform.</para>
+        file into an HPCC Systems platform.</para>
       </listitem>
 
       <listitem>
@@ -708,37 +708,37 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
                 <row>
                   <entry><programlisting role="wsig">  FullVersion</programlisting></entry>
 
-                  <entry>Full Version of HPCC Platform</entry>
+                  <entry>Full Version of the HPCC Systems platform</entry>
                 </row>
 
                 <row>
                   <entry><programlisting role="wsig">  Major</programlisting></entry>
 
-                  <entry>Major of HPCC Platform</entry>
+                  <entry>Major version of the HPCC Systems platform</entry>
                 </row>
 
                 <row>
                   <entry><programlisting role="wsig">  Minor</programlisting></entry>
 
-                  <entry>Minor of HPCC Platform</entry>
+                  <entry>Minor version of the HPCC Systems platform</entry>
                 </row>
 
                 <row>
                   <entry><programlisting role="wsig">  Point</programlisting></entry>
 
-                  <entry>Point of HPCC Platform</entry>
+                  <entry>Point of HPCC Systems platform</entry>
                 </row>
 
                 <row>
                   <entry><programlisting role="wsig">  Project</programlisting></entry>
 
-                  <entry>Project of HPCC Platform</entry>
+                  <entry>Project of HPCC Systems platform</entry>
                 </row>
 
                 <row>
                   <entry><programlisting role="wsig">  Maturity</programlisting></entry>
 
-                  <entry>Maturity of HPCC Platform</entry>
+                  <entry>Maturity of HPCC Systems platform</entry>
                 </row>
 
                 <row>
@@ -785,15 +785,15 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
     <sect1>
       <title>GetDBMetaData</title>
 
-      <para>This methods allows you to query the HPCC Platform and get
-      metadata to use to create a view or model of the target HPCC system as a
+      <para>This methods allows you to query the HPCC Systems platform and get
+      metadata to use to create a view or model of the target HPCC Systems as a
       SQL accessible DB.</para>
 
       <para>You can request one or more of the followinfg:</para>
 
       <itemizedlist>
         <listitem>
-          <para>Tables (Logical files in the HPCC Cluster)</para>
+          <para>Tables (Logical files in the HPCC Systems Cluster)</para>
         </listitem>
 
         <listitem>
@@ -1334,8 +1334,8 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
 
                   <entry>N</entry>
 
-                  <entry>User Name to pass to HPCC. This is used as the job
-                  owner name in HPCC</entry>
+                  <entry>User Name to pass to HPCC Systems. This is used as the job
+                  owner name in HPCC Systems</entry>
                 </row>
 
                 <row>
@@ -1935,7 +1935,7 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
                   <entry>N</entry>
 
                   <entry>The username to use as the job's ownername in the
-                  HPCC platform</entry>
+                  HPCC Systems platform</entry>
                 </row>
 
                 <row>
@@ -2101,11 +2101,11 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
     <sect1 id="CreateTableAndLoad">
       <title>CreateTableAndLoad</title>
 
-      <para>This method creates a table (HPCC logical file) which can
+      <para>This method creates a table (HPCC Systems logical file) which can
       subsequently be accessed using WsSQL. The table is assigned the layout
       as specified in the request ECLFields section. The table is then
       populated with data from an existing file. The source data file can
-      either reside on the HPCC Landing Zone after being uploaded, or it can
+      either reside on the HPCC Systems Landing Zone after being uploaded, or it can
       already have been sprayed on to the system.</para>
 
       <sect2>
@@ -2192,8 +2192,8 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
 
                   <entry>Y</entry>
 
-                  <entry>The name of the table to create in the HPCC
-                  Platform's distributed file system.</entry>
+                  <entry>The name of the table to create in the HPCC Systems
+                  platform's distributed file system.</entry>
                 </row>
 
                 <row>
@@ -2320,7 +2320,7 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
 
                   <entry>Y**</entry>
 
-                  <entry>IP address or hostname of the HPCC Landing
+                  <entry>IP address or hostname of the HPCC Systems Landing
                   Zone</entry>
                 </row>
 
@@ -3242,7 +3242,7 @@ Joe Smith CA
 </programlisting>
 
       <para>The interface supports SQL index hints, which gives the SQL user
-      the option to specify the most appropriate HPCC index for the current
+      the option to specify the most appropriate HPCC Systems index for the current
       SQL query. This also allows you to disable the use of an index.</para>
 
       <para><emphasis role="bold">select
@@ -3567,8 +3567,8 @@ Select Firstname from persons where lastname = 'Jones' and zip &gt; '33445'   /*
       role="bold">]]<emphasis role="bold">[;]</emphasis></emphasis></para>
 
       <para>The CREATE TABLE and LOAD DATA SQL statements allow you to create
-      a file in an HPCC cluster that is accessible via WsSQL. You can populate
-      the new file from data in a logical file already on the HPCC cluster or
+      a file in an HPCC Systems cluster that is accessible via WsSQL. You can populate
+      the new file from data in a logical file already on the HPCC Systems cluster or
       one that is on a landing zone.</para>
 
       <para>All Create requests MUST be accompanied by a Load request. You
@@ -3585,7 +3585,7 @@ Select Firstname from persons where lastname = 'Jones' and zip &gt; '33445'   /*
               <row>
                 <entry><emphasis>newtablename</emphasis></entry>
 
-                <entry>The logical filename to create on the HPCC cluster.
+                <entry>The logical filename to create on the HPCC Systems cluster.
                 <emphasis role="bold">Note: </emphasis>Create and Load must
                 target the same file.</entry>
               </row>
@@ -3601,7 +3601,7 @@ Select Firstname from persons where lastname = 'Jones' and zip &gt; '33445'   /*
                 <entry><emphasis>sourcetablename</emphasis></entry>
 
                 <entry>The source file from which to extract data to load into
-                the new table. This can be a logical file on an HPCC cluster
+                the new table. This can be a logical file on an HPCC Systems cluster
                 or a physical file on a landing zone. For a landing zone file,
                 you MUST provide a <emphasis role="bold">connection</emphasis>
                 '<emphasis>landingzoneIP</emphasis>' and a <emphasis
@@ -3614,7 +3614,7 @@ Select Firstname from persons where lastname = 'Jones' and zip &gt; '33445'   /*
               <row>
                 <entry><emphasis>landingzoneIP</emphasis></entry>
 
-                <entry>The IP Address or hostname of the HPCC Landing
+                <entry>The IP Address or hostname of the HPCC Systems Landing
                 Zone</entry>
               </row>
 
@@ -3819,7 +3819,7 @@ INTO TABLE newCustomerFile4CSV
         <sect3>
           <title>Reserved SQL Keywords</title>
 
-          <para>Your HPCC identifiers (field names, Stored Procedure names,
+          <para>Your HPCC Systems identifiers (field names, Stored Procedure names,
           etc) cannot use SQL reserved words such as:</para>
 
           <programlisting>ADD ALL ANY AS ASC AT AVG BETWEEN BOOL BOOLEAN BY CALL COLUMN CONTAINS COUNT 
@@ -3831,7 +3831,7 @@ SUM TABLE TRUE UPPER USE WHERE XOR DIV MOD OR AND</programlisting>
         <sect3>
           <title>Special Characters</title>
 
-          <para>Your HPCC filenames should avoid special characters other
+          <para>Your HPCC Systems filenames should avoid special characters other
           than:</para>
 
           <programlisting>( 'A'..'Z' | 'a'..'z' | '' | '$') ( 'A'..'Z' | 'a'..'z' | '' | '$' | '0'..'9' )