diff --git a/vertical-pod-autoscaler/docs/quickstart.md b/vertical-pod-autoscaler/docs/quickstart.md
index 7ef784d30009da00bff0ed014183078a4dcb9425..59f6352a0fe2706ab2be18f6e7ab5631451a6058 100644
--- a/vertical-pod-autoscaler/docs/quickstart.md
+++ b/vertical-pod-autoscaler/docs/quickstart.md
@@ -25,6 +25,9 @@ There are four modes in which *VPAs* operate:
   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.
+- `"InPlaceOrRecreate"`: 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_.
 - `"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.