diff --git a/vertical-pod-autoscaler/docs/quickstart.md b/vertical-pod-autoscaler/docs/quickstart.md
index 4b7dfcca4f472797d4a4305425c387a576f8daaa..b0f6eddae5088ca92de89e5909d0e3227c810e53 100644
--- a/vertical-pod-autoscaler/docs/quickstart.md
+++ b/vertical-pod-autoscaler/docs/quickstart.md
@@ -22,9 +22,10 @@ There are five modes in which *VPAs* operate:
   from the new recommendation (respecting the Pod Disruption Budget, if defined).
   This mode should be used rarely, only if you need to ensure that the pods are restarted
   whenever the resource request changes.
-- `"InPlaceOrRecreate"`: VPA assigns resource requests on pod creation as well as updates
+- `"InPlaceOrRecreate"`[__alpha feature__]: VPA assigns resource requests on pod creation as well as updates
   them on existing pods by leveraging [Kubernetes `in-place` update](https://kubernetes.io/blog/2025/05/16/kubernetes-v1-33-in-place-pod-resize-beta/) capability.
   If `in-place` update fails, it falls back to evicting the pods, performing a _recreation_.
+  For more details, see the [In-Place Updates documentation](https://github.com/kubernetes/autoscaler/blob/master/vertical-pod-autoscaler/docs/features.md#in-place-updates-inplaceorrecreate).
 - `"Initial"`: VPA only assigns resource requests on pod creation and never changes them
   later.
 - `"Off"`: VPA does not automatically change the resource requirements of the pods.