Update 360 SaaS content

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

Author: IanMadd

content/360/saas/get_started/_index.md

@@ -9,29 +9,29 @@ parent = "chef_cloud/360/get_started"
 weight = 10
 +++
 
-This section provides quickstart guides for getting started with Chef 360 SaaS and its tools.
+This section is a quickstart guide to using Chef 360 SaaS and its tools.
 
-## Get started guides
+## How Chef 360 SaaS works
 
-Before you begin with these guides, [review the system requirements]({{< relref "system_requirements" >}}).
+Chef 360 SaaS consists of three main components:
 
-Chef 360 SaaS guides:
+- **Chef 360 SaaS CLIs**: Users use the CLIs to define and invoke Chef Courier jobs, and configure user accounts, tenants, organizations, and nodes.
+- **Chef 360 SaaS**: Manages users, organizations, and tenants, schedules and distributes Courier jobs, and monitors nodes and job results.
+- **Chef skills**: Chef 360 SaaS installs skills on each node that manage the node, execute jobs, and report to Chef 360 SaaS.
 
-- [Set up Chef 360 SaaS]({{< relref "set_up" >}})
+## What this guide covers
 
-Chef 360 Platform CLI guides:
+This guide walks you through the following steps:
 
-- [Install and register the Chef 360 Platform CLIs]({{< relref "install_cli" >}})
+1. Installing Chef 360 SaaS in a single-node Kubernetes cluster.
+1. Installing Chef 360 SaaS CLIs on a local workstation and registering it with Chef 360 SaaS.
+1. Enrolling a node with Chef 360 SaaS. Nodes can be enrolled using a Chef 360 SaaS CLI or by uploading a Chef Infra cookbook if Chef Infra Client is already installed on the node.
+1. Defining and running a basic job on a node, and reviewing the job's execution details and the results of each step.
 
-Chef Node Management guides:
+## Before you begin
 
-- [Register the Node Management agent]({{< relref "register_node_agent" >}})
-- [Define skills]({{< relref "define_skills" >}})
-- [Create a skill assembly]({{< relref "create_skill_assembly" >}})
-- [Create override settings]({{< relref "override_settings" >}})
-- [Create a node cohort]({{< relref "node_cohort" >}})
-- [Enroll nodes]({{< relref "enroll_nodes" >}})
+- Review the [Chef 360 SaaS system requirements]({{< relref "/360/saas/system_requirements.md" >}}).
 
-Chef Courier job guides:
+## Next steps
 
-- [Run jobs with Chef Courier]({{< relref "jobs" >}})
+- [Set up Chef 360 SaaS]({{< relref "/360/saas/get_started/set_up.md" >}}).

content/360/saas/get_started/create_skill_assembly.md

@@ -8,31 +8,47 @@ parent = "chef_cloud/360/get_started"
 weight = 100
 +++
 
