Corrections

Signed-off-by: Ian Maddaus <[email protected]>

Author: IanMadd

content/360/saas/_index.md

@@ -15,13 +15,13 @@ weight = 10
 
 Chef 360 SaaS focuses on job orchestration and node management in the cloud to complete your DevOPS journeys whenever, wherever, and however a business scenario requires. Chef 360 SaaS is hosted, maintained, and upgraded by Chef allowing you to focus on your workflows.
 
-**Whenever**: The Chef 360 SaaS Platform provides real-time observability of the changing infrastructure environment through scheduled actions, continuous scanning or immediate “execute-once" semantics.
+**Whenever**: Chef 360 SaaS provides real-time observability of the changing infrastructure environment through scheduled actions, continuous scanning or immediate “execute-once" semantics.
 
-**Wherever**: The Chef 360 SaaS Platform operates across hybrid environments from on-premises data centers through to all major public clouds, and secures the wide variety of platforms and resources supported by Chef.
+**Wherever**: Chef 360 SaaS operates across hybrid environments from on-premises data centers through to all major public clouds, and secures the wide variety of platforms and resources supported by Chef.
 
-**Whatever**: The Chef 360 SaaS Platform enables DevOps and security engineering teams—whether they follow ITIL or ChatOps—to leverage the native JSON syntax or use one of several, extensible infrastructure-as-code DSLs.
+**Whatever**: Chef 360 SaaS enables DevOps and security engineering teams—whether they follow ITIL or ChatOps—to leverage the native JSON syntax or use one of several, extensible infrastructure-as-code DSLs.
 
-The Chef 360 SaaS Platform has a workflow engine to execute varied jobs in compliance and infrastructure management:
+Chef 360 SaaS has a workflow engine to execute varied jobs in compliance and infrastructure management:
 
 - Regularly scan, audit, and remediate infrastructure, protecting your fleet with certified industry compliance profiles like CIS, SOC2, and CSPM.
 - Create composable jobs quickly using shell scripting and out-of-the-box skills to develop full playbooks, capable of coordinating the other DevOps IaC tools you own.

content/360/saas/get_started/_index.md

@@ -1,5 +1,5 @@
 +++
-title = "Get started with Chef 360 Platform on-prem"
+title = "Get started with Chef 360 SaaS"
 linkTitle = "Get started"
 
 [menu.cloud]
@@ -9,7 +9,7 @@ parent = "chef_cloud/360/get_started"
 weight = 10
 +++
 
-This section provides quickstart guides for getting started with Chef 360 Platform and its tools.
+This section provides quickstart guides for getting started with Chef 360 SaaS and its tools.
 
 ## Get started guides
 

content/360/saas/get_started/define_skills.md

@@ -20,7 +20,7 @@ A skill is an agent that gives you the ability to perform actions on a node to a
 
 ## Create skill definitions
 
-The following Chef 360 Platform skills are required or recommended for managing nodes, running actions, and returning action results:
+The following Chef 360 skills are required or recommended for managing nodes, running actions, and returning action results:
 
 - Courier Runner skill
 - Gohai skill

content/360/saas/get_started/enroll_nodes.md

@@ -8,7 +8,7 @@ parent = "chef_cloud/360/get_started"
 weight = 100
 +++
 
-Node enrollment brings nodes under management by Chef 360 Platform.
+Node enrollment brings nodes under management by Chef 360 SaaS.
 
 This document demonstrates two different methods of node enrollment:
 
@@ -17,7 +17,7 @@ This document demonstrates two different methods of node enrollment:
 
 {{< note >}}
 
-This version of Chef 360 Platform doesn't support node re-enrollment.
+This version of Chef 360 SaaS doesn't support node re-enrollment.
 
 {{< /note >}}
 
