diff --git a/docs/source/reference/config.rst b/docs/source/reference/config.rst
index d926ef92695..4db8c612fd7 100644
--- a/docs/source/reference/config.rst
+++ b/docs/source/reference/config.rst
@@ -901,13 +901,13 @@ Default: ``10``.
 
 Autoscaler type (optional).
 
-Type of autoscaler to use.
+Type of autoscaler used by the underlying Kubernetes cluster. Used to configure the GPU labels used by the pods submitted by SkyPilot.
 
 Can be one of:
 
-- ``gke``: Google Kubernetes Engine Autopilot
-- ``eks``: Amazon EKS
-- ``aks``: Azure Kubernetes Service
+- ``gke``: Google Kubernetes Engine
+- ``karpenter``: Karpenter
+- ``generic``: Generic autoscaler, assumes nodes are labelled with ``skypilot.co/accelerator``.
 
 .. _config-yaml-kubernetes-pod-config:
 
diff --git a/docs/source/reference/kubernetes/kubernetes-getting-started.rst b/docs/source/reference/kubernetes/kubernetes-getting-started.rst
index 0b453041cf5..7d67ee9a50e 100644
--- a/docs/source/reference/kubernetes/kubernetes-getting-started.rst
+++ b/docs/source/reference/kubernetes/kubernetes-getting-started.rst
@@ -348,9 +348,9 @@ FAQs
 
 * **Can I use multiple Kubernetes clusters with SkyPilot?**
 
-  SkyPilot can work with multiple Kubernetes contexts set in your kubeconfig file. By default, SkyPilot will use the current active context. To use a different context, change your current context using :code:`kubectl config use-context <context-name>`.
+  SkyPilot can work with multiple Kubernetes contexts in your kubeconfig file by setting the ``allowed_contexts`` key in :code:`~/.sky/config.yaml`. See :ref:`multi-kubernetes`.
 
-  If you would like to use multiple contexts seamlessly during failover, check out the :code:`allowed_contexts` feature in :ref:`config-yaml`.
+  If ``allowed_contexts`` is not set, SkyPilot will use the current active context. To use a different context, change your current context using :code:`kubectl config use-context <context-name>`.
 
 * **Are autoscaling Kubernetes clusters supported?**