Lint fix

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

Author: IanMadd

content/360/saas/_index.md

@@ -15,18 +15,18 @@ 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**: Chef 360 SaaS 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**: 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**: 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.
+**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.
 
 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.
 - Safely build, package, and deploy applications from a fully cloud-native, zero-trust platform in conjunction with Chef Habitat.
-- Discover assets effortlessly from existing Chef environments, other Progress products like What’s-Up-Gold, and even your own CMDB and monitoring solutions.
+- Discover assets effortlessly from existing Chef environments, other Progress products like What's-Up-Gold, and even your own CMDB and monitoring solutions.
 - Leverage an open partner ecosystem with Chef premium content and content from thought leaders such as OSL and MITRE, and easily extensible formats which require no special knowledge.
 
 ## Additional guides

content/360/saas/get_started/override_settings.md

@@ -38,7 +38,7 @@ Create node override settings for the Courier Runner and Gohai skills.
     {
         "item": {
             "settingId": "<SETTING_ID>"
-        ｝
+        }
     }
     ```
 

content/360/saas/get_started/system_requirements.md

@@ -32,11 +32,11 @@ Nodes enrolled with Chef 360 SaaS using a Chef Infra cookbook have the following
 - 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`.
 - Nodes must allow for outbound and inbound communication with <https://bldr.habitat.sh>
-- Nodes can’t have localhost (127.0.0.1) as an IP address.
+- Nodes can't have localhost (127.0.0.1) as an IP address.
 - You must have sudo privileges on the node.
 - Note: Requires Chef Infra Server or running Chef Infra Client in zero mode. For SaaS, this requires Chef 360 SaaS Enterprise.
 
-### Chef 360 platform-based enrollment
+### Chef 360 SaaS enrollment
 
 Nodes enrolled using single-node enrollment have the following requirements.
 
@@ -45,9 +45,9 @@ Connection requirements:
 - Nodes must be accessible with SSH or WinRM from `https://CUSTOMER_SUBDOMAIN.cloud.chef.io`.
 - 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 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.
+- 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 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.
 
 Nodes connected to with SSH have the following requirements:
 
@@ -57,7 +57,7 @@ Nodes connected to with SSH have the following requirements:
 
 Nodes connected to with WinRM have the following requirements:
 
-- Ports 5985–5986 must be open.
+- Ports 5985 and 5986 must be open.
 - Configure WinRM by running the following:
 
     ```ps1

content/360/saas/reusable_text/md/skill_assembly_get_started.md

@@ -2,7 +2,6 @@
 
    {{% readfile file="_vendor/github.com/chef/samples/cohorts/skill-assembly.json" highlight="json" %}}
 
-
 1. Create the skill assembly:
 
     ```sh