@@ -32,7 +32,7 @@ Review the [node requirements]({{< relref "system_requirements#node-requirements
 ## Single-node enrollment
 
 Single-node enrollment enrolls nodes from the server side.
-With this method, you define connection and configuration details and push them up to Chef 360 Platform, which connects to each node and installs Chef Habitat, Chef Node Management, and any skills or agents assigned to a node cohort.
+With this method, you define connection and configuration details and push them up to Chef 360 SaaS, which connects to each node and installs Chef Habitat, Chef Node Management, and any skills or agents assigned to a node cohort.
 
 ### Enroll Linux nodes
 
@@ -120,7 +120,7 @@ To enroll a Windows node, follow these steps:
 
 ## Cookbook-based enrollment
 
-With cookbook-based enrollment, you enroll nodes from the client side by uploading a [cookbook](https://docs.chef.io/cookbooks/) with enrollment settings to Chef Infra Server and then Chef Infra Client enrolls the node with Chef 360 Platform.
+With cookbook-based enrollment, you enroll nodes from the client side by uploading a [cookbook](https://docs.chef.io/cookbooks/) with enrollment settings to Chef Infra Server and then Chef Infra Client enrolls the node with Chef 360 SaaS.
 
 ### Enroll nodes
 
@@ -168,15 +168,15 @@ To configure the cookbooks and define enrollment settings, follow these steps:
 
     Replace:
 
-    - `<CHEF_360_FQDN>` with the fully qualified domain name (FQDN) for your Chef 360 Platform deployment.
+    - `<CHEF_360_FQDN>` with the fully qualified domain name (FQDN) for your Chef 360 SaaS deployment.
     - `<ENROLLMENT_TYPE>` with either `full` or `partial` depending on the form of enrollment. Use `full` unless you must `partial`.
-    - `<API_PORT>` with the API port configured in Chef 360 Platform. The default value is `31000`.
-    - `<ACCESS_KEY>` with an access key for secure communication with Chef 360 Platform. Store securely using an [encrypted Chef data bag](https://docs.chef.io/data_bags/) or a [secrets manager](https://docs.chef.io/infra_language/secrets/).
-    - `<SECRET_KEY>` with a secret key for secure communication with Chef 360 Platform. Store securely using an [encrypted Chef data bag](https://docs.chef.io/data_bags/) or a [secrets manager](https://docs.chef.io/infra_language/secrets/).
+    - `<API_PORT>` with the API port configured in Chef 360 SaaS. The default value is `31000`.
+    - `<ACCESS_KEY>` with an access key for secure communication with Chef 360 SaaS. Store securely using an [encrypted Chef data bag](https://docs.chef.io/data_bags/) or a [secrets manager](https://docs.chef.io/infra_language/secrets/).
+    - `<SECRET_KEY>` with a secret key for secure communication with Chef 360 SaaS. Store securely using an [encrypted Chef data bag](https://docs.chef.io/data_bags/) or a [secrets manager](https://docs.chef.io/infra_language/secrets/).
     - `<COHORT_ID>` with a valid cohort UUID. The cohort defines all skills and settings installed on the node.
     - `<HABITAT_BUILDER_URL>` with the URL of the Chef Habitat Builder used by your organization. Default value: `https://bldr.habitat.sh`
     - `<VALID_DIR_PATH>` with a temporary working directory where all required builds are downloaded. Specify a valid path based on the OS. Default value: `/tmp`.
-    - `<UPGRADE_SKILLS>` with `true` or `false`. If `true`, Chef 360 Platform checks for the latest skill versions and installs them if found. Default value: `false`.
+    - `<UPGRADE_SKILLS>` with `true` or `false`. If `true`, Chef 360 SaaS checks for the latest skill versions and installs them if found. Default value: `false`.
 
 1. Push the wrapper cookbook or policy to the Chef Infra Server.
 
@@ -195,7 +195,7 @@ To configure the cookbooks and define enrollment settings, follow these steps:
 
 1. Include the wrapper cookbook in your node's run-list by adding it to a role or Policyfile. See the [run-list](https://docs.chef.io/run_lists/) and [role](https://docs.chef.io/roles/#manage-roles) documentation for more information.
 
-   The next time Chef Infra Client runs, it executes the `node_management_enroll` resource and the node is enrolled with Chef 360 Platform.
+   The next time Chef Infra Client runs, it executes the `node_management_enroll` resource and the node is enrolled with Chef 360 SaaS.
 
 ## Check the node enrollment status
 

content/360/saas/get_started/install_cli.md

@@ -10,7 +10,7 @@ parent = "chef_cloud/360/get_started"
 weight = 40
 +++
 
-This page documents how to download and install the Chef 360 Platform CLIs and register your workstation with your Chef 360 Platform deployment.
+This page documents how to download and install the Chef 360 Platform CLIs and register your workstation with your Chef 360 SaaS deployment.
 
 ## Prerequisites
 
@@ -73,7 +73,7 @@ To create a profile, follow these steps:
 
     {{< note >}}
 
-    If you've configured Chef 360 Platform with a system-generated or custom certificate in the API/UI settings, use the following CLI arguments:
+    If you've configured Chef 360 SaaS with a system-generated or custom certificate in the API/UI settings, use the following CLI arguments:
 
     - If you don't have the root certificate authority, use the `--insecure` flag. This flag skips certificate validation.
     - If have the root certificate authority present, use the `--cafile <ABSOLUTE_PATH_TO_ROOT_CA_FILE>` flag.
@@ -86,7 +86,7 @@ To create a profile, follow these steps:
     - `<PROFILE_NAME>` with a profile name for the role that this profile will use. For example, add the `courier-operator` profile name for the `courier-operator` role.
     - `<TENANT_URL>` with the tenant URL, for example `https://chef360.example.com:31000`.
 
-    The CLI responds with an authorization code that includes a link to log into Chef 360 Platform.
+    The CLI responds with an authorization code that includes a link to log into Chef 360 SaaS.
 
     ```sh
     Device Id :  ac:de:48:00:11:22-admin-chef-courier-cli
@@ -106,19 +106,19 @@ To create a profile, follow these steps:
 
 1. Select the organization and role you would like to link to this profile and select **Submit**.
 
-    {{< figure src="/images/360/select-role.png" width="500px" alt="Chef 360 Platform organization and role selection screen." >}}
+    {{< figure src="/images/360/select-role.png" width="500px" alt="Chef 360 SaaS organization and role selection screen." >}}
 
-1. On the **Device Authorization** screen, Chef 360 Platform shows your OAuth code and you can select an expiration date for your session.
+1. On the **Device Authorization** screen, Chef 360 SaaS shows your OAuth code and you can select an expiration date for your session.
 
-   Chef 360 Platform automatically refreshes your access token up to this expiration date.
+   Chef 360 SaaS automatically refreshes your access token up to this expiration date.
 
    After entering this information, select **Authorize**.
 
-    {{< figure src="/images/360/setting-expiry-token.png" alt="Chef 360 Platform device authorization screen with OAuth token and expiration date." width="500px">}}
+    {{< figure src="/images/360/setting-expiry-token.png" alt="Chef 360 SaaS device authorization screen with OAuth token and expiration date." width="500px">}}
 
 1. Return to your terminal and enter `y` to continue.
 
-    The CLI displays your device profile and your workstation is authorized to access Chef 360 Platform services.
+    The CLI displays your device profile and your workstation is authorized to access Chef 360 SaaS services.
 
     ```sh
     Is the device authorised? (y or n)
@@ -159,6 +159,10 @@ To create a profile, follow these steps:
 
 1. Repeat this procedure so that you have separate profiles for the Node Manager and Courier Operator roles.
 
+## Additional information
+
+- [Chef 360 CLI reference documentation](https://docs.chef.io/360/1.2/reference/cli/)
+
 ## Next step
 
 - [Register the Node Management agent]({{< relref "register_node_agent.md" >}}).

content/360/saas/get_started/jobs.md

@@ -29,7 +29,7 @@ This job template creates a job that's executed one node, it runs immediately, a
 
 ## Create the job
 
-When you add the job to Chef 360 Platform, the Courier Dispatcher sends the job definition to the Courier Runner on the specified node which determines when and how to run the job.
+When you add the job to Chef 360 SaaS, the Courier Dispatcher sends the job definition to the Courier Runner on the specified node which determines when and how to run the job.
 You can submit a job definition using a JSON, YAML, or TOML file. The default format is JSON.
 
 - Add the job run using the job template file:

content/360/saas/get_started/override_settings.md

@@ -9,7 +9,7 @@ weight = 80
 +++
 
 When you created the Courier Runner skill definition in the previous section,
-it contained a base64-encoded TOML string in the value of `content` key. This TOML includes settings that can or should be overridden with settings for your Chef 360 Platform system.
+it contained a base64-encoded TOML string in the value of `content` key. This TOML includes settings that can or should be overridden with settings for your Chef 360 SaaS system.
 When Node Management runs on a node, it executes Courier Runner using values in the TOML file that are set by values stored in the Courier Runner's default settings or the Courier Runner's override settings.
 
 ## Prerequisites

content/360/saas/get_started/set_up.md

@@ -56,3 +56,7 @@ If your login failed because you forgot your password or you missed the five min
 1. At your organization's login page (**`https://CUSTOMER_SUBDOMAIN.cloud.chef.io/app/hub`**), select **Forgot Password** and enter the email address you used sign up with Chef 360 SaaS.
 
 1. You'll receive an email with a link to reset your password. You have five minutes follow the link and create a new password.
+
+## Next step
+
+- [Install Chef 360 CLIs]({{< relref "install_cli" >}})

content/360/saas/get_started/system_requirements.md

@@ -27,7 +27,7 @@ Open the following default ports for outbound connections.
 
 ### Cookbook-based enrollment
 
-Nodes enrolled with Chef 360 Platform using a Chef Infra cookbook have the following requirements:
+Nodes enrolled with Chef 360 SaaS using a Chef Infra cookbook have the following requirements:
 
 - Nodes must have Chef Infra Client installed.
 - Nodes have a public DNS or public IP address that can be reached from `https://CUSTOMER_SUBDOMAIN.cloud.chef.io`.
@@ -46,8 +46,8 @@ Connection requirements:
 - Nodes must have a public DNS or public IP address that can be reached from `https://CUSTOMER_SUBDOMAIN.cloud.chef.io`.
 - Nodes must allow for outbound and inbound communication with <https://bldr.habitat.sh>
 - A node IP address can’t be localhost (127.0.0.1)
-- A node CIDR address can’t be in the same range as the Chef 360 Platform services. The default CIDR range for Chef 360 Platform services is `10.244.0.0/16` or `10.96.0.0/12`.
-- The node’s ports for RabbitMQ (31050) and the nginx API gateway (31000) must be open to Chef 360 Platform. Additionally, the Chef 360 Platform should allow inbound connections to these ports from the node.
+- A node CIDR address can’t be in the same range as the Chef 360 SaaS services. The default CIDR range for Chef 360 SaaS services is `10.244.0.0/16` or `10.96.0.0/12`.
+- The node’s ports for RabbitMQ (31050) and the nginx API gateway (31000) must be open to Chef 360 SaaS. Additionally, the Chef 360 SaaS should allow inbound connections to these ports from the node.
 
 Nodes connected to with SSH have the following requirements:
 

content/360/saas/reusable_text/md/node_cohort_overview.md

@@ -1,3 +1,3 @@
 A node cohort defines skills and settings installed on every node in a cohort.
 
-After you create a cohort, you assign nodes to the cohort during node enrollment, and Chef 360 Platform installs or removes the skills and settings on every node accordingly.
+After you create a cohort, you assign nodes to the cohort during node enrollment and Chef 360 SaaS installs or removes the skills and settings on every node accordingly.