diff --git a/src/api/composition-api.md b/src/api/composition-api.md
index a770a3731d..4f518614b9 100644
--- a/src/api/composition-api.md
+++ b/src/api/composition-api.md
@@ -117,6 +117,9 @@ The component instance context is also set during the synchronous execution of l
   - `errorCaptured` -> `onErrorCaptured`
   - `renderTracked` -> `onRenderTracked`
   - `renderTriggered` -> `onRenderTriggered`
+  - `activated` -> `onActivated`
+  - `deactivated` -> `onDeactivated`
+
 
 - **See also**: [Composition API lifecycle hooks](../guide/composition-api-lifecycle-hooks.html)
 
diff --git a/src/guide/composition-api-lifecycle-hooks.md b/src/guide/composition-api-lifecycle-hooks.md
index 1fbd0ed00a..9745620b24 100644
--- a/src/guide/composition-api-lifecycle-hooks.md
+++ b/src/guide/composition-api-lifecycle-hooks.md
@@ -21,6 +21,9 @@ The following table contains how the lifecycle hooks are invoked inside of [setu
 | `errorCaptured`   | `onErrorCaptured`   |
 | `renderTracked`   | `onRenderTracked`   |
 | `renderTriggered` | `onRenderTriggered` |
+| `activated`       | `onActivated`       |
+| `deactivated`     | `onDeactivated`     |
+
 
 :::tip
 Because `setup` is run around the `beforeCreate` and `created` lifecycle hooks, you do not need to explicitly define them. In other words, any code that would be written inside those hooks should be written directly in the `setup` function.