diff --git a/docs/docs/user/migration-guide/v6-v7.md b/docs/docs/user/migration-guide/v6-v7.md
index eb99e46a8..c08be2af8 100644
--- a/docs/docs/user/migration-guide/v6-v7.md
+++ b/docs/docs/user/migration-guide/v6-v7.md
@@ -65,13 +65,13 @@ As a result of the restructure, some imports need to be adjusted:
 
 Before v7, the KPOps CLI executed `destroy` before running `reset/clean` to ensure the component was destroyed.
 
-This logic has changed. The `destroy` method is now called within the `PipelineComponent`'s `reset/clean`.
+This logic has changed. The `destroy` method is now called within the `PipelineComponent`'s `reset`/`clean`.
 
-During migrating to v7, you should check your custom components and see if they override the `reset/clean` methods. If so, you need to call the supermethod `reset/clean` to trigger the `destroy` inside the parent class. Alternatively, if you are implementing the `PipelineComponent` class, you need to call the `destroy` method at the beginning of the method.
+During migrating to v7, you should check your custom components and see if they override the `reset`/`clean` methods. If so, you need to call the supermethod `reset`/`clean` to trigger the `destroy` inside the parent class. Alternatively, if you are implementing the `PipelineComponent` class, you need to call the `destroy` method at the beginning of the method.
 
 #### components.py
 
-For example, when creating a custom `StreamsApp` or `ProducerApp` (or any other custom component), you **must** call the supermethod `rest/clean` to execute the `destroy` in the parent class. **Otherwise, the logic of destroy will not be executed!**
+For example, when creating a custom `StreamsApp` or `ProducerApp` (or any other custom component), you **must** call the supermethod `reset`/`clean` to execute the `destroy` in the parent class. **Otherwise, the logic of destroy will not be executed!**
 
 ````diff
 class MyStreamsApp(StreamsApp):