Update 360 content to match 1.2.1 docs

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

Author: IanMadd

content/360/saas/get_started/register_node_agent.md

@@ -17,9 +17,9 @@ You must define settings on the Node Management agent before defining skills and
 
 ## Register the Node Management agent
 
-To register a Node Management agent, follow these steps:
+To register the Node Management agent, follow these steps:
 
-1. Create a file named `register-agent-skill.json` that contains the settings for Node Management agent to function:
+1. Create a file named `register-agent-skill.json` that defines the Node Management agent settings:
 
     ```json
     {
@@ -34,17 +34,31 @@ To register a Node Management agent, follow these steps:
 
     Replace:
 
-    - `<HABITAT_BUILDER_URL>` with the Chef Habitat Builder URL. Use `https://bldr.habitat.sh` for Chef's Habitat Builder, or the URL of your own Habitat Builder deployment.
-    - `<CHANNEL>` with the release channel from which to install the skills. For example, `stable`.
+    - `<HABITAT_BUILDER_URL>` with the Chef Habitat Builder URL. Use `https://bldr.habitat.sh` for Chef's Habitat Builder or the URL of your own Habitat Builder deployment.
+    - `<CHANNEL>` with the release channel from which to install skills. For example, `stable`.
     - `<TOKEN>` with the authentication token for Habitat Builder. If you're using Chef's Habitat Builder, set this to an empty string.
-    - `<CHECK_IN_INTERVAL>` with the interval (in seconds) at which check-in occurs. Value starting from `3600` (1 hr).
-    - `<UPDATE_SKILL_INTERVAL>` with the interval (in seconds) at which skill definitions will be updated. Value starting from `3600` (1 hr).
+    - `<CHECK_IN_INTERVAL>` with the interval (in seconds) at which check-in occurs. Value starting from `3600` (1 hour).
+    - `<UPDATE_SKILL_INTERVAL>` with the interval (in seconds) at which skill definitions are updated. Value starting from `3600` (1 hour).
     - `<LOG_LEVEL>`: The logging level of the agent. For example, `debug`.
 
+      Supported log levels:
+
+      `debug`
+      : Reports detailed information that can aid in identifying issues or debugging a workload. This includes the info, warn, and error logs.
+
+      `info`
+      : Reports general information about the system's operations.
+
+      `warn`
+      : Reports potential failures, but the operation can continue functioning for the time being.
+
+      `error`
+      : Reports errors that prevent the execution of an operation.
+
 1. Create the skill assembly:
 
     ```sh
-    chef-node-management-cli management skill update-agent --body-file register-agent-skill.json --profile <NODE_MANAGER_PROFILE_NAME>
+    chef-node-management-cli management skill update-agent --body-file register-agent-skill.json
     ```
 
     It returns the following response:

content/360/saas/get_started/system_requirements.md

@@ -13,7 +13,17 @@ weight = 20
 This guide describes two methods of enrolling nodes, either with a Chef Infra cookbook or with single-node enrollment from Chef 360 SaaS.
 See the node requirements for those methods in the following sections.
 
-For more information on these enrollment methods, see the node enrollment guide or the node enrollment documentation.
+### Ports
+
+Open the following default ports for outbound connections.
+
+| Port  | Description                  |
+|-------|------------------------------|
+| 443   | HTTPS                        |
+| 31050 | RabbitMQ AMQP/AMQP-TLS       |
+| 31000 | Nginx Reverse Proxy NodePort |
+| 22    | SSH (optional)               |
+| 80    | HTTP (optional)              |
 
 ### Cookbook-based enrollment