diff --git a/src/api/composition-api-setup.md b/src/api/composition-api-setup.md
index 9a73a49c6f..b108aa1503 100644
--- a/src/api/composition-api-setup.md
+++ b/src/api/composition-api-setup.md
@@ -7,7 +7,7 @@ The `setup()` hook serves as the entry point for Composition API usage in compon
 1. Using Composition API without a build step;
 2. Integrating with Composition-API-based code in an Options API component.
 
-:::info Note
+:::info
 If you are using Composition API with Single-File Components, [`<script setup>`](/api/sfc-script-setup) is strongly recommended for a more succinct and ergonomic syntax.
 :::
 
diff --git a/src/api/options-state.md b/src/api/options-state.md
index 4aa176a250..deae94d7a0 100644
--- a/src/api/options-state.md
+++ b/src/api/options-state.md
@@ -144,7 +144,8 @@ Declare computed properties to be exposed on the component instance.
 
   type ComputedGetter<T> = (
     this: ComponentPublicInstance,
-    vm: ComponentPublicInstance
+    vm: ComponentPublicInstance,
+    previous: T
   ) => T
 
   type ComputedSetter<T> = (
diff --git a/src/api/sfc-script-setup.md b/src/api/sfc-script-setup.md
index c2a04391a9..6e32e18651 100644
--- a/src/api/sfc-script-setup.md
+++ b/src/api/sfc-script-setup.md
@@ -479,7 +479,7 @@ const post = await fetch(`/api/post/1`).then((r) => r.json())
 
 In addition, the awaited expression will be automatically compiled in a format that preserves the current component instance context after the `await`.
 
-:::warning Note
+:::warning
 `async setup()` must be used in combination with [`Suspense`](/guide/built-ins/suspense.html), which is currently still an experimental feature. We plan to finalize and document it in a future release - but if you are curious now, you can refer to its [tests](https://github.com/vuejs/core/blob/main/packages/runtime-core/__tests__/components/Suspense.spec.ts) to see how it works.
 :::
 
diff --git a/src/guide/components/provide-inject.md b/src/guide/components/provide-inject.md
index d95edf797a..ceccfb6507 100644
--- a/src/guide/components/provide-inject.md
+++ b/src/guide/components/provide-inject.md
@@ -6,7 +6,7 @@
 
 Usually, when we need to pass data from the parent to a child component, we use [props](/guide/components/props). However, imagine the case where we have a large component tree, and a deeply nested component needs something from a distant ancestor component. With only props, we would have to pass the same prop across the entire parent chain:
 
-![prop drilling diagram](./images/prop-drilling.png)
+![Diagram showing props being passed through multiple levels of components just to reach a deeply nested child](./images/prop-drilling.png)
 
 <!-- https://www.figma.com/file/yNDTtReM2xVgjcGVRzChss/prop-drilling -->
 
@@ -14,7 +14,7 @@ Notice although the `<Footer>` component may not care about these props at all,
 
 We can solve props drilling with `provide` and `inject`. A parent component can serve as a **dependency provider** for all its descendants. Any component in the descendant tree, regardless of how deep it is, can **inject** dependencies provided by components up in its parent chain.
 
-![Provide/inject scheme](./images/provide-inject.png)
+![Diagram showing the provide/inject mechanism where a parent component provides a dependency that can be directly injected by a deeply nested child, bypassing intermediate components](./images/provide-inject.png)
 
 <!-- https://www.figma.com/file/PbTJ9oXis5KUawEOWdy2cE/provide-inject -->
 
diff --git a/src/guide/components/slots.md b/src/guide/components/slots.md
index b50855cdf6..728ea451ce 100644
--- a/src/guide/components/slots.md
+++ b/src/guide/components/slots.md
@@ -26,7 +26,7 @@ The template of `<FancyButton>` looks like this:
 
 The `<slot>` element is a **slot outlet** that indicates where the parent-provided **slot content** should be rendered.
 
-![slot diagram](./images/slots.png)
+![Diagram showing slot content from the parent being injected into the slot outlet in the child component](./images/slots.png)
 
 <!-- https://www.figma.com/file/LjKTYVL97Ck6TEmBbstavX/slot -->
 
@@ -207,7 +207,7 @@ To pass a named slot, we need to use a `<template>` element with the `v-slot` di
 
 `v-slot` has a dedicated shorthand `#`, so `<template v-slot:header>` can be shortened to just `<template #header>`. Think of it as "render this template fragment in the child component's 'header' slot".
 
-![named slots diagram](./images/named-slots.png)
+![Diagram showing multiple named slots in a layout component, with content from the parent being directed to the corresponding header, main, and footer slots](./images/named-slots.png)
 
 <!-- https://www.figma.com/file/2BhP8gVZevttBu9oUmUUyz/named-slot -->
 
@@ -367,7 +367,7 @@ Receiving the slot props is a bit different when using a single default slot vs.
 </MyComponent>
 ```
 
-![scoped slots diagram](./images/scoped-slots.svg)
+![Diagram showing a scoped slot where the child component passes data back to the parent-provided slot content](./images/scoped-slots.svg)
 
 <!-- https://www.figma.com/file/QRneoj8eIdL1kw3WQaaEyc/scoped-slot -->
 
diff --git a/src/guide/components/v-model.md b/src/guide/components/v-model.md
index e1248c18f5..fb819fa24f 100644
--- a/src/guide/components/v-model.md
+++ b/src/guide/components/v-model.md
@@ -84,7 +84,7 @@ Then, `v-model="foo"` in the parent component will be compiled to:
 />
 ```
 
-As you can see, it is quite a bit more verbose. However, it is helpful to understand what is happening under the hood.
+As you can see, it is quite a bit more verbose. However, it is helpful to understand what is happening internally.
 
 Because `defineModel` declares a prop, you can therefore declare the underlying prop's options by passing it to `defineModel`:
 
diff --git a/src/guide/essentials/component-basics.md b/src/guide/essentials/component-basics.md
index cec4114e5b..aef605cc3e 100644
--- a/src/guide/essentials/component-basics.md
+++ b/src/guide/essentials/component-basics.md
@@ -6,7 +6,7 @@
 
 Components allow us to split the UI into independent and reusable pieces, and think about each piece in isolation. It's common for an app to be organized into a tree of nested components:
 
-![Component Tree](./images/components.png)
+![Diagram showing a component tree structure with a root component branching into multiple child and nested sub-child components](./images/components.png)
 
 <!-- https://www.figma.com/file/qa7WHDQRWuEZNRs7iZRZSI/components -->
 
diff --git a/src/guide/essentials/forms.md b/src/guide/essentials/forms.md
index 1ee276d7ae..96e8106696 100644
--- a/src/guide/essentials/forms.md
+++ b/src/guide/essentials/forms.md
@@ -49,7 +49,7 @@ In addition, `v-model` can be used on inputs of different types, `<textarea>`, a
 - `<input type="checkbox">` and `<input type="radio">` use `checked` property and `change` event;
 - `<select>` uses `value` as a prop and `change` as an event.
 
-::: tip Note
+:::tip
 `v-model` will ignore the initial `value`, `checked` or `selected` attributes found on any form elements. It will always treat the current bound JavaScript state as the source of truth. You should declare the initial value on the JavaScript side, using <span class="options-api">the [`data`](/api/options-state.html#data) option</span><span class="composition-api">[reactivity APIs](/api/reactivity-core.html#reactivity-api-core)</span>.
 :::
 
@@ -274,7 +274,7 @@ Single select:
 
 </div>
 
-:::tip Note
+:::tip
 If the initial value of your `v-model` expression does not match any of the options, the `<select>` element will render in an "unselected" state. On iOS this will cause the user not being able to select the first item because iOS does not fire a change event in this case. It is therefore recommended to provide a disabled option with an empty value, as demonstrated in the example above.
 :::
 
diff --git a/src/guide/essentials/lifecycle.md b/src/guide/essentials/lifecycle.md
index 99762475d9..a995e2dc5d 100644
--- a/src/guide/essentials/lifecycle.md
+++ b/src/guide/essentials/lifecycle.md
@@ -59,7 +59,7 @@ Do note this doesn't mean that the call must be placed lexically inside `setup()
 
 Below is a diagram for the instance lifecycle. You don't need to fully understand everything going on right now, but as you learn and build more, it will be a useful reference.
 
-![Component lifecycle diagram](./images/lifecycle.png)
+![Diagram showing the full lifecycle of a Vue component, from creation to destruction, including all major lifecycle hooks and the internal processes like template compilation and mounting](./images/lifecycle.png)
 
 <!-- https://www.figma.com/file/Xw3UeNMOralY6NV7gSjWdS/Vue-Lifecycle -->
 
diff --git a/src/guide/essentials/list.md b/src/guide/essentials/list.md
index 9451e41bac..2d53a3a911 100644
--- a/src/guide/essentials/list.md
+++ b/src/guide/essentials/list.md
@@ -245,7 +245,7 @@ This can be fixed by moving `v-for` to a wrapping `<template>` tag (which is als
 </template>
 ```
 
-:::warning Note
+:::warning
 It's **not** recommended to use `v-if` and `v-for` on the same element due to implicit precedence.
 
 There are two common cases where this can be tempting:
@@ -277,7 +277,7 @@ When using `<template v-for>`, the `key` should be placed on the `<template>` co
 </template>
 ```
 
-:::tip Note
+:::tip
 `key` here is a special attribute being bound with `v-bind`. It should not be confused with the property key variable when [using `v-for` with an object](#v-for-with-an-object).
 :::
 
diff --git a/src/guide/essentials/template-syntax.md b/src/guide/essentials/template-syntax.md
index 8a42bff4dd..4428cc4d50 100644
--- a/src/guide/essentials/template-syntax.md
+++ b/src/guide/essentials/template-syntax.md
@@ -118,7 +118,8 @@ data() {
   return {
     objectOfAttrs: {
       id: 'container',
-      class: 'wrapper'
+      class: 'wrapper',
+      style: 'background-color:green'
     }
   }
 }
@@ -286,6 +287,6 @@ You'll see other examples of modifiers later, [for `v-on`](./event-handling#even
 
 And finally, here's the full directive syntax visualized:
 
-![directive syntax graph](./images/directive.png)
+![Diagram visualizing the full directive syntax, including directive name, argument, modifiers, and value](./images/directive.png)
 
 <!-- https://www.figma.com/file/BGWUknIrtY9HOmbmad0vFr/Directive -->
diff --git a/src/guide/extras/reactivity-in-depth.md b/src/guide/extras/reactivity-in-depth.md
index 6e417f5a8f..24af146562 100644
--- a/src/guide/extras/reactivity-in-depth.md
+++ b/src/guide/extras/reactivity-in-depth.md
@@ -8,7 +8,7 @@ import SpreadSheet from './demos/SpreadSheet.vue'
 
 # Reactivity in Depth {#reactivity-in-depth}
 
-One of Vue’s most distinctive features is the unobtrusive reactivity system. Component state consists of reactive JavaScript objects. When you modify them, the view updates. It makes state management simple and intuitive, but it’s also important to understand how it works to avoid some common gotchas. In this section, we are going to dig into some of the lower-level details of Vue’s reactivity system.
+One of Vue’s most distinctive features is the unobtrusive reactivity system. Component state consists of reactive JavaScript objects. When you modify them, the view updates. It makes state management simple and intuitive, but it’s also important to understand how it works to avoid some common pitfalls. In this section, we are going to dig into some of the lower-level details of Vue’s reactivity system.
 
 ## What is Reactivity? {#what-is-reactivity}
 
@@ -202,7 +202,7 @@ In fact, this is pretty close to how a Vue component keeps the state and the DOM
 
 <div class="options-api">
 
-The `ref()`, `computed()` and `watchEffect()` APIs are all part of the Composition API. If you have only been using Options API with Vue so far, you'll notice that Composition API is closer to how Vue's reactivity system works under the hood. In fact, in Vue 3 the Options API is implemented on top of the Composition API. All property access on the component instance (`this`) triggers getter / setters for reactivity tracking, and options like `watch` and `computed` invoke their Composition API equivalents internally.
+The `ref()`, `computed()` and `watchEffect()` APIs are all part of the Composition API. If you have only been using Options API with Vue so far, you'll notice that Composition API is closer to how Vue's reactivity system works internally. In fact, in Vue 3 the Options API is implemented on top of the Composition API. All property access on the component instance (`this`) triggers getter / setters for reactivity tracking, and options like `watch` and `computed` invoke their Composition API equivalents internally.
 
 </div>
 
@@ -278,7 +278,9 @@ type DebuggerEvent = {
 
 ### Computed Debugging {#computed-debugging}
 
-<!-- TODO options API equivalent -->
+<div class="options-api">
+Computed debugging options are only available when using the Composition API.
+</div>
 
 We can debug computed properties by passing `computed()` a second options object with `onTrack` and `onTrigger` callbacks:
 
@@ -312,10 +314,30 @@ count.value++
 
 ### Watcher Debugging {#watcher-debugging}
 
-<!-- TODO options API equivalent -->
-
 Similar to `computed()`, watchers also support the `onTrack` and `onTrigger` options:
 
+<div class="options-api">
+
+```js
+export default {
+  watch: {
+    source: {
+      handler(val) {
+        // ...
+      },
+      onTrack(e) {
+        debugger
+      },
+      onTrigger(e) {
+        debugger
+      }
+    }
+  }
+}
+```
+
+</div>
+
 ```js
 watch(source, callback, {
   onTrack(e) {
diff --git a/src/guide/quick-start.md b/src/guide/quick-start.md
index bb9ffde788..6a9793e3b9 100644
--- a/src/guide/quick-start.md
+++ b/src/guide/quick-start.md
@@ -10,7 +10,7 @@ import { VTCodeGroup, VTCodeGroupTab } from '@vue/theme'
 
 ## Try Vue Online {#try-vue-online}
 
-- To quickly get a taste of Vue, you can try it directly in our [Playground](https://play.vuejs.org/#eNo9jcEKwjAMhl/lt5fpQYfXUQfefAMvvRQbddC1pUuHUPrudg4HIcmXjyRZXEM4zYlEJ+T0iEPgXjn6BB8Zhp46WUZWDjCa9f6w9kAkTtH9CRinV4fmRtZ63H20Ztesqiylphqy3R5UYBqD1UyVAPk+9zkvV1CKbCv9poMLiTEfR2/IXpSoXomqZLtti/IFwVtA9A==).
+- To quickly explore Vue, you can try it directly in our [Playground](https://play.vuejs.org/#eNo9jcEKwjAMhl/lt5fpQYfXUQfefAMvvRQbddC1pUuHUPrudg4HIcmXjyRZXEM4zYlEJ+T0iEPgXjn6BB8Zhp46WUZWDjCa9f6w9kAkTtH9CRinV4fmRtZ63H20Ztesqiylphqy3R5UYBqD1UyVAPk+9zkvV1CKbCv9poMLiTEfR2/IXpSoXomqZLtti/IFwVtA9A==).
 
 - If you prefer a plain HTML setup without any build steps, you can use this [JSFiddle](https://jsfiddle.net/yyx990803/2ke1ab0z/) as your starting point.
 
diff --git a/src/guide/reusability/custom-directives.md b/src/guide/reusability/custom-directives.md
index 989e2f9fd5..4d397a04ea 100644
--- a/src/guide/reusability/custom-directives.md
+++ b/src/guide/reusability/custom-directives.md
@@ -233,7 +233,7 @@ Similar to built-in directives, custom directive arguments can be dynamic. For e
 
 Here the directive argument will be reactively updated based on `arg` property in our component state.
 
-:::tip Note
+:::tip
 Apart from `el`, you should treat these arguments as read-only and never modify them. If you need to share information across hooks, it is recommended to do so through element's [dataset](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/dataset).
 :::
 
diff --git a/src/guide/scaling-up/routing.md b/src/guide/scaling-up/routing.md
index 4cc26f6e83..1ce2ffb61e 100644
--- a/src/guide/scaling-up/routing.md
+++ b/src/guide/scaling-up/routing.md
@@ -10,7 +10,6 @@ In such SPAs, the "routing" is done on the client side, in the browser. A client
 
 ## Official Router {#official-router}
 
-<!-- TODO update links -->
 <div>
   <VueSchoolLink href="https://vueschool.io/courses/vue-router-4-for-everyone" title="Free Vue Router Course">
     Watch a Free Video Course on Vue School
diff --git a/src/guide/scaling-up/tooling.md b/src/guide/scaling-up/tooling.md
index dda4318927..2aa56b755c 100644
--- a/src/guide/scaling-up/tooling.md
+++ b/src/guide/scaling-up/tooling.md
@@ -186,4 +186,13 @@ The official loader that provides Vue SFC support in webpack. If you are using V
 - [Vue on Codepen](https://codepen.io/pen/editor/vue)
 - [Vue on WebComponents.dev](https://webcomponents.dev/create/cevue)
 
-<!-- TODO ## Backend Framework Integrations -->
+## Backend Framework Integrations {#backend-framework-integrations}
+
+If you are using Vue with a backend framework (e.g. Laravel, Rails, Django, or Go), Vite provides several integrations for popular backend frameworks to help you manage your assets efficiently.
+
+- **Laravel**: Official [Laravel Vite integration](https://laravel.com/docs/vite).
+- **Rails**: [Vite Ruby](https://vite-ruby.netlify.app/).
+- **Django**: [django-vite](https://github.com/MrBin99/django-vite).
+- **Go**: [vite-go](https://github.com/hvuhsg/vite-go).
+
+Alternatively, you can manually configure Vite to work with your backend by following the [Vite Backend Integration Guide](https://vite.dev/guide/backend-integration.html).