diff --git a/vertical-pod-autoscaler/docs/quickstart.md b/vertical-pod-autoscaler/docs/quickstart.md
index 7ef784d30009da00bff0ed014183078a4dcb9425..b0f6eddae5088ca92de89e5909d0e3227c810e53 100644
--- a/vertical-pod-autoscaler/docs/quickstart.md
+++ b/vertical-pod-autoscaler/docs/quickstart.md
@@ -12,19 +12,20 @@ resource requests for your pods.
 In order to use it, you need to insert a *Vertical Pod Autoscaler* resource for
 each controller that you want to have automatically computed resource requirements.
 This will be most commonly a **Deployment**.
-There are four modes in which *VPAs* operate:
+There are five modes in which *VPAs* operate:
 
 - `"Auto"`: VPA assigns resource requests on pod creation as well as updates
   them on existing pods using the preferred update mechanism. Currently, this is
-  equivalent to `"Recreate"` (see below). Once restart free ("in-place") update
-  of pod requests is available, it may be used as the preferred update mechanism by
-  the `"Auto"` mode.
+  equivalent to `"Recreate"` (see below).
 - `"Recreate"`: VPA assigns resource requests on pod creation as well as updates
   them on existing pods by evicting them when the requested resources differ significantly
   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. Otherwise, prefer the `"Auto"` mode which may take
-  advantage of restart-free updates once they are available.
+  whenever the resource request changes.
+- `"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.