Fix spelling typo

replicatedhq · May 1, 2024 · c604b38 · c604b38
1 parent 2f8a9ac
commit c604b38
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/docs/partials/cmx/_billing.mdx b/docs/partials/cmx/_billing.mdx
@@ -1,6 +1,6 @@
-Clusters created with the compatiblity matrix are billed by the minute. Per-minute billing begins when the cluster reaches a `running` status and ends when the cluster is deleted. The compatibility matrix marks a cluster as `running` when a working kubeconfig for the cluster is accessible.
+Clusters created with the compatibility matrix are billed by the minute. Per-minute billing begins when the cluster reaches a `running` status and ends when the cluster is deleted. The compatibility matrix marks a cluster as `running` when a working kubeconfig for the cluster is accessible.
 
 You are billed only for the time that the cluster is in a `running` status. You are _not_ billed for the time that it takes the compatibility matrix to create and tear down clusters, including when the cluster is in an `assigned` status.
 
 To create clusters with the compatibility matrix, you must have credits in your vendor portal account. 
-To request credits, log in to the vendor portal and go to [**Compatibility Matrix > Request more credits**](https://vendor.replicated.com/compatibility-matrix).
+To request credits, log in to the vendor portal and go to [**Compatibility Matrix > Request more credits**](https://vendor.replicated.com/compatibility-matrix).
diff --git a/docs/partials/cmx/_overview.mdx b/docs/partials/cmx/_overview.mdx
@@ -2,7 +2,7 @@ The Replicated compatibility matrix quickly provisions ephemeral clusters of dif
 
 You can use the compatibility matrix to get kubectl access to running clusters within minutes or less. This allows you to more easily test your code in a range of different environments before releasing to customers.
 
-Example use cases for the compatiblity matrix include:
+Example use cases for the compatibility matrix include:
 * Run tests before releasing a new version of your application to validate compatibility with supported Kubernetes distributions
 * Get access to a cluster to develop on and quickly test changes
-* Reproduce a reported issue on a customer-representative environment for troubleshooting
+* Reproduce a reported issue on a customer-representative environment for troubleshooting