Removed reference to traditional, Spec. Guides (#2775)

* Removed reference to traditional, Spec. Guides.

* Cont.

* Cont.

modules/specialized-guides/pages/large-deployments/overview.adoc

@@ -10,13 +10,6 @@ There is no hard maximum number of supported systems.
 Many factors can affect how many clients can reliably be used in a particular installation.
 Factors can include which features are used, and how the hardware and systems are configured.
 
-
-[WARNING]
-====
-Large installations require standard Salt clients.
-These instructions cannot be used in environments using traditional clients or Salt SSH minions.
-====
-
 There are two main ways to manage large scale deployments.
 You can manage them with a single {productname} Server, or you can use multiple servers in a hub.
 Both methods are described in this book.

modules/specialized-guides/pages/public-cloud-guide/payg/payg-overview.adoc

@@ -1,13 +1,17 @@
 = {payg} overview
-:description: {productname} {payg} or {payglongform} is a flexible and cost-effective solution that allows users to manage and monitor their systems. Unlike traditional subscription models, {payg} does not require a long-term subscription. Users can leverage the images of {productname} on a {payglongform} basis, paying only for the time of use, and the number of managed and monitored systems. {payg} with {productname} is an optimal solution for those seeking control, convenience, and cost savings when managing and monitoring their infrastructure on AWS, Azure, and GCP.
+:description: {productname} {payg} or {payglongform} is a flexible and cost-effective solution that allows users to manage and monitor their systems. 
+{payg} does not require a long-term subscription. 
+Users can leverage the images of {productname} on a {payglongform} basis, paying only for the time of use, and the number of managed and monitored systems. 
+{payg} with {productname} is an optimal solution for those seeking control, convenience, and cost savings when managing and monitoring their infrastructure on AWS, Azure, and GCP.
 :keywords: Payg, Pay-as-you-go, AWS, Amazon Web Services, Azure, GCP, Google Cloud Compute,  cost-effective, scaling, Cloud Services, {productname}, Monitoring
 
 
 == Introduction to {payg}
 
 {productname} {payg} or {payglongform} is a flexible and cost-effective solution that allows users to manage and monitor their systems from several cloud services. 
-Unlike traditional subscription models, {payg} does not require a long-term subscription through the {scc}. 
-Users can leverage images of {productname} on a {payglongform} basis, paying only for the time of use, and the number of **managed** and **monitored** systems. {payg} with {productname} is an optimal solution for those seeking control, convenience, and cost savings when managing and monitoring their infrastructure on AWS, Azure, and GCP.
+{payg} does not require a long-term subscription through the {scc}. 
+Users can leverage images of {productname} on a {payglongform} basis, paying only for the time of use, and the number of **managed** and **monitored** systems. 
+{payg} with {productname} is an optimal solution for those seeking control, convenience, and cost savings when managing and monitoring their infrastructure on AWS, Azure, and GCP.
 
 
 == Benefits of using {payg}

modules/specialized-guides/pages/salt/salt-overview.adoc

@@ -12,11 +12,3 @@ This book is designed to be a primer for using Salt with {productname}.
 For more information about Salt, see the Salt documentation at https://docs.saltstack.com/en/latest/contents.html.
 
 The current version of Salt in {productname} is {saltversion}.
-
-[NOTE]
-====
-Throughout the {productname} documentation, we use the term `Salt clients` to refer to Salt machines that are connected to and controlled by the Salt master on the {productname} Server.
-This is to clearly differentiate them from traditional clients.
-In other documentation, and in some internal references, Salt clients are sometimes referred to as Salt `minions` instead.
-This is a difference in terminology only.
-====

modules/specialized-guides/pages/salt/salt-terminology.adoc

@@ -52,8 +52,8 @@ The Salt master issues commands to its attached clients.
 In {productname}, the Salt master must be the {productname} Server.
 
 Minions::
-Salt clients that are connected to and controlled by the Salt master on the {productname} Server.
-In {productname}, these are referred to as Salt clients, in order to clearly differentiate them from traditional clients.
+Salt clients that are connected to and controlled by the {salt} master on the {productname} Server.
+In {productname}, these are sometimes referred to as {salt} clients.
 This is a difference in terminology only.
 
 Modules::