diff --git a/docs/getting-started/getting-started-rest/03-handling-errors.md b/docs/getting-started/getting-started-rest/03-handling-errors.md
index 33a3a9d6c..7a0e86854 100644
--- a/docs/getting-started/getting-started-rest/03-handling-errors.md
+++ b/docs/getting-started/getting-started-rest/03-handling-errors.md
@@ -6,7 +6,7 @@ title: Handling Errors
 
 ## Introduction
 
-In this section, we'll focus on handling errors in your REST API. We'll define error models and demonstrate how to use union types for different response scenarios.
+In this section, we'll focus on handling errors in your REST API. We'll define error models and demonstrate how to add them as possible responses to your CRUD operations.
 
 ## Why Use Error Models?
 
diff --git a/docs/getting-started/getting-started-rest/06-versioning.md b/docs/getting-started/getting-started-rest/06-versioning.md
index 6bf7d2a45..d0fcf4873 100644
--- a/docs/getting-started/getting-started-rest/06-versioning.md
+++ b/docs/getting-started/getting-started-rest/06-versioning.md
@@ -401,6 +401,4 @@ In this example:
 
 ## Conclusion
 
-In this section, we focused on implementing versioning in your REST API. By using the `@versioned` and `@added` decorators, we can manage changes to our API over time without breaking existing clients.
-
 In the next section, we'll dive into creating custom response models for your REST API.