Merge pull request #2629 from replicatedhq/AmberAlston-patch-1

Some CMX content improvements

Author: paigecalvert

docs/reference/replicated-cli-cluster-create.md

@@ -71,7 +71,7 @@ replicated cluster create [flags]
   <tr>
     <td>--nodegroup</td>
     <td>string</td>
-    <td>Node group to create (name=?,instance-type=?,nodes=?,min-nodes=?,max-nodes=?,disk=? format, can be specified multiple times). For each nodegroup, one of the following flags must be specified: name, instance-type, nodes, min-nodes, max-nodes or disk.</td>
+    <td>Node group to create (name=?,instance-type=?,nodes=?,min-nodes=?,max-nodes=?,disk=? format, can be specified multiple times). For each nodegroup, at least one of the following flags must be specified: name, instance-type, nodes, min-nodes, max-nodes or disk.</td>
   </tr>
   <Output/>
   <tr>

docs/vendor/testing-ingress.md

@@ -46,7 +46,7 @@ The following diagram shows how the traffic is routed into the service using Com
 Compatibity matrix tunnels are a beta feature.
 :::
 
-Tunnels are viewed, created, and removed using the Replicated CLI, GitHub Actions, or directly with the Vendor API v3. There is no limit to the number of tunnels you can create for a cluster and multiple tunnels can connect to a single service, if desired.
+Tunnels are viewed, created, and removed using the Compatibility Matrix UI within Vendor Portal, the Replicated CLI, GitHub Actions, or directly with the Vendor API v3. There is no limit to the number of tunnels you can create for a cluster and multiple tunnels can connect to a single service, if desired.
 
 ### Limitations