diff --git a/docs/content/cluster-api/control-plane-provider.md b/docs/content/cluster-api/control-plane-provider.md
index 1f4129b..a093aaf 100644
--- a/docs/content/cluster-api/control-plane-provider.md
+++ b/docs/content/cluster-api/control-plane-provider.md
@@ -60,7 +60,7 @@ spec:
 ```
 
 !!! info "Full Reference"
-    For a full reference of the `KamajiControlPlane` custom resource, please see the [Reference APIs](reference/api.md).
+    For a full reference of the `KamajiControlPlane` custom resource, please see the [Reference APIs](https://doc.crds.dev/github.com/clastix/cluster-api-control-plane-provider-kamaji/controlplane.cluster.x-k8s.io/KamajiControlPlane/v1alpha1).
 
 ## Getting started with the Kamaji Control Plane Provider
 
diff --git a/docs/content/cluster-api/vsphere-infra-provider.md b/docs/content/cluster-api/vsphere-infra-provider.md
index 83571f0..cb1a112 100644
--- a/docs/content/cluster-api/vsphere-infra-provider.md
+++ b/docs/content/cluster-api/vsphere-infra-provider.md
@@ -223,7 +223,7 @@ The template file `capi-kamaji-vsphere-template-csi.yaml` includes the [vSphere
 
 This template file introduces a *"split configuration"* for the vSphere CSI Driver, with the CSI driver deployed on the worker nodes as daemonset and the CSI Controller Manager deployed on the Management Cluster as part of the Hosted Control Plane. In this way, no vSphere credentials are required on the tenant cluster.
 
-This spit architecture enables:
+This split architecture enables:
 
 * Tenant isolation from vSphere credentials
 * Simplified networking requirements
diff --git a/docs/mkdocs.yml b/docs/mkdocs.yml
index 386a5e1..c5c57fc 100644
--- a/docs/mkdocs.yml
+++ b/docs/mkdocs.yml
@@ -63,9 +63,9 @@ nav:
 - 'Cluster API':
   - cluster-api/index.md
   - cluster-api/control-plane-provider.md
-  - cluster-api/vsphere-infra-provider.md
   - cluster-api/cluster-class.md
   - cluster-api/cluster-autoscaler.md
+  - cluster-api/vsphere-infra-provider.md
   - cluster-api/other-providers.md
 - 'Guides':
   - guides/index.md