diff --git a/steps/25/README.md b/steps/25/README.md
index da7a132..a3883ec 100644
--- a/steps/25/README.md
+++ b/steps/25/README.md
@@ -4,10 +4,6 @@ So far we have worked with local JSON data, but now we will access a real OData
 
 ***
 
-So far we have worked with local JSON data, but now we will access a real OData service to visualize remote data.
-
-***
-
 In the real world, data often resides on remote servers and is accessed via an OData service. We will add a data source configuration to the manifest and replace the JSONModel type for our `invoice` model with the publicly available Northwind OData service to visualize remote data. You will be surprised how little needs to be changed in order to make this work!
 
 > :bulb: **Note:**
@@ -127,7 +123,7 @@ In the `models` section, we replace the content of the `invoice` model. This key
 
 Our component now automatically creates an instance of `sap.ui.model.odata.v2.ODataModel` according to the settings we specified above, and makes it available as a model named `invoice`. When you use the `invoiceRemote` data source, the `ODataModel` fetches the data from the real Northwind OData service. The invoices we receive from the Northwind OData service have identical properties as the JSON data we used previously \(except for the `status` property, which is not available in the Northwind OData service\).
 
-> :bulb: **Note:**:
+> :bulb: **Note:**
 >
 > If you want to have a default model on the component, you can change the name of the model to an empty string in the descriptor file. 
 >
@@ -152,4 +148,4 @@ As our app is now bound to a remote OData service, we do not need the `invoices.
 
 [First-Aid Kit](https://sdk.openui5.org/topic/dfe4f79843c44c40b3fb95ebffb65646.html "This section contains the most common issues that you might face when developing OpenUI5 apps and how to solve them.")
 
-[NPM Package: `ui5-middleware-simpleproxy`](https://www.npmjs.com/package/ui5-middleware-simpleproxy "Middleware for ui5-server, enabling proxy support.")
\ No newline at end of file
+[NPM Package: `ui5-middleware-simpleproxy`](https://www.npmjs.com/package/ui5-middleware-simpleproxy "Middleware for ui5-server, enabling proxy support.")
diff --git a/steps/33/README.md b/steps/33/README.md
index 3ce19f8..e78d681 100644
--- a/steps/33/README.md
+++ b/steps/33/README.md
@@ -295,7 +295,7 @@ You can now stop the interface generator again, as no further control API change
 
 ### webapp/controller/Detail.controller.ts
 
-In the `Detail` controller we implement a new `onRathingChange` event that reads the value of our coustom change event that is fired when a rating has been submitted. This requires to import our new control, as well as the `ProductRating$ChangeEvent` type we just defined to the detail controller. To keep the sample simple we only display a message message instead of sending the rating to the backend. We therefore load the `MessageToast` module from the `sap.m` namespace to our script. In addition we need the `ResourceBundle` module from the `sap/base/i18n` namespace as well as the `ResourceModel` module from the `sap/ui/model/resource` namespace as we want to display the confirmation message we specified in our resource bundle in the message toast.
+In the `Detail` controller we implement a new `onRatingChange` event that reads the value of our coustom change event that is fired when a rating has been submitted. This requires to import our new control, as well as the `ProductRating$ChangeEvent` type we just defined to the detail controller. To keep the sample simple we only display a message message instead of sending the rating to the backend. We therefore load the `MessageToast` module from the `sap.m` namespace to our script. In addition we need the `ResourceBundle` module from the `sap/base/i18n` namespace as well as the `ResourceModel` module from the `sap/ui/model/resource` namespace as we want to display the confirmation message we specified in our resource bundle in the message toast.
 
 In the `onRatingChange` the event handler we extract the value of our custom change event that is fired when the rating has been submitted. We then display the confirmation message we defined in our resource bundle with the rating value in a `MessageToast` control.