-Node enrollment brings nodes under management by Chef 360 SaaS.
+When you enroll a node into a node cohort, Chef 360 Platform installs the Chef skills and skill settings that are defined for all nodes in that cohort.
+These skills allow Chef 360 Platform to manage the node, execute Chef Courier jobs, and report back to Chef 360 Platform.
+
+Chef 360 Platform installs the following skills in the default skill assembly:
+
+- **Chef Infra Client interpreter skill**: Executes Chef Infra Client runs.
+- **Courier Runner skill**: Interprets and executes Chef Courier jobs.
+- **Gohai skill**: Reports node attribute data to Chef 360 Platform.
+- **Inspec interpreter skill**: Executes Chef InSpec audits.
+- **Node Management agent**: Manages and installs other skills on the node.
+- **Restart interpreter skill**: Restarts nodes.
+- **Shell interpreter skill**: Executes shell scripts.
+
+For more information, see the [Chef 360 skills](https://docs.chef.io/360/1.3/node_management/skills/) documentation.
+
+## Node enrollment methods
 
 This document demonstrates two different methods of node enrollment:
 
 - cookbook-based enrollment
 - single-node enrollment
 
+For more information, see the [node enrollment documentation](https://docs.chef.io/360/1.3/node_management/enroll_nodes/).
+
 {{< note >}}
 
-This version of Chef 360 SaaS doesn't support node re-enrollment.
+Chef 360 Platform doesn't support node re-enrollment.
 
 {{< /note >}}
 
-## Prerequisites
+## Role requirements
 
-- [A node cohort has been created]({{< relref "node_cohort" >}}).
+To enroll nodes, use a profile with the [node-manager role](https://docs.chef.io/360/1.3/administration/system_roles/).
 
-## Requirements
+## Before you begin
 
-Review the [node requirements]({{< relref "system_requirements#node-requirements" >}}) before enrolling nodes.
+- Review the [node requirements]({{< relref "/360/saas/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 SaaS, which connects to each node and installs Chef Habitat, Chef Node Management, and any skills or agents assigned to a node cohort.
+Single-node enrollment allows you to enroll nodes directly from the server side. With this method, you specify the connection and configuration details for each node and upload them to Chef 360 Platform. Chef 360 Platform then connects to each node, installs Chef Habitat, Chef Node Management, and any skills or agents associated with the node's cohort.
 
 ### Enroll Linux nodes
 

content/360/saas/get_started/define_skills.md

@@ -10,11 +10,11 @@ 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 SaaS deployment.
+This page documents how to download and install the Chef 360 SaaS CLIs and register your workstation with your Chef 360 SaaS deployment.
 
 ## Prerequisites
 
-- [Chef 360 SaaS configured]({{< relref "set_up" >}}).
+- [Chef 360 SaaS is configured]({{< relref "set_up" >}}).
 - `/usr/local/bin` is present in the PATH environment variable.
 
 ## Install CLIs
@@ -142,7 +142,7 @@ To create a profile, follow these steps:
 
 1. Optional: Set your new profile as the default profile.
 
-    The Chef 360 Platform CLIs use a default profile automatically in any command that accepts the `--profile` argument.
+    The Chef 360 SaaS CLIs use a default profile automatically in any command that accepts the `--profile` argument.
     If you don't set a default profile, you will have to specify it in each command with `--profile <PROFILE_NAME>`.
 
     Set a default profile:
@@ -155,10 +155,11 @@ 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
+## More information
 
-- [Chef 360 CLI reference documentation](https://docs.chef.io/360/1.3/reference/cli/)
+- [Chef 360 Platform CLI reference documentation](https://docs.chef.io/360/1.3/reference/cli).
+- [Chef 360 Platform roles documentation](https://docs.chef.io/360/1.3/administration/system_roles/)
 
 ## Next step
 
-- [Register the Node Management agent]({{< relref "register_node_agent.md" >}}).
+- [Review the node management settings]({{< relref "node_management_settings" >}})

content/360/saas/get_started/enroll_nodes.md

@@ -8,34 +8,46 @@ parent = "chef_cloud/360/get_started"
 weight = 110
 +++
 
-A Courier job defines the actions performed on a node or set of nodes, the schedule that the actions are performed on, and the group of nodes that the actions are performed on.
-A job can be executed multiple times across multiple nodes for multiple actions.
+A Courier job specifies the actions to perform, the schedule for execution, and the target nodes where the actions will run. Jobs can execute multiple actions, across multiple nodes, and can run multiple times as defined by the schedule.
 
-## Prerequisites
+## How jobs are executed on a node
 
-- [Nodes are enrolled]({{< relref "enroll_nodes" >}}).
+Chef 360 SaaS uses skills to execute Courier jobs.
+For example, the Courier Runner is a skill that interprets jobs and executes them, the Shell interpreter is a skill that executes shell scripts included in a job, and the Node Management agent is a skill that manages nodes and other skills.
+
+In this example, the Courier Runner skill interprets the job definition and passes a shell command to the Shell interpreter.
+
+## Before you begin
+
+- You'll need at least one [enrolled node]({{< relref "enroll_nodes.md" >}}).
 
 ## Define a job
 
-Jobs are defined using a job template, which is a file in JSON, YAML, or TOML format that tells Chef Courier the name of the job, when the job should run, the nodes that the job should run on, and the actions that the job should take.
+You define a job with a job template, which is a JSON, YAML, or TOML file that tells Chef Courier the name of the job, when the job should run, the nodes that the job should run on, and the actions that the job should take.
 
-This job template creates a job that's executed one node, it runs immediately, and it uses the `chef-platform/shell-interpreter` to run the `sleep 10` command.
+This job template creates a job that's executed on one node, it runs immediately, and runs the `sleep 10` command using the Shell interpreter skill.
 
-- Create a file called `create-job-simple.json` and with the following JSON string:
+1. Get the ID of an enrolled node:
+
+    ```sh
+    chef-node-management-cli management node find-all-nodes
+    ```
 
-  {{% readfile file="_vendor/github.com/chef/samples/courier-job-examples/create-job-simple.json" highlight="json" %}}
+1. Create a JSON file with the following job definition:
 
-  Replace `<NODE_ID>` in the JSON file with the node identifier of your enrolled node.
+   {{% readfile file="_vendor/github.com/chef/samples/courier-job-examples/create-job-simple.json" highlight="json" %}}
 
-## Create the job
+    Replace the node ID in the JSON file with the node identifier of an enrolled node.
 
-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.
+## Submit the job
+
+When you send 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:
 
   ```sh
-  chef-courier-cli scheduler jobs add-job --body-file create-job-simple.json --profile <COURIER_OPERATOR_PROFILE_NAME>
+  chef-courier-cli scheduler jobs add-job --body-file <PATH_TO_JSON_FILE> --profile <COURIER_OPERATOR_PROFILE_NAME>
   ```
 
   The default file format is JSON, you can also submit the job using YAML or TOML using the `--body-format` option. For example:
@@ -71,7 +83,6 @@ A job instance is created every time the job executes. This job is set to run im
     The response is similar to the following:
 
     ```json
-
     {
       "items": [
         {
@@ -272,7 +283,7 @@ A job run is created for each target node in a job instance.
   }
   ```
 
-## Debug Courier jobs
+## Debug Chef Courier jobs
 
 You can also review the job step details by connecting to a node with SSH and checking the Courier Runner logs.
 
@@ -289,3 +300,10 @@ For a Windows node:
 cd C:\hab\svc\courier-runner\logs
 gc .\courier-log -Wait
 ```
+
+## More information
+
+To define and run jobs, see the following documentation:
+
+- [Create a Courier job](https://docs.chef.io/360/1.3/courier/jobs/).
+- [Create a Courier job template](https://docs.chef.io/360/1.3/courier/jobs/template